IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
At first I thought it was a one-off. Took me hours to figure out my internel IP subnet has changed from 192.168.0.1 to 192.168.1.1. After a few reboots, i've confirmed that the IPv4 LAN IP kept changing back to 192.168.1.1. What is going on?
Edit: Just adding that I am running Pi-hole on the same network. I'm forwarding the router's DNS request to the pi-hole's IP. The Pi-hole's DHCP server is disabled.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello, what is the current WAN DNS of the Deco M9 plus? Please ensure that there is no IP conflict between the LAN IP and WAN DNS on the Deco.
You can customize the LAN IP to another subnet if there do have IP conflict and you need use the specific WAN DNS, vice versa.
And we will forward this issue to our engineer, they will work on it then.
May it help.
- Copy Link
- Report Inappropriate Content
Sorry for the late reply. I did not get an email notification as I usually do on my other posts.
The WAN DNS IP is of course forwarded to the RPi that hosts Pi-Hole. Pi-Hole's DHCP is disabled and it's IP is DHCP reserved on 192.168.0.0/24. Somewhere above .100.
There are no devices that takes .0.1 since DHCP range is from .100 - .254. All other devices i set manually between .50 - .99. Yet every time i reboot both master and slave mesh, the master primary LAN IP will default to 192.168.1.1. This has happened twice already.
Thanks
- Copy Link
- Report Inappropriate Content
@NoMadPH I'm having the same issue. IP resets to 192.168.0.1 every time Deco is rebooted. No conflicts on the network. My LAN range is 192.168.20.1. This is very annoying. Please resolve.
- Copy Link
- Report Inappropriate Content
This issue has taken entirely too fucking long to resolve. I spend $400 on a pair of hardware with shitty development. This is the last time i purchase from this shoddy company.
- Copy Link
- Report Inappropriate Content
Hi there! I am so familiar with this problem!
- Copy Link
- Report Inappropriate Content
I am having the same problem with my DECO AX5700. i noticed sometimes when mu DECO reboot it change to an IP of 192.168.4.x but I set my LAN IP to 192.168.0.x. There's definately no conflicts as I can go back to the DECO and change my LAN IP back to 192.168.0.1. This is very annoying as it messes up my network setup as I would have to release and renew my IPs on the client get get the corect subnet after I change my LAN IP back to 192.168.0.x
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 13
Replies: 0
Voters 0
No one has voted for it yet.