Router changes IP to 192.168.1.1, a fix I hope can help others

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Router changes IP to 192.168.1.1, a fix I hope can help others

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Router changes IP to 192.168.1.1, a fix I hope can help others
Router changes IP to 192.168.1.1, a fix I hope can help others
2021-01-16 15:49:57 - last edited 2021-01-18 23:54:31
Model: Archer AX11000  
Hardware Version: V6
Firmware Version: 1.1.1

So first off, love the router as it replaced a dying ASUS AC3200.  Very easy to set up, very fast throughput!

 

However in my home I have some advanced things going on that lead me to not use the routers DHCP server and I can't change the network address range without significant pain and suffering on my part.

 

The AX11000 kept changing from the default 192.168.0.1 to 192.168.1.1 which would of course break everything.  I suspect because it detected an issue connecting with my ARRIS S33 which uses 192.168.100.1.  (The ASUS didn't allow me to navigate to the modems status page but it never complained about the 0.1 IP address I assigned it!)

 

Anyway, the solution seems wonky to me but it makes sense.  I'm sure some networking guys would shake their head because it seems like a cheesy way out but whatever, it works.

 

Just go set the routers LAN IP back to 192.168.0.1 and set the subnet to 255.255.0.0.  This tells it all networks in the 192.168.*.* range are valid.  It created a proper route in the routing table and everything works perfectly.

 

I found nothing on the web to help so I'm posting this in hopes that it's indexed and if anyone else has the issue, because of the reasons I had them (cannot change their network range) this may help them too!

  7      
  7      
#1
Options
2 Reply
Re:Router changes IP to 192.168.1.1, a fix I hope can help others
2021-01-18 23:50:42

@IzBox 

 

If it works, it works.

 

Thank you for the solution.

  0  
  0  
#2
Options
Re:Router changes IP to 192.168.1.1, a fix I hope can help others
2021-12-29 23:45:49 - last edited 2021-12-29 23:49:44

@IzBox 

 

Replying to this old thread for other users' future reference.

 

This issue is not caused by the modem management interface at 192.168.100.1.  Instead, it's caused by a hidden "auto-detection" feature of the TP Link router which interprets the presence of DNS and DHCP service running on another host within the same subnet as an indication of a duplicate gateway/subnet conflict.  It's intended to avoid causing existing networks from being taken down by a non-technical user plugging the router into a network with an existing gateway.  The TP Link router will automatically change it's LAN configuration to a different subnet to avoid the collision.  A cryptic error message will be displayed, "To avoid IP conflict with the front-end device, your routers IP address has been changed to X.X.X.X" but the real explanation won't be given.  As you've explained, you are deliberately running a separate DHCP service (and presumably DNS too) within your network. This should be permissible but the router won't tolerate it.

 

I've posted about the issue in more detail in a separate post:  https://community.tp-link.com/us/home/forum/topic/516726?replyId=1031064

 

That said, your workaround to set the router subnet mask to /16 (255.255.0.0) will not be suitable for any user/network that requires subnetting (e.g. using VLANs).  An alternate approach is to ensure that your TP Link router is configured to use a DNS other than the one colocated on your DHCP server.  This had the disadvantage of not funnelling all DNS queries to your private DNS, but it would enable use of proper /24 subnets.

  9  
  9  
#3
Options