How to Change Your Router's LAN IP to Avoid Conflicts

It's a rite of passage: you plug in the travel router at a hotel, the VPN connects, and… nothing loads. Or the admin panel becomes unreachable. Or the tunnel establishes and immediately dies. The culprit is often absurdly mundane: both routers are using the same LAN subnet, usually 192.168.8.1 or 192.168.1.1, and your devices can't tell them apart. Here's why it breaks things, and how to change your router LAN IP to avoid conflicts like this for good.

Why Two 192.168.8.1 Routers Break Your VPN

Every router defines a LAN subnet: the range of private addresses it hands to connected devices. GL.iNet travel routers famously default to 192.168.8.1; countless home routers default to 192.168.1.1 or 192.168.0.1. Trouble starts when your travel router's LAN subnet matches the upstream network's subnet.

Picture it: the hotel's network is 192.168.8.0/24, and your travel router's LAN is also 192.168.8.0/24. Your laptop asks for 192.168.8.100. Which network answers: the hotel's, or your router's? The routing table can't distinguish them, so traffic goes to the wrong place, or nowhere. Symptoms vary by which confusion wins:

• VPN tunnel won't establish. The router tries to reach your home server, but the conflicting routes send handshake packets into the void.
• Tunnel establishes, then everything hangs. Some packets route correctly, others don't, depending on which table entry wins each lookup.
• Admin panel unreachable. You browse to 192.168.8.1 expecting your travel router and get the hotel's gateway instead (or vice versa).
• Devices get conflicting DHCP. Two DHCP servers on overlapping ranges hand out chaos.

The same collision happens at home in reverse: if your home router and travel router share a subnet, the VPN tunnel's routing gets confused about which "192.168.1.x" is local and which is across the tunnel. The rule is simple: every subnet in your life must be unique: home LAN, travel router LAN, and ideally nothing matching the common hotel defaults.

Changing the LAN Subnet: Home or Travel Router

Pick one router to change (usually the travel router, since you control it and it meets new networks constantly). The procedure on OpenWrt-based routers like GL.iNet:

1. Connect to the router's admin panel directly (plug in via ethernet or join its WiFi before it joins any conflicting upstream).
2. Find the LAN IP settings. Usually under Network, LAN, or similar. You'll see the current IP (e.g., 192.168.8.1) and subnet mask (255.255.255.0).
3. Change the IP to your chosen new subnet. For example, 192.168.8.1 becomes 192.168.50.1. Keep the mask the same unless you know why you'd change it.
4. Apply and wait. The router restarts its network services. Your connection to the admin panel drops: that's expected.
5. Reconnect to the new address. Join the router's WiFi again (it may briefly disappear), then browse to the new IP (192.168.50.1 in the example). DHCP will hand your devices addresses in the new range automatically.
6. Update anything with the old IP hardcoded. VPN AllowedIPs referencing the old LAN range, firewall rules, port forwards, bookmarks to the admin panel. This is the step people forget, and it causes mysterious "worked before the change" issues.
7. Verify the VPN still works. Reconnect the tunnel, confirm the home IP, run the usual checks. Then test against a network that used to conflict, if you can.

If you'd rather change the home router instead (say the travel router's subnet is referenced in many configs), the same procedure applies; just be careful to update the VPN server's notion of the home LAN accordingly.

Choosing Subnets That Won't Clash With Hotels

Not all private subnets are equally collision-prone. Hotels, cafés, and ISPs overwhelmingly use a handful of defaults:

The crowded defaults (avoid these for your own gear):

• 192.168.0.0/24 and 192.168.1.0/24: the most common home/hotel defaults on earth
• 192.168.8.0/24: GL.iNet's default, hence half the travel routers in existence
• 10.0.0.0/24: common in corporate and hotel setups
• 172.16.0.0/24: less common, but some hotel chains use it

Better picks (obscure enough to rarely collide):

• 192.168.50.0/24, 192.168.77.0/24, 192.168.123.0/24: valid, memorable, rarely used by hotels
• 10.20.30.0/24: from the 10.x range, essentially never a hotel default
• 172.16.42.0/24: distinctive, easy to recognize in logs

A practical scheme: give the home LAN something like 192.168.50.0/24 and the travel router 192.168.77.0/24 (or 10.20.30.0/24). Both avoid the crowded defaults, both are easy to type, and they can never collide with each other. Write the scheme down somewhere you'll find it at midnight in a hotel: a note on the laptop, a label on the router, whatever works.

One more consideration: if you run services at home that the VPN needs to reach (a NAS, a printer, a media server), their addresses change with the subnet. Update bookmarks, app configs, and any firewall rules that reference them. And if you use the 10.x range, remember some corporate VPNs also use 10.x: if you ever need to run a work VPN inside your home IP tunnel, check for that second-order collision too.

FAQ

Need Help Setting This Up?

Subnet planning sounds trivial until it's 1am and two routers are fighting over 192.168.8.1. Our done-for-you setup includes sane subnet design across your home and travel gear, documented so you (or anyone) can understand it later: https://homeipvpn.com.