Static/Fixed IP not working (ER706W V1.0 VPN Router with EAP653)
Static/Fixed IP not working (ER706W V1.0 VPN Router with EAP653)
Hello,
I am running a network with an Omada controller (hosted on premise on QNAP server Docker) whereby teh controller is fully managing the network.
Everything is working fine (roaming, 3 vlans, 3 SSIDs), but there is one thing not working: the fixed ip setting in Omada.
I've set for a lot of Tapo P115 devices a fixed ip within the Omada controller, but the IP address is switching every day. It seems like the fixed IP address option is simply not working.
I already tried the following things:
- Restart of whole network (VPN router & EAP653 APs)
- Enforcing configuration of controllers to router & EAP653
- Reconnecting the devices after setting the fixed IP address
Controller version:
5.14.32.3
EAP653:
VPN Router:
Example of IOT device (TAPO P115)
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
ok, I'm also using version 5.15 beta. but I don't think I've had the same problem as you with my ER706W ever. now mine is in a lab and is not used that much, so it could be something that I haven't discovered yet. I've had the router since it came out but haven't really had any problems as I can remember, so your problem is a mystery :-)
- Copy Link
- Report Inappropriate Content
Good to know, as the issue should be something within my setup. As a matter of fact, I did a hard reset yesterday evening, it took some minutes to adopt again, but until know everything is working fine again!
The beta version didn't make any change btw. It is just giving me errors in the mobile app when I'm opening a client for more details, but I don't care for now :p.
Let's see how long it will stay this way now.
- Copy Link
- Report Inappropriate Content
Looks like it fixed the problem (full reset of the router and adoption by the controller). It is currently also rejecting mac-adresses which try to get a reserved IP, but aren't allowed to get that reserverd IP.
Thanks again for your help, will close the topic for now.
- Copy Link
- Report Inappropriate Content
Well, having the same issue again and I may identified what is happening...
On November 16th, I executed the full factory reset on the VPN router.
On November 26th I turned of one EAP, as I needed to replace the power plug.
After this, a couple of devices (which were connected with this EAP), switched to another AP (the VPN Router).
At that moment it switched the IP to a completely different IP (192.168.2.37) in stead of the fixed IP address (192.168.2.8).
Then I just rejoined the device on the network and it is getting another new IP address (192.168.2.43) in stead of the fixed IP address. Looks like a kind of bug within the roaming functionality between the EAP and the VPN router. (see below image)
Could you please try out if you having the same issue in your lab environment? If so, I can reach out to TP-link support desk and hopefully they can fix this issue.
See below my site settings related to roaming.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @larrezz
Thanks for posting in our business forum.
larrezz wrote
Well, having the same issue again and I may identified what is happening...
On November 16th, I executed the full factory reset on the VPN router.
On November 26th I turned of one EAP, as I needed to replace the power plug.
After this, a couple of devices (which were connected with this EAP), switched to another AP (the VPN Router).
At that moment it switched the IP to a completely different IP (192.168.2.37) in stead of the fixed IP address (192.168.2.8).
Then I just rejoined the device on the network and it is getting another new IP address (192.168.2.43) in stead of the fixed IP address. Looks like a kind of bug within the roaming functionality between the EAP and the VPN router. (see below image)
Could you please try out if you having the same issue in your lab environment? If so, I can reach out to TP-link support desk and hopefully they can fix this issue.
See below my site settings related to roaming.
Delete the Fixed IP.
Go to the Service create a DHCP reservation and input the IP and MAC address manually. Save it.
Reboot the cam and see if it can request a new IP address.
- Copy Link
- Report Inappropriate Content
Thanks for the reply, but it doesn't fix the issue. It is rebooting again to the last IP address known.
Thereby, if I need to do this again and again, it's simply a workaround for a bug in the software/controller.
Do you have any idea why it is changing an IP address when it is moving to an other AP? This shouldn't be the case right?
- Copy Link
- Report Inappropriate Content
Hi @larrezz
Thanks for posting in our business forum.
larrezz wrote
Thanks for the reply, but it doesn't fix the issue. It is rebooting again to the last IP address known.
Thereby, if I need to do this again and again, it's simply a workaround for a bug in the software/controller.
First, there is a thing called DHCP lease time.
If your lease is not over, you will be using the same IP address.
That's not a bug. Read the RFC of DHCP.
Does this problem only happen to this device or all the network devices are affected?
Do not configure the fixed IP. Delete related reservations. Just create the DHCP reservation and reboot the router as well. It assigned the last known IP, which could be the DHCP lease time is not over so it reassign that known IP.
- Copy Link
- Report Inappropriate Content
Hi Clive, I understand how DHCP lease is working. The problem is that the gateway doesn't use the fixed IP in the right way. What is the cause that it doesn't use the fixed IP set in the router? Why are devices switching their ip address when they are roaming to another AP? Especially when they are changing from an EAP to the wifi of the router. Normally this behaviour can happen when someone is using standalone access points / a non-roaming/ mesh network.
A fixed IP should prevent that an IP adress is switching right? Or am I missing something here.
I simply never had this issue with my previous wifi set (TP link M4 (AP mode) with a Fritzbox as main router).
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 445
Replies: 19
Voters 0
No one has voted for it yet.