Home Networking

Home VPN Not Working on Some Wi-Fi? It's Probably a Same-Subnet Conflict

Xavier •
#vpn#wireguard#tailscale#home network#192.168.1.0/24#subnet conflict#split tunnel

Short answer

Your laptop is on two networks at once: the Wi-Fi you’re sitting on and your home network through the VPN. If both use the same range (say 192.168.1.0/24), your laptop thinks 192.168.1.50 is on the local Wi-Fi and never sends it into the VPN. The lasting fix is to move your home network to an uncommon range, for example a random /24 inside 10.0.0.0/8 such as 10.47.83.0/24. If you can’t renumber, there are workarounds, but they are fiddly.

Sound familiar? In a post on r/HomeNetworking, one person worked it out like this: “I ended up realizing it was the first time I connected VPN while on a WiFi at a friend’s house, who also used a 192.168.x.x subnet range.” Another thread sums up the usual fear: “The hotel, or wherever, may also be using a 192.168.1.1 subnet. My understanding is that you are then out of luck.”

You are not out of luck. This guide shows why it happens, how to prove it with one command, and which home subnet to switch to so it stops happening. There is a small helper further down that picks a subnet for you.

A few words first, because they come up a lot:

  • A subnet is a block of IP addresses that sit on the same local network, like all the addresses your home router hands out.
  • /24 is the size of the block. The number after the slash says how many bits at the front are fixed. A /24 fixes the first three numbers, so 192.168.1.0/24 means 192.168.1.0 to 192.168.1.255 (256 addresses, 254 for devices). A /16 is bigger: 192.168.0.0/16 covers everything from 192.168.0.0 to 192.168.255.255. The CIDR notation guide explains this properly.
  • A route is a rule like “to reach 192.168.1.0/24, use the Wi-Fi”. Your device keeps a list of them, the route table, and checks it for every packet.

Why your VPN breaks when the Wi-Fi uses the same subnet as home

Everyone uses the same private ranges

Home networks, hotels and cafés all use private IP ranges. These are three blocks set aside for local networks that never appear on the internet:

  • 10.0.0.0/8
  • 172.16.0.0/12
  • 192.168.0.0/16

Anyone can use them, and everyone does. Your router uses NAT (network address translation) to swap these private addresses for your one public address when you go online. That is why millions of homes can all use 192.168.1.x without a problem, as long as they never have to talk to each other. More on these in private IP address ranges explained.

A VPN breaks that “never talk to each other” rule. Now your laptop is on the hotel’s private network and your home’s private network at the same time.

Routers ship with the same few defaults

Most home routers come with one of a small set of default /24s, such as 192.168.1.0/24, 192.168.0.0/24 or 10.0.0.0/24. Most people never change them. So the chance that the Wi-Fi you’re on uses the same range as your home is much higher than you’d guess.

Only real overlap clashes, not “both start with 192.168”

Two networks clash only when their ranges overlap, meaning some addresses are in both.

  • 192.168.1.0/24 and 192.168.0.0/24 do not overlap. One is 192.168.1.x, the other is 192.168.0.x. No clash.
  • 192.168.0.0/23 and 192.168.1.0/24 do overlap. A /23 is twice the size of a /24, and this one covers 192.168.0.0 to 192.168.1.255. That includes all of 192.168.1.x.

Not sure about your two ranges? Paste them into the subnet overlap checker. To see exactly what any /23 or /16 covers, use the CIDR to IP range tool or the CIDR calculator.

How your device picks a path: longest prefix match

When your laptop sends a packet, it looks for every route that matches the destination. Then it picks the most specific one: the route with the biggest number after the slash. This is called longest prefix match.

Say you are on a friend’s Wi-Fi that uses 192.168.0.0/24, and your VPN pushes a route for 192.168.0.0/16. Your laptop’s route table looks like this:

