Home Network Community > All Threads > IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
< All Threads

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.
12

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.
IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2020-01-21 06:10:13 - last edited 2020-01-21 06:17:03
Model: Deco M9 Plus  
Hardware Version: V1
Firmware Version: 1.3.0 Build 20190821 Rel. 54023

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.

  0      
 
  0      
 
#1
Options
16 Reply
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2020-01-22 01:12:25

@NoMadPH 

 

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. 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer AX55V2 Supports WireGuard VPN, EasyMesh Ethernet Backhaul, IoT Network, Speed Limit,and More If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#4
Options
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2020-01-25 17:57:20 - last edited 2020-01-25 17:58:52

@Kevin_Z 

 

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

  0  
  0  
#5
Options
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2020-05-24 17:44:45

@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. 

  0  
  0  
#6
Options
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2020-05-24 17:51:06

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. 

  0  
  0  
#7
Options
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2020-06-04 19:42:51 - last edited 2020-06-05 09:49:36

Hi there! I am so familiar with this problem!

  0  
  0  
#8
Options
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2021-06-12 14:49:21

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

  0  
  0  
#10
Options
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2021-12-17 10:53:57 - last edited 2021-12-17 10:57:32

@kubbie Yeah I could be wrong, I'm a programmer not IT/sysadmin, but Tp-Link's explanation of IP conflict seems sounds like a cop-out. I don't think I've ever seen someone with this problem post back and say "Oh hey! I found a solution - everyone set your X to Y!" or whatever. I wish I understood more about IPsec and could do some live-stream network activity recordings of exactly what happens at the time Deco decides to change the mask. Because after failing to configure this a half dozen times, everyone here just kinda gave up and are hoping for a patch.

 

If there IS indeed a ip problem, I have, again, not seen in the 7+ threads related to this issue, the settings needed to fix this. I find myself checking back here evry 2-4 months.

  0  
  0  
#11
Options
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2021-12-21 06:06:14

@flashVenom 

Hi, I am happy that you have shared your confusion with us.

The IP conflict here does not refer to a specific IP address.

The most common case I have ever seen is to set up the Pi-Hole IP address as a WAN DNS server under IPV4, which is not allowed since WAN DNS could not be in the same IP range as the LAN IP of Deco.

It might not be triggered the moment you changed the settings and a restart might be needed.

Possible solution: set up the Pi-Hole DNS as the LAN DNS server.

How to use Pi-Hole DNS Server on TP-Link routers?

 

The second is the WAN IP address/subnet mask and LAN IP/subnet mask are overlapping.

For example, WAN IPV4 settings 192.168.1.100/255.255.255.0 and LAN settings 192.168.68.1/255.255.0.0. Due to the wider range of LAN subnet marks, the LAN IP range actually included the WAN IP address.

Possible solution: change both the WAN and LAN subnet mask to 255.255.255.0.

 

So normally, if users said their LAN IP address kept changing, we could suggest they check whether they have the above issues.

While if you don’t, we would be glad to provide further assistance and you could send an email to support.forum@tp-link.com.

Thank you very much.

 

 

Deco Monthly Recap- Check What's Currently Going on With Deco KidShield Test Recruitment, Share Your Ideas With us! Wi-Fi Schedule Ideas Wanted!
  0  
  0  
#12
Options
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2022-01-05 06:25:19

@TP-Link thanks for responding. I'll give this another shot. And let's get this solved for everyone else as well. I have a feeling everyone else just wants a simple "Set this" answer so maybe we can give it to them... I'm trying to fully understand what you've said. I think I have my head wrapped around 80% of it.

 

I have a image below of all the pertinent settings screens. I'm using a fake IP address and gateway below. My network configuration is pretty much as simple and vanilla and standard as it could ever be... I also have a simple network diagram. Static IP of the Raspberry Pi running PiHole is 192.168.0.229. DHCP uses 192.168.0.100 to 192.168.0.255. So far so good, right?

 

