2 IP addresses wrong presented in Omada controller sotware and app after update of controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi there, good evening,
Have 3 EAP's running under Omada software controller v 3.2.4 Win64 Server 2016. Everything was running fine.
After update from v 3.2.4 Win64 to 3.2.6 2 IP addresses are presented wrong.
Two wireless devices which have fixed IP adresses are presented as 169.254.82.13 and 169.254.80.0 in stead of 192.168.125.201 and .202.
The devices are running perfectly but this is annoying me...
Sytem reboot didn't solve it
Anybody facing the same issue?
Regards,
A333
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Two wireless devices which have fixed IP addresses are presented as 169.254.82.13 and 169.254.80.0 instead of 192.168.125.201 and .202.
After you upgrade the firmware, the EAP devices get the IP addresses with 169.254.x.x, it means the EAPs don't get IP normally. You say the EAP should be presented as 192.168.125.201, so do you set the static IP address for the EAP? Normally if the EAP cannot get IP address, the fallback IP address will be 192.168.0.254.
Do you try to reset the EAP to have a try?
The devices are running perfectly but this is annoying me...
Do you mean even the EAP get an IP address with 169.254.82.13, when the client clients connect to the AP, the clients can still access the Internet?
- Copy Link
- Report Inappropriate Content
The EAP's have fixed ip addresses. They are running fine.
Only two identical Axis ip camera's presenting wrong ip addresses in omada controller and app. But they actually have a fixed address. Double checked it and they are running fine.
Yesterday they were actually presenting the correct ip. But after I forced a reconnection the wrong presentation was back again.
This ip camera network is isolated from the internet. The videostreams are recorded to a NAS which is working fine as a system.
This networksegment is also a separate VLAN.
A333
- Copy Link
- Report Inappropriate Content
@A333, IPs from the 169.254.0.0/16 address block are RFC 3927 link-local addresses (also sometimes called »automatic private IP addresses (APIPA)« in the Microsoft world).
An IP in this range means that the device (the Axis cam) cannot determine its IP address either by DHCP or due to a misconfiguration of a static IP. It then assigns itself an IP from this address block automatically.
See https://en.wikipedia.org/wiki/Link-local_address.
I suggest to disconnect the Axis cams from the network and to check their IPs in stand-alone mode. Then reconnect them to the WLAN and check the IP assignment again. If the IP then changes, it's anything but no static IP address what has been set on the Axis cam (this includes a possible bug in the Axis firmware).
- Copy Link
- Report Inappropriate Content
@R1D2 I know exactly what you mean.
Checked the settings again in the Axis IP cams. They are set correct. They are working like it should be and having fixed IP addresses.
Also, with previous Omada controller software it was presenting the right IP's.
Just after the Omada update, (and EAP firmware update which I did not mention!) the Axis are presented wrong in Omada.
And, again everything is working the way it should.. I thought the same: Axis firmware. Did a downgrade of it. Nothing changes. Back to latest again.
Now TP-Link support team is looking into it. fingers crossed..
Thx for the suggestion anyway.
Regards, A333
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2747
Replies: 4
Voters 0
No one has voted for it yet.