Destination        Goes to
192.168.0.0/24  -> Wi-Fi (connected, the friend's network)
192.168.0.0/16  -> VPN (pushed by the VPN)
0.0.0.0/0       -> Wi-Fi router (internet)

0.0.0.0/0 is the default route. It matches every address, so it is the “everything else” rule.

  • Destination 192.168.0.10 matches all three. The /24 is the longest (most specific), so it goes to the local Wi-Fi.
  • Destination 192.168.5.20 matches only the /16 and the /0. The /16 wins, so it goes into the VPN.
  • Destination 8.8.8.8 only matches 0.0.0.0/0, so it goes to the internet.

Rule to remember: the most specific route wins. The metric (a cost number on each route) only breaks ties between identical routes.

Want to play with it? Try this route table yourself in the routing simulator. Type in the three routes above and test a few addresses.

What happens when both sides are exactly 192.168.1.0/24

Now the Wi-Fi route and the VPN route are the same size. Neither is more specific. On most systems the directly connected Wi-Fi route wins, so your home devices are unreachable. You can ping 192.168.1.50 and get an answer, but it comes from some device in the hotel, or from nothing at all.

Why “just use full tunnel” usually doesn’t help

There are two common VPN modes:

  • Split tunnel: only some traffic goes through the VPN, usually just your home range. Everything else goes straight to the internet.
  • Full tunnel: all your traffic goes through the VPN, including normal web browsing.

A full tunnel works by adding 0.0.0.0/0 (or two halves, 0.0.0.0/1 and 128.0.0.0/1) through the VPN. But the local Wi-Fi’s connected /24 is still more specific than a /0 or a /1. So traffic to the local subnet still stays on the Wi-Fi. Full tunnel or split tunnel, the same LAN range on both sides breaks it the same way.

Check it in one command

Stop guessing. Ask your device which way it would send one home address. Swap 192.168.1.50 for a real device at home, like your NAS.

Windows (PowerShell):

Find-NetRoute -RemoteIPAddress 192.168.1.50

You can also see the full table with route print.

macOS (Terminal):

route -n get 192.168.1.50

Linux:

ip route get 192.168.1.50

Look at the interface in the answer. If it names your Wi-Fi (for example Wi-Fi, en0 or wlan0) instead of your VPN (for example wg0, utun3 or the VPN adapter’s name), it’s the conflict.

Then check the Wi-Fi’s own range, so you know what you are clashing with:

  • Windows: ipconfig
  • macOS: ifconfig, or the Wi-Fi details panel in System Settings
  • Linux: ip addr

If the Wi-Fi’s address and mask put it in the same range as home, you’ve found it.

Trust a live test more than the table

Some VPN clients don’t follow the route table you see. In this r/fortinet thread, the poster saw route print say a destination was local, but Find-NetRoute showed the VPN for addresses that only existed on the remote side. So trust a live test (Find-NetRoute, ip route get, or an actual ping to a home device) more than reading the table.

The real fix: change your home router’s subnet

Moving your home network to a less common range fixes this for good, on every Wi-Fi. It takes about an hour for a typical home.

Do this while you’re at home, not over the VPN. The moment you change the router’s address, the VPN connection drops and you’re locked out.

  1. Pick a range. See the next section and the helper below. This guide uses 10.47.83.0/24 as the example.
  2. Change the router’s LAN address. In the router’s admin page, change the LAN IP, for example from 192.168.1.1 to 10.47.83.1. Keep the subnet mask at 255.255.255.0 (that’s /24).
  3. Set the DHCP pool. DHCP is the router feature that hands out addresses automatically. Set it to, for example, 10.47.83.100 to 10.47.83.250.
  4. Update everything that has the old address in it:
    • DHCP reservations (fixed addresses the router hands to certain devices)
    • devices with static IPs: printers, NAS, a Proxmox host, Pi-hole
    • port forwards
    • firewall rules
    • DNS records
    • the VPN config: WireGuard AllowedIPs, Tailscale advertised routes, OpenVPN pushed routes
    • bookmarks
  5. Reboot or reconnect your devices so they pick up a new address.

Worked example: 10.47.83.0/24

Address
Network address10.47.83.0
Broadcast address10.47.83.255
Usable addresses10.47.83.1 to 10.47.83.254 (254 hosts)
Router (gateway)10.47.83.1
Static IPs10.47.83.2 to 10.47.83.99 (98 addresses)
DHCP pool10.47.83.100 to 10.47.83.250 (151 addresses)

The gateway is the router’s own address, the one devices send internet traffic to. You can check every line of this in the subnet calculator.

Which home subnet should I pick?

Best bet: a random /24 from the middle of 10.0.0.0/8. That block has 65,536 different /24s, versus 4,096 in 172.16.0.0/12 and only 256 in 192.168.0.0/16. More choice means less chance of a clash. See the whole 10.0.0.0/8 block for scale.

Avoid the obvious picks that other people also choose:

  • 10.0.0.x, 10.0.1.x, 10.1.1.x
  • 192.168.0.x, 192.168.1.x, 192.168.2.x
  • “nice” numbers like 10.10.10.x, 10.42.42.x, 192.168.10.x, 192.168.100.x

Avoid ranges your own tools use:

ToolRangeCovers
Docker default bridge172.17.0.0/16172.17.0.0 to 172.17.255.255
k3s pods10.42.0.0/1610.42.0.0 to 10.42.255.255
k3s services10.43.0.0/1610.43.0.0 to 10.43.255.255
kubeadm default services10.96.0.0/1210.96.0.0 to 10.111.255.255
Flannel default pods10.244.0.0/1610.244.0.0 to 10.244.255.255
Tailscale and CGNAT100.64.0.0/10100.64.0.0 to 100.127.255.255
iPhone Personal Hotspot172.20.10.0/28172.20.10.0 to 172.20.10.15 (14 usable)

Running Kubernetes at home? The Kubernetes pod CIDR calculator checks your cluster ranges against your LAN.

100.64.0.0/10 is not private RFC 1918 space. It’s shared space for ISPs (CGNAT) and Tailscale uses it for device addresses, so don’t use it for a LAN. And don’t put your home inside 172.20.10.x, or your laptop will clash with your own phone’s hotspot.

Some vendor defaults to skip, for example: AVM FRITZ!Box uses 192.168.178.x, GL.iNet travel routers use 192.168.8.x, newer ASUS routers use 192.168.50.x, and many ISP gateways use 10.0.0.x.

Plan for growth. If you might add VLANs later (separate networks for IoT, guests or a lab), pick a /16 for the whole house, such as 10.47.0.0/16, and use one /24 per VLAN: 10.47.10.0/24, 10.47.20.0/24, and so on. The VLSM calculator and the subnet cheat sheet help you split it. Want to get faster at this? Try the subnetting practice.

An honest note: nothing is guaranteed. Some networks (offices, universities, a few ISPs) use big parts of 10.0.0.0/8. An uncommon range just makes a clash rare.

Pick a safer home subnet

Press the button for a random 10.X.Y.0/24. It skips the Kubernetes ranges above, “pattern” numbers like 10.50.50.x, and anything in the box. Add any network you connect from often, like your office or a family member’s Wi-Fi.

Pick a safer home subnet

Gives you a random 10.X.Y.0/24 that skips popular picks and the ranges in the box below. Runs in your browser. Nothing is sent anywhere.

Ranges to avoid

Always skipped as well: 10.42.0.0/16 (k3s pods), 10.43.0.0/16 (k3s services), 10.96.0.0/12 (kubeadm services), 10.244.0.0/16 (Flannel pods). Add the hotel, office or lab ranges you know about.

Can’t renumber? Workarounds, from simplest to most work

Sometimes you can’t change your home subnet (a landlord’s router, a family who’ll riot). These work, but each has a catch.

a) Use mobile data or a phone hotspot when you need home access. A quick fix, not a solution.