So what you are saying is that when I set the Primary and Secondary DNS to the Pi's Static IP in the "DHCP Server" (SCREEN A) setting screen, this is the LAN... and when using the IPv4 Dynamic Ip" Setting (SCREEN B) screen, it is the WAN. So when I add the DNS servers in the WAN, it gets confused since the WAN DNS IPs is in the same range as the LAN DNS IP so it gets confused and thinks to itself "Hey, I can't have a DNS server inside my own subnet/mask"? Is that correct? If that's NOT correct, I guess I need to know what the difference is between the DHCP Server screen (SCREEN A below) and the IPv4 Settings screen (SCREEN B below)

 

So...

 

POSSIBLE SOLUTION #1 - So should I try JUST setting the "DHCP Server" DNS severs to the PiHole's IP (per SCREEN B)? And leave the IPv4 DNS servers blank on SCREEN A/A2? What do I fill in for SCREEN A2's DNS Servers (WAN)?

 

POSSIBLE SOLUTION #2 - You said I can try to set the WAN and LAN subnet mask to 255.255.255.0. But if I set the WAN to dynamic IP (A2) so I can change the subnet mask, it makes me enter a static IP for my ISP. If I don't have a static IP with my ISP, what should I do then? What should I enter for DNS IPs? Or am I going about this wrong?

 

Perhaps you can give me the settings for each screen, and I will give it a shot (and I'll update the image and post it back here for science). Then at least other people having this problem can have a visual idea of a very basic configuration.

 

 

 

  0  
  0  
#13
Options
Re:IPv4 LAN IP keeps changing back to 192.168.1.1 after multiple reboots
2022-01-05 09:13:02

 

flashVenom wrote

 POSSIBLE SOLUTION #1 - So should I try JUST setting the "DHCP Server" DNS severs to the PiHole's IP (per SCREEN B)? And leave the IPv4 DNS servers blank on SCREEN A/A2? What do I fill in for SCREEN A2's DNS Servers (WAN)?

When Deco connected to the ISP modem, the modem will assign IPV4 address/subnet mask/gateway as well as the DNS server to Deco. So if you choose Obtain DNS Automatically, it will use the ISP assigned DNS settings.

 

POSSIBLE SOLUTION #2 - You said I can try to set the WAN and LAN subnet mask to 255.255.255.0. But if I set the WAN to dynamic IP (A2) so I can change the subnet mask, it makes me enter a static IP for my ISP. If I don't have a static IP with my ISP, what should I do then? What should I enter for DNS IPs? Or am I going about this wrong?

The work around is only suitable when we noticed the IP conflict is cased by that the subnet mask of LAN is bigger than WAN, so we could change the LAN subnet mask to a smaller one, like 255.255.255.0. normally the WAN subnet mask could not be configured.

@flashVenom 

So currently, the reason why the LAN IP kept changing is that Deco might detect an IP conflict.

And the following configuration will intrigue IP conflict:

  • set up a LAN server as WAN DNS server.
  • the LAN subnet mask is larger than WAN which made the LAN and WAN actually in the same IP segment. (This case is very rare)

Most cases are related to the first one.

So If you have a PI-hole server, it needs to be configured under DHCP, like How to use Pi-Hole DNS Server on TP-Link routers?

Unless you find setting up a Pi-hole server under DHCP is not acceptable since it breaks the initial purpose of using PI-hole, we would like to hear more details on how you want to use the PI-Hole server.

Thank you very much.

Deco Monthly Recap- Check What's Currently Going on With Deco KidShield Test Recruitment, Share Your Ideas With us! Wi-Fi Schedule Ideas Wanted!
  0  
  0  
#14
Options
12

Information

Helpful: 0

Views: 4162

Replies: 16

Related Articles
Lan IP (DHCP Range keeps changing)
5159 0
Deco M9 - LAN IP range keeps changing on its own
624 0
Router keeps changing the LAN IP address
15182 0
Deco changing its "LAN IP" settings by itself
1934 3
LAN IP has been changing every reboot
5568 0
A10 changing LAN IP
406 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.