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
Hi Clive,
First some test results below:
1. I added a DHCP Reservation for a Tapo P115 plug (Charger phone)
2. I fully resetted the P115 and then connected it to the network
3. It is using the right IP address.
4. Then I tried to 'rebind' the plug via the Omada software controller. Result: connected again to the right IP-address
5. I took out the plug from the wall socket and inserted again, still same IP address.
So yes, it works for a fresh/clean device after full reset of it. There was one warning regarding ARP:
I tried the same for another plugin without resetting the device, and this was also working after step 4.
So yes, for now it is working.
Does this mean that the 'fixed IP' option when selecting is to a device after getting an IP address from the DHCP server is simply not working?
Why is this working fine with LAN connected device (including devices which sometimes power-off), but not with the wireless devices which sometimes move from AP to another AP?
Remote session: open for this, if this helps to find the strange issue somehow.
Settings, please see screenshots below.
LAN Setup:
Lan-IOT setup:
Wifi setup:
IOT WiFi setup:
- Copy Link
- Report Inappropriate Content
Hi @larrezz
Thanks for posting in our business forum.
larrezz wrote
Hi Clive,
First some test results below:
1. I added a DHCP Reservation for a Tapo P115 plug (Charger phone)
2. I fully resetted the P115 and then connected it to the network
3. It is using the right IP address.
4. Then I tried to 'rebind' the plug via the Omada software controller. Result: connected again to the right IP-address
5. I took out the plug from the wall socket and inserted again, still same IP address.
So yes, it works for a fresh/clean device after full reset of it. There was one warning regarding ARP:
I tried the same for another plugin without resetting the device, and this was also working after step 4.
So yes, for now it is working.
Does this mean that the 'fixed IP' option when selecting is to a device after getting an IP address from the DHCP server is simply not working?
Why is this working fine with LAN connected device (including devices which sometimes power-off), but not with the wireless devices which sometimes move from AP to another AP?
Remote session: open for this, if this helps to find the strange issue somehow.
Settings, please see screenshots below.
LAN Setup:
Lan-IOT setup:
Wifi setup:
IOT WiFi setup:
I am very worried about the ARP warning
As you are the owner of the network, have you tried anything to diagnose this MAC address and what device that is?
With this ARP warning bearing in mind, I am beginning to believe this might be a problem with your network environment where a second DHCP server appears.
I will consider creating a ticket or not before you figure out what that MAC address and type of device is.
- Copy Link
- Report Inappropriate Content
Hi @larrezz
Thanks for posting in our business forum.
Is there an update to my last reply on the ARP?
Do you have any results on this case now? Does it persist?
Can I close this case?
- Copy Link
- Report Inappropriate Content
Hi Clive,
I gave it a few weeks to see if there are coming new ARP requests, but it didn't. I didn't figure out why it did a ARP request in the first place.
After following your guidance by cleaning up all reserverd IP addresses, created new ones and connected the devices again to the netwerk, everything is finally working stable.
Thanks for that.
I just couldn't image why it has to be done like that in the first place.
You can close the topic for now, thanks.
Regards,
Lars
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1196
Replies: 24
Voters 0
No one has voted for it yet.