ER605 OC200 WAN Static IP can not be set if prior used
ER605 OC200 WAN Static IP can not be set if prior used
Hi,
Bug: When a static IP address once was set for a WAN, this IP can not be used on any other WAN port in future as static IP (it can as dynamic one though), even if the WAN port on which the address was originally used, was set back to dynamic IP address, uses a different IP address or even if the original WAN port which used that static IP is completely deactivated.
Scenario: switching a WAN Internet connection with fixed IP address from WAN/LAN 1 to the main WAN port or to WAN/LAN 2. Even if WAN/LAN 1 is set to dynamic IP and is disconnected or turned off, there will always be the error message: "The IP range you set for the WAN port conflicts with the IP range of the other WAN port." even though all other WAN ports now use a different IP address or even if all other WAN ports are deactivated.
I am using OC200, 5.14.26.23, 1.31.3 Build 20240620 Rel.80383
Problem: it seems once an IP address for a WAN connection has ben set to static, this IP address seems to be blocked forever. Not sure if there are underlying conditions that lead to the issue (like when exactly the cable has been switched or whatever).
What I tried, but unsuccessfully: Factory reset of the ER605, did not change anything, after adopting it was the same; turning on the original WAN/LAN 1 again and connect it again with the original modem - even then when you try to set a static IP again, you get the same error message (my thinknig was, I setup the original configuration, change the IP address, press disconnect and then set the static IP address on the other WAN port). Turning on WAN/LAN 2 and tried to set the static IP there, even then it was not possible.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Marc3485
Thanks for posting in our business forum.
As the error says, do you have an overlapped WAN/LAN subnet? Please post a screenshot of the WAN IP address you are supposed to get.
And the LAN IP address if you intend to change from the default VLAN interface 192.168.0.1/24.
It is normal for our devices to ban WAN and LAN from using the same subnet. It would make the routing incorrect. Avoid setting them to the same subnet would solve the error you see.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A , thanks for your message.
As mentioned in the original post, there is no other WAN activated.
The IP and Gateway also work very fine when dynamic set, so they are correct and not conflicting. However, we had issues with the ISP working in our area and therefore taking us offline for some seconds or minutes several times recently. Then - for whatever reason - their DHCP server took ages to allocate the IP again (I believe as the DHCP had to restart too), which is the reason why we want to switch to static as we have a static IP anyways and are then much faster online again after an interruption.
The VLANs dont overlap
Btw: the error says conflict with other WAN port, so I hope for a conflict with a VLAN another error message would apply. Otherwise the error message would be misleading.
However, as you see, it is so or so not the case.
The only thing I could think of is, that the WAN port gets before switching to Static this IP address already allocated. However, if that is the problem, it is still a bug because of course you should be able to switch on the same WAN port from Dynamic to Static by keeping the IP address. As the system also caches the IP for quite some time, you would then never be able to switch to static, so that it also can not be.
Thank you for your help!
- Copy Link
- Report Inappropriate Content
Hi @Marc3485
Thanks for posting in our business forum.
Marc3485 wrote
Hi @Clive_A , thanks for your message.
As mentioned in the original post, there is no other WAN activated.
The IP and Gateway also work very fine when dynamic set, so they are correct and not conflicting. However, we had issues with the ISP working in our area and therefore taking us offline for some seconds or minutes several times recently. Then - for whatever reason - their DHCP server took ages to allocate the IP again (I believe as the DHCP had to restart too), which is the reason why we want to switch to static as we have a static IP anyways and are then much faster online again after an interruption.
The VLANs dont overlap
Btw: the error says conflict with other WAN port, so I hope for a conflict with a VLAN another error message would apply. Otherwise the error message would be misleading.
However, as you see, it is so or so not the case.
The only thing I could think of is, that the WAN port gets before switching to Static this IP address already allocated. However, if that is the problem, it is still a bug because of course you should be able to switch on the same WAN port from Dynamic to Static by keeping the IP address. As the system also caches the IP for quite some time, you would then never be able to switch to static, so that it also can not be.
Thank you for your help!
Can you readopt the router if possible?
Looks not conflicting but this error looks abnormal. Will this behave after you readopt/force provisioning? This will resync the config.
- Copy Link
- Report Inappropriate Content
@Marc3485 Same behavior in here! Happy to see that i'm not the only one.
Is it fixed already somehow?
We had an power outage in the part of our country and after the power was back, the startup takes more than 4 hours before our WAN was connected to WAN DHCP.
My provider told me to do STATIC ip, but this is not possible due an error in Omada..
I can't switch to static due a WAN port that is used the same address, but there is no other port in use?
I hope to see this fixed asap.
Using VLAN 100 for WAN and using VLAN 1 for internal LAN network, the rest in LAN is DHCP and that's it.
Only difference i can imagine is the Subnet? Static subnet is 255.255.255.240 while our LAN is 255.255.255.0, no other specials i think?
Also DNS on LAN is not in use trough the gateway since we are using an local internal dns resolving, and the wan DNS is using google (8.8.8.8)
Our internet is glassfiber with an SFP+ module (10GBit).
Changing the LAN subnet to the same as WAN 255.255.255.240 leaves us behind without any internet, and still not possible to change from DHCP to STATIC on WAN side.
Using all latest firmwares of Omada.
hope to hear! Thanks
- Copy Link
- Report Inappropriate Content
@Clive_A I have re-adopted the router. I have even reset the router to factory settings, upgraded and adopted again. No change.
- Copy Link
- Report Inappropriate Content
Hi @Marc3485
Thanks for posting in our business forum.
Marc3485 wrote
@Clive_A I have re-adopted the router. I have even reset the router to factory settings, upgraded and adopted again. No change.
What about a new site without anything configured?
I think the problem is about the controller config as clearly, your settings are not conflicting the IP address. Something corrupts.
If you try this on a new site and it works okay, then it is the config corrupts. I think this might need the controller specialist to take a look. Could be a potential bug.
- Copy Link
- Report Inappropriate Content
@Barry1980 Unfortunatey it is not resolved yet.
Did you switch the physical WAN port at one point in time? My feeling is, the error is since we switched from WAN 2 to WAN 1. However, WAN 2 is turned off totally, there is no static IP set in this WAN port, so even if that might be the trigger (just a feeling), it is still wrong - and I did not find any way to solve it. Even turning back to WAN 2 does not help. Basically no chance to set a static IP.
Currently our ISPs DHCP is stable again, so dynamic works for us now. But still I want to switch to static to be safe. I hope tp-link helps us!
- Copy Link
- Report Inappropriate Content
@Clive_A New site. Hm, not so happy about that, never touch a running system ;-)
What would be the easiest workflow not to lose the current settings? There is no real way to "pause"/deactivate the current site and keep it in the controler, set up a test site and afterwards turn on the original one again? Beside exporting, deleting and importing, I know of that option of course.
- Copy Link
- Report Inappropriate Content
Hi @Marc3485
Thanks for posting in our business forum.
Marc3485 wrote
@Clive_A New site. Hm, not so happy about that, never touch a running system ;-)
What would be the easiest workflow not to lose the current settings? There is no real way to "pause"/deactivate the current site and keep it in the controler, set up a test site and afterwards turn on the original one again? Beside exporting, deleting and importing, I know of that option of course.
Then I run out of options so far. I don't have an OC200 ready next to me which I can use it to import your config and test. Software does not work with the backup from the hardware controller. I cannot test it. I have not experienced this issue for several firmware.
If the file has been corrupted, it does not work export/import because it contains the errors in the backup(config).
I mean you can simply adopt it to a new site and check if you can set the parameters. If this works, then it means the config problem on the previous site.
This can be recovered very quickly as you don't delete the old site but simply adopt it to the new site for a test and can be reset quickly and get back.
I've also updated the test team about this problem. Waiting for further replies from them as well.
- Copy Link
- Report Inappropriate Content
@Marc3485 no i did not switch any ports. I'm using glassfiber into the gateway directly. Works perfectly, but im still not able to do static wan like said before.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 658
Replies: 12
Voters 0
No one has voted for it yet.