EAP225 V3 FW bug ?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi TP,
I am using EAP225 V3 in stand-alone mode, managed by Web-UI only. In the WiFi network I am using a multi-room audio system (Block) which can be managed by the Undok App. After reboot of the AP everything works fine with the audio system. But then after > 10 (?) hours (audio system on or on stand-by) it gets somehow disconnected to the Undok App (device not found) - although it is still in the active client list of the EAP AP. I can also switch the audio system on manually and it works fine with Internet radio. But it cannot be found on the WiFi network anymore by a network scan. The only way to resolve this issue is a reboot of the EAP225.
To me this looks like a bug in the EAP V3 FW ... like as if the SSID isolation gets activated after a while automatically/accidentially/by false trigger. Can anyone of the TP team please create a support ticket on this case? Thank you.
Cheers, Manfred
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I had a similar problem which i think i have traced back to the EAP receiving its DHCP address. I am using a netgear router and have 3 EAP and the OC200 set with reserved ip. It seems by default the EAP will use their 'fallback ip' of 192.18.0.254 even when the option is disabled. This then causes the devices attached to the EAP to not be able to retrieve an IP. The EAP would sometimes not receive a new ip from the router and I was ending up with several EAP with IP conflict which then caused my whole network to slowly die until nothing would connect.
The controller would eventually report them as disconnected and only rebooting everything would get me back up.
The only solution I have found to be working is to enable the fallback ip on the EAP to be the same as it's reserved IP (including gateway address). Even then, after a reboot the controller reports that they connected to lan with .254 but after about 30 seconds they change and get the new (correct) lan IP. Same setup on the OC200 where the fallback ip is enabled and assigned to the same address as the DHCP reservation. This drove me insane for about 2 weeks, hope this helps someone else.
- Copy Link
- Report Inappropriate Content
Switch off the feature "Airtime Fairness"... in my case it helped !!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Questionmark wrote
Hey @forrest
Did your testing involve Airtime Fairness? It sounds like that is where the issue is...
Hi,
PLease upgrade the firmware to the latest version, we have optimized the Airtime Fairness in the latest firmware.
- Copy Link
- Report Inappropriate Content
forrest wrote
Questionmark wrote
Hey @forrest
Did your testing involve Airtime Fairness? It sounds like that is where the issue is...
Hi,
PLease upgrade the firmware to the latest version, we have optimized the Airtime Fairness in the latest firmware.
I upgraded to the new firmware after seeing this message last week. For 3 days now I have not experienced this issue (with Airtime Fairness on). I will report back if this changes or I get any further trouble.
However, thank you very much for resolving this issue.
- Copy Link
- Report Inappropriate Content
I've just experienced the problem again. I was unable to access devices connected to the EAP225 until I rebooted the AP. I am going to turn off the airtime fairness feature now to see if it makes a difference.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 7395
Replies: 26
Voters 0
No one has voted for it yet.