Router keeps changing the LAN IP address
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Router keeps changing the LAN IP address
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
At least once per week the router changes the LAN from 192.168.1.1 to 192.168.2.1 i don't have a clue what's going on with this thing! Has anyone else had this issue?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
As far as I know, the LAN IP of the router will change automatically once it detected that there is an IP conflict. So we would like to do further troubleshooting.
1. What is the current network diagram? How do you connect these devices together?
2. When the LAN IP of the C3150 changed to another one, what is the IP address of the front-end device? You can login to the web UI to verify it.
3. Does it affect the actual performance of the main router?
Thanks in advance, and have a nice day.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Same problem. AX11000 costs $400 and the stupid router won't take a LAN IP. I have my own DHCP server and other servers on the network and I want to assign the router a 192.168.1.1 address and it keeps resetting to 192.168.0.1. I've tried other 192.168.x.1 addresses and it still does the same thing when it's connected to the WAN. Pretty annyoing that you can't set a LAN IP on a $400 router.
- Copy Link
- Report Inappropriate Content
May I know your network topology as well, how is the AX11000 connected to the network? Is it working as a router, or access point?
If it is a router, what is the WAN IP address on it?
- Copy Link
- Report Inappropriate Content
I'm not wasting my time with all that again. I did that for hours with support. That isn't the issue.
Resolved: I set the router to use an external DNS server.
I haven't spent the time to figure out why an internal DNS server in the same IP range as the LAN causes the issue but it does. I really thought it was going to be an issue with the DHCP server but it isn't that. It's having a DNS server on an IP in the LAN IP range. Also, the issue *could* be that the internal DNS server is pi-hole. Like I said I haven't spent the time yet to figure it out. For anyone else you can still have a different DHCP server and that DHCP server can issue an internal DNS server to the clients. However, on the router itself you have to set an external DNS server, like openDNS 208.67.220.220, 208.67.222.222.
If I get the time I'll dig into the why but for now I don't care.
- Copy Link
- Report Inappropriate Content
Glad to know the issue was resolved.
I can explain this. There is auto-detecting mechanism that the router will detect the WAN and LAN addresses, it will change its own LAN IP address to 192.168.0.1/192.168.1.1 if it confirms there is an IP conflict, which means it is not allowed to configure the WAN DNS servers and the LAN IP address in the same subnet. To solve this, you can only change the DNS servers on the DHCP Server page.
- Copy Link
- Report Inappropriate Content
Ok. I see what you're saying. Since it's the WAN I need to have a non-lan IP as the DNS server. Makes sense. A different error message and/or highlighting that field as the conflict as it changes would save some debugging time. The conflict wasn't clear without the explanation you provided. Thanks.
- Copy Link
- Report Inappropriate Content
Awesome, great idea.
We would forward this to the develop team as a firmware improvement, hope they would consider it seriously.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 15305
Replies: 15
Voters 0
No one has voted for it yet.