NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NetGear Router | WAN / LAN IP Conflict issue
I recently had an issue on my XR1000 where I was not able to apply IP address reservation in the LAN setup page, due to the router reporting back that the LAN IP range is in conflict with the WAN IP. I have seen several posts in relation to this issue, one of which is:
If anyone else is experiencing this issue, check for this as a solution:
In the "internet setup" page in settings, check for any LAN IP's entered as your DNS servers, i.e. do you have primary / secondary DNS set as your LAN IP of the router or any other internal devices like a DNS server on your LAN? Try changing the DNS servers to something external like 1.1.1.1 and 8.8.8.8, THEN try applying your LAN settings config, you might find that the error message no longer exists.
This problem should not exist, but I guess it could be a bug / oversight in the coding.
20 Replies
That certainly would be a bug that should be reported. There should be no problem using a DNS server within the local IP subnet to resolve URLs. (Something only a tiny number of users would elect to do, but still perfectly legitimate.)
What FW is loaded on the XR router?
What browser are you using when you attempt to set an IP address reservation?
What brand and model# is the ISP modem or ONT that the XR router is connected too?
I recently had an issue on my XR1000 where I was not able to apply IP address reservation in the LAN setup page, due to the router reporting back that the LAN IP range is in conflict with the WAN IP. I have seen several posts in relation to this issue, one of which is:
The IP address conflicts with the WAN IP subnet. Please enter a different IP address. | NETGEAR Communities
If anyone else is experiencing this issue, check for this as a solution:
In the "internet setup" page in settings, check for any LAN IP's entered as your DNS servers, i.e. do you have primary / secondary DNS set as your LAN IP of the router or any other internal devices like a DNS server on your LAN? Try changing the DNS servers to something external like 1.1.1.1 and 8.8.8.8, THEN try applying your LAN settings config, you might find that the error message no longer exists.
This problem should not exist, but I guess it could be a bug / oversight in the coding.The firmware is XR1000 1.0.0.74_1.0.63.
The issue is resolved when I populate the DNS server fields with external (non-LAN) IP addresses. The issue only exists when I have LAN IP in the DNS server, and then try to apply config changes in the LAN setup page.
Possible for the XR series, requires external DNS addresses and not something supported if a LAN side address is used. This is a gaming router so focus maybe pointed at connections and getting gaming performances between WAN and LAN and using this in a standard connection path way. Having a internal DNS service or device may not be what was intended or may inhibit correct operation of the gaming system and FW. These gaming routers are fairly complex in what there features are and do.
Something to try, set the routers default DHCP IP address range to .100 to .200. Then set a static IP address on your DNS service device to something that is not with in the new DHCP IP address range. After thats configured, then try to apply the static IP address given on the DNS service device and set it in the routers DNS address menu. What do you see then?
I'll check this out with my XR as well and see. Most of the time, i've only used external DNS addressing and nothing from the LAN side.
The only reason I encountered this issue and found the cause was because I have pi-hole on my LAN serving DNS, so I had it's IP as the DNS server in the WAN setup page. I'm guessing its something like, the code behind the scenes scrapes IPs matching with regex or something and checks all IPs on the WAN setup page against the LAN IPs in the LAN setup page, then gives the error message of conflicting WAN / LAN IPs if match is found.
I have looked everywhere (I think) on the netgear site, but they don't make it clear where to report bug. Would you know where I could do this?
The issue is not being able to set an internal IP as DNS server, the issue is when an internal IP is used in the DNS servers and then you try to apply config changes in the LAN setup page, it then gives an error saying that there's a WAN / LAN IP conflict.
I have used a Pi-hole on the LAN as a DNS server with an Orbi router. Definitely legitimate.
The XR1000 runs DumaOS, so perhaps a bug report should go to Duma??
The Settings pages are NTGR software, not something we've touched ever so it wouldn't be something we could change. I don't believe using internal DNS has worked in the past, I could be wrong. Don't know the setup but if it's a device upstream of the XR it may not work, it may need an IP from the XR to work instead, again, I don't recall using internal DNS working though.
Using internal DNS server IP does work, it's just that I noticed this "WAN / LAN IP conflict" message issue if you happen to be using a LAN IP for DNS requests (i.e. a pi-hole), and then you want to apply configuration settings in the LAN setup page, then it gives the message and won't apply the new config. I have noticed a few individuals mentioning this same issue, albeit probably not a very common one since most people just either use ISP assigned or choose cloudflare or google.
The WAN IP subnet definitely is not 10.0.0.x (255.255.255.0), correct?
No, certainly not. My WAN IP is assigned by BT internet and is unique, which is why I hid it.
(sigh) yet another instance where access to the source code would lead almost immediately to the source of the problem.
It might be interesting to see if the choice of IP subnet has any effect on this. i.e. rather than set the router to use 10.0.0.x, pick some other IP subnet, such as the traditional 192.168.1.x Something is triggering the router firmware to this invalid conclusion and unfortunate acction.
As a side note, people on the Forum have different methods to approach the concept of IP addresses in the defined subnet. There are three types of address assignments:
- Static: where the IP address is set on the device, rather than on the router. The device never issues a DHCP request.
- Reserved: where the router maintains a list of MAC addresses and the IP address that should be given to each when it makes a DHCP request.
- Pool: a set of IP addresses that are randomly given out to devices that make requests and do not appear in the reserved list.
My personal practice is to divide the IP subnet into three contiguous sets:
- One set of IP addresses that are used for Reserved devices.
- One set of IP addresses that are used for the 'pool'.
- One set of IP addresses that are NEVER used for DHCP, and thus available for use by devices set with Static IPs.
My setup is
- IPs 192.168.1.2 through 192.168.1.100 are used for 'reserved' devices. The LAN setup table is used to record the MAC address of devices I want to manage and the IP address to assign to each of them.
- IPs 192.168.1.101 through 192.168.199 are used for the 'pool'. Any device that makes a DHCP request and is not in the assignment table gets an IP from this pool.
- IPs 192.168.201 through 192.168.1.154 are not defined as far as DHCP is concerned. The router will NEVER issue an IP address in this range to any device. (I actually have zero devices with Static IPs, but might occasionally set one up for an experiment.)
So if you set up all IP address reservations first and apply, then set the local LAN side DNS static IP address to be enabled and apply, does the system work as expected?
