Subnet Overlap: Fixing 192.168.1.x Conflicts Between Routers, VPNs and Offices

Some “IP conflicts” aren't two devices sharing one address at all — they're two whole networks using the same address range. The symptoms look similar, but the fix is different: you renumber a network, not a device.

What subnet overlap is

Home and office networks use private address ranges that are reused by millions of other networks: 192.168.0.0/16, 172.16.0.0/12 and 10.0.0.0/8. Inside one network that's fine. The trouble starts when your device is connected to two networks at once that use the same range — for example, your home Wi-Fi is 192.168.1.0/24 and the office VPN also routes 192.168.1.0/24. Your computer now has two equally valid paths for 192.168.1.20 and can only pick one.

Typical symptoms

• The VPN connects, but you can't reach a file server, printer or intranet site at the office.
• Once the VPN is up, you lose access to your own home printer or NAS.
• A second router at home (from your ISP, or a mesh kit) leaves some devices on one network and some on another, and they can't see each other.
• The internet drops randomly after adding a router, and devices show addresses from two different ranges (e.g. some 192.168.0.x, some 192.168.1.x).

Scenario 1: Home network vs office VPN

This is the classic case. Corporate networks often use 192.168.1.0/24 or 10.0.0.0/24 — the same defaults home routers ship with. The cleanest fix is on your side, because you control your router:

1. Log in to your router's LAN settings.
2. Change the LAN IP from 192.168.1.1 to something uncommon, e.g. 10.47.12.1 with mask 255.255.255.0. The DHCP pool usually follows automatically (check it now reads 10.47.12.100–200).
3. Save; the router reboots. Reconnect your devices so they get new leases.
4. Update anything with a manual IP, port-forwarding rules and DHCP reservations.

Use our subnet calculator to double-check the range, mask and usable host addresses before you commit.

If you're the IT admin: choose corporate ranges that avoid the common home defaults, and for site-to-site VPNs between networks that already overlap, use NAT on the tunnel (sometimes called “NAT-T mapping” or “netmap”) rather than renumbering.

Scenario 2: Two routers on one home network

An ISP modem-router plus your own Wi-Fi router, or a hand-me-down router used as an extender, often creates two DHCP servers. Depending on how they're cabled, you get either double NAT (two separate networks) or two DHCP servers on one network handing out overlapping addresses — the latter causes genuine IP address conflicts.

• Best fix: put the ISP box in bridge / modem-only mode, so only your own router does routing and DHCP.
• If the second router is just for Wi-Fi: set it to access point mode, or disable its DHCP server, give it a static IP in the main network outside the DHCP pool, and connect a LAN port (not the WAN port) to the main router.
• If you must keep both routing: make sure their LAN ranges differ (e.g. 192.168.0.0/24 upstream, 192.168.50.0/24 downstream). Accept that devices on the two networks can't easily see each other.

Scenario 3: Two ISPs at home

Running two internet connections (say fibre plus a 5G backup) with two routers that both default to 192.168.1.1 is a recipe for confusion when a device or switch is connected to both. Give each router a distinct range, or use a dual-WAN router that manages failover from one LAN.

Scenario 4: Hotel, café and travel networks

Public Wi-Fi frequently uses 192.168.1.0/24 or 10.0.0.0/24 too, which can break a VPN back to your home network. Another reason to move your home LAN to an uncommon range: the overlap problem disappears wherever you travel.

How to see which ranges are in play

• Windows: route print — look for two entries covering the same network.
• macOS: netstat -rn -f inet
• Linux: ip route

If the same destination network appears on two interfaces (your Wi-Fi and the VPN adapter), you have an overlap. A traceroute to the unreachable host (see our traceroute guide) will show the traffic leaving on the wrong interface.

Rule of thumb: never use 192.168.0.x or 192.168.1.x for a network you'll ever need to reach over a VPN. Pick something boring and unique in 10.x.x.x and you'll never think about overlap again.