b) Route only the hosts you need. Add a /32 route (a route for one single address) through the VPN for each home device you need. In WireGuard, put it in AllowedIPs, for example AllowedIPs = 192.168.1.50/32. A /32 is more specific than the Wi-Fi’s /24, so it wins.

The catch: while connected, you can’t reach whatever uses 192.168.1.50 on the local Wi-Fi. And never do this for the local gateway’s address (often .1), or you cut off your own internet.

c) A common mistake: splitting the home /24 into two /25s. Some guides say to route 192.168.1.0/25 and 192.168.1.128/25 through the VPN. Each /25 beats the local /24, so it looks clever. But 192.168.1.1, the local Wi-Fi gateway, is inside 192.168.1.0/25. You can break your own internet, or even the VPN connection itself. Only for people who know exactly what they’re doing.

d) 1:1 NAT on the VPN server (also called NETMAP). The server shows your home 192.168.1.0/24 to VPN clients as a different range, say 10.99.1.0/24. You reach 192.168.1.50 at 10.99.1.50. On a Linux WireGuard server that’s one rule, plus 10.99.1.0/24 in the client’s AllowedIPs:

iptables -t nat -A PREROUTING -i wg0 -d 10.99.1.0/24 -j NETMAP --to 192.168.1.0/24

It works, but now every device has two addresses, and your DNS names and bookmarks must use the mapped one.

