<
WiFi
Bad Firmware for EAP235-Wall
Bad Firmware for EAP235-Wall
Posts: 114
Helpful: 60
Solutions: 4
Stories: 0
Registered: 2020-05-11
2024-05-11 09:04:03 - last edited 2024-05-11 09:14:49
Posts: 114
Helpful: 60
Solutions: 4
Stories: 0
Registered: 2020-05-11
Bad Firmware for EAP235-Wall
2024-05-11 09:04:03 - last edited 2024-05-11 09:14:49
Tags:
#Firmware Update
Omada app alerted me to new firmware release for EAP235-Wall - 3.2.2 Build 20240407 Rel. 70269.
This is not listed on the firmware page for this device.
After installing it WiFi clients struggled to load web pages. Reverting to 3.1.1 Build 20230414 Rel. 54637 resolves the issue.
Anyone else having this issue, or is it something about my network and devices?
#1
Options
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thread Manage
Announcement Manage
22 Reply
Posts: 2104
Helpful: 767
Solutions: 190
Stories: 0
Registered: 2022-03-05
Re:Bad Firmware for EAP235-Wall
2024-09-09 13:17:54
@Hank21 Hank, this issue seems to have dragged on for far too long. Has TPlink abandoned/delayed firmware fixes for Omada devices to develop the Festa loads? Your product team is nuts if they think I'm going to stay with Omada if they keep ignoring existing products/issues for the next shiny thing.
<< Paying it forward, one juicy problem at a time... >>
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#23
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 5
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2024-02-07
Re:Bad Firmware for EAP235-Wall
2024-09-30 15:16:46
I'm seeing what I think is the same problem. I've been having issues printing with AirPrint for months. I thought it was the printer so replaced it with another from a different manufacturer, but it has exactly the same issue. I pinned to the problem down to Link-local IPv6 communication. Today, I tried to enable IPv6 on the router and added IPv6 to my subnets. The wired connections are all still working perfectly. But the Wireless EAP325-Wall connections are unusably slow, seem to block communication. Reverting these to firmware 3.1.1 (which does not claim to support IPv6) seems to solve it. This removes the ability for the EAP to be assigned an IPv6 address itself, but the clients still get an IPv6 address, and seem to work ok.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#24
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 114
Helpful: 60
Solutions: 4
Stories: 0
Registered: 2020-05-11
2024-05-11 09:04:03 - last edited 2024-05-11 09:14:49
Posts: 114
Helpful: 60
Solutions: 4
Stories: 0
Registered: 2020-05-11
Information
Helpful: 4
Views: 2286
Replies: 22
Voters 0
No one has voted for it yet.
Tags
Report Inappropriate Content
Transfer Module
New message