e) Tailscale subnet router with an overlapping subnet. Tailscale has a feature for exactly this, called 4via6 subnet routers. Read their docs to set it up.

If you’re an MSP with many client sites on the same range, this guide is the wrong size for you. Read overlapping IP ranges across multiple clients instead.

Wake-on-LAN over VPN

Even after you fix the subnet, Wake-on-LAN often still fails over the VPN. A WoL “magic packet” is usually a broadcast (sent to every device on the local network), and broadcasts don’t cross a routed VPN. Send it from something already on the home side: your router’s WoL feature, Home Assistant, or a Raspberry Pi. Or SSH into a home box over the VPN and send it from there.

Common mistakes

  • Changing to another popular range (192.168.0.x or 10.0.0.x) and hitting the same problem at the next hotel.
  • Thinking 192.168.0.0/24 and 192.168.1.0/24 clash. They don’t. Only overlapping ranges clash.
  • Pushing 192.168.0.0/16 over the VPN “to cover everything” and expecting it to beat the local /24. It won’t. The /24 is more specific.
  • Forgetting static IPs, reservations, port forwards and VPN AllowedIPs after renumbering.
  • Renumbering remotely over the VPN and locking yourself out.
  • Picking a home range that clashes with Docker, k3s or Tailscale on your own lab.
  • Using 100.64.x.x or public IP ranges for a LAN. Stick to 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16.

FAQ

Why does my VPN work on mobile data but not on hotel or friends' Wi-Fi?

The Wi-Fi you are on probably uses the same IP range as your home network, for example both are 192.168.1.0/24. Your device sees that range as local, so traffic for your home devices stays on the Wi-Fi and never enters the VPN. Mobile data uses a different range, so there is no clash.

Will a full-tunnel VPN fix a same-subnet conflict?

Usually not. A full tunnel sends the default route (0.0.0.0/0) through the VPN, but your device also has a route for the local Wi-Fi subnet, such as 192.168.1.0/24. The most specific route wins, so traffic to that range still stays on the local Wi-Fi.

Does 192.168.0.x clash with 192.168.1.x?

No. 192.168.0.0/24 and 192.168.1.0/24 are two separate ranges that do not overlap. A clash only happens when the ranges actually overlap, for example 192.168.0.0/23 and 192.168.1.0/24, because the /23 covers 192.168.0.0 to 192.168.1.255.

What is the best subnet for a home network if I use a VPN?

Pick a random /24 from the middle of 10.0.0.0/8, such as 10.47.83.0/24, and avoid popular ranges like 192.168.0.x, 192.168.1.x and 10.0.0.x. Also avoid ranges your own tools use, such as Docker's 172.17.0.0/16 and Tailscale's 100.64.0.0/10. No range is guaranteed, but an uncommon one makes clashes rare.

How do I check if my VPN traffic is going to the right place?

Ask your device which route it will use for one home address. On Windows run Find-NetRoute -RemoteIPAddress 192.168.1.50 in PowerShell, on macOS run route -n get 192.168.1.50, and on Linux run ip route get 192.168.1.50. If the answer is your Wi-Fi interface instead of the VPN, you have a subnet conflict.

I can't change the other network. Can I still reach my home devices?

Yes, with workarounds. You can add a /32 route through the VPN for each home device you need, such as 192.168.1.50/32, because a /32 is more specific than the Wi-Fi's /24. Or set up 1:1 NAT on the VPN server so your home range appears as a different range, such as 10.99.1.0/24. Changing your home subnet is still the cleanest fix.

Why doesn't Wake-on-LAN work over my VPN?

Wake-on-LAN normally uses a broadcast packet, and broadcasts do not cross a routed VPN. Send the wake packet from a device that is already on your home network, such as your router, Home Assistant or a Raspberry Pi, and trigger it over the VPN.