Beta Software EAP783_V1_1.1.92 Beta Firmware (Update on 23th May, 2025)
This Article Applies to: EAP783_V1 Fully Adapted to Omada SDN Controller v5.14 or above
Release Notes:
New Features/Enhancements:
1. Supports displaying Configuration Result.
2. Supports cluster deployment in Controller mode (CBC does not support).
3. Supports Radius Proxy.
4. Supports OWE.
5. Supports custom Channel Range.
6. Supports upgrading firmware through cloud in Standalone mode.
7. Supports Portal Logout.
8. Supports disabling HTTP protocol in Standalone mode.
9. Supports DHCP Option43.
10. Supports multiple Radius Servers for MAC-Based Authentication.
11. Supports configuring NAS ID with WPA-Enterprise encryption.
12. Supports DNS Queries.
13. Supports configuring Rate Limit with Portal in Controller mode.
14. Supports configuring the Device Name in Controller mode, which can be carried in LLDP/SNMP/DHCP interaction.
15. Supports viewing status information and making some simple configuration through Standalone management page when the EAP is managed by the Controller and disconnected with Controller currently.
16. Supports displaying the maximum associated clients based on the EAP model in Controller mode.
17. Supports displaying the radio bandwidth of the EAP in Controller mode.
18. Supports configuring wireless mode in Controller mode.
19. Supports statistics of Multicast/Broadcast packets.
20. Supports 1024 PPSK entries.
21. Supports 802.11 a/n mixed in 5G.
22. Supports Non-stick Roaming function.
23. Supports authentication type of EKMS and Generic Radius with Unbound MAC for PPSK with Radius.
24. Supports Multicast Filtering with IPv6 address.
25. Supports reporting default OFDMA status.
26. Supports MAC Filter with 2000 entries per MAC Group profile.
27. Support DNS adoption.
28. Supports Multicast/Broadcast Rate Limit.
29. Enhances security protection.
30. Improves stability.
31. Improves support for more SSH commands.
32. Optimizes Automatic Power Optimization function.
33. Optimizes the configuration of Beacon Interval.
34. Optimizes roaming function.
35. Optimizes logs displayed in Controller.
Bug Fixed:
1. Fixed the issue that RSSI information display error in WLAN Optimization.
2. Fixed the issue about LLDP-MED packet forwarding exception.
3. Fixed the issue that URL Filtering cannot work properly when TLS1.3 is enabled in the browser.
4. Fixed the issue that HTTPS Redirection and Pre-Authentication Access don’t take effect in some special scenarios.
5. Fixed the reboot issue of EAP when client try connecting tri-band MLO SSID.
Notes:
1. This version of firmware is applied to the Omada APP v4.17 or above.
Beta Firmware Download
Attention
Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
EAP783_v1_1.1.92_Build_20250507(Beta)
EAP783_v1_1.1.90_Build_20250115(Beta)
Notes:
(1) The above firmware is applied to EAP783 V1.
(2) Your device’s configuration won’t be lost after upgrading.
(3) The above firmware is fully adapted to Omada SDN Controller v5.14 and above
Update Log
23th May, 2025
Provide the beta link for EAP783_1.1.92:
EAP783_v1_1.1.92_Build_20250507(Beta)
18th Mar, 2025
Update the release note.
17th Jan, 2025
Provide the download link:
EAP783_v1_1.1.90_Build_20250115(Beta)
Feedback
Any further feedback on the new firmware, please feel free to comment below or start a new thread from HERE.
To get better assistance, you may check Tips For Efficiently Reporting an Issue In The Community.
When reporting an issue, especially it's about firmware upgrade, it's suggested to include the following info:
- Management mode (Controller or Standalone)
- Device Model(s) and Hardware
- Device Firmware (previous and current)
Thank you in advance for your great cooperation and support.
Recommended Threads
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Current Available Solutions to Omada EAP Related Issues [Constantly Updated]
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
It's unlikely to be a hardware issue. Based on the feedback we've received so far, the affected clients are exclusively Samsung and iOS devices - other clients are functioning without any issues.
b101 wrote
@nikisima what i am afraid of is this: the hardware is defective. No amount of software/firmware will ever fix faulty HW.
- Copy Link
- Report Inappropriate Content
Hi Vincent,
After experiencing issues with 1.1.92, we downgraded back to 1.0.14. Could this cause problems with the devices?
We have already replaced two because they were not functioning properly. Ping interruptions, restarts, etc. It appears as though there may be issues with the downgrade.
It does indeed look like a hardware defect, but I would say it's due to the downgrade.
BR Tim
- Copy Link
- Report Inappropriate Content
Hi @TW_EPC
Under normal circumstances, downgrading the firmware should not cause any issues.
What's the performance of the replaced EAP783?
- Copy Link
- Report Inappropriate Content
Vincent-TP wrote
Hi @TW_EPC
Under normal circumstances, downgrading the firmware should not cause any issues.
What's the performance of the replaced EAP783?
The new or replaced AP is working again with 1.0.14. Just as it should.
Do you know roughly when we can expect a new version? Is the team really working on it?
BR Tim
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
> Did you try it?
Yes. Like everyone else here, it is still causing issues.
I don't really understand the question though, surely you guys have one modern iPhone to test this?
> Based on the feedback we've received so far, the affected clients are exclusively Samsung and iOS devices - other clients are functioning without any issues.
So only about 80% of all smartphones in the western world crash the access point.
- Copy Link
- Report Inappropriate Content
We have been actively collaborating with the Samsung and IOS technical support team to resolve the issues.
nikisima wrote
> Did you try it?
Yes. Like everyone else here, it is still causing issues.
I don't really understand the question though, surely you guys have one modern iPhone to test this?
> Based on the feedback we've received so far, the affected clients are exclusively Samsung and iOS devices - other clients are functioning without any issues.
So only about 80% of all smartphones in the western world crash the access point.
- Copy Link
- Report Inappropriate Content
@Vincent-TP When can we see the same update for EAP773? I'm having RADIUS problems over here. Clients getting dropped randomly and not re-associated. Also, a whole lot of these: "protocol 0000 is buggy, dev ath14"
Here's an example of what happened this morning with my iPhone 16 Pro:
-
AP and iPhone were in a stable MLO session.
-
Around 6:45 AM PT, the AP initiated a re-negotiation (possibly due to PMF key rekey, MLO link change, or driver restart).
-
The MLO negotiation path glitched (firmware bug), leaving the AP’s station entry half-valid.
-
AP stopped passing your data traffic but didn’t send a deauth/disassoc, so your phone stayed “connected” until you toggled Wi-Fi.
- Copy Link
- Report Inappropriate Content
Hi @Ashkaan
Thanks for the feedback.
This thread primarily discusses the EAP783 and already has numerous replies. We recommend creating a new thread specifically for your case to keep discussions organized.
In the new thread, please include the following info:
1. The controller type and firmware version;
2. The affected wireless clients. Or only the mentioned iPhone is affected?
3. The config of the RADIUS network, better with some screenshots.
4. Some screenshots of the mentioned "protocol 0000 is buggy, dev ath14".
Ashkaan wrote
@Vincent-TP When can we see the same update for EAP773? I'm having RADIUS problems over here. Clients getting dropped randomly and not re-associated. Also, a whole lot of these: "protocol 0000 is buggy, dev ath14"
Here's an example of what happened this morning with my iPhone 16 Pro:
AP and iPhone were in a stable MLO session.
Around 6:45 AM PT, the AP initiated a re-negotiation (possibly due to PMF key rekey, MLO link change, or driver restart).
The MLO negotiation path glitched (firmware bug), leaving the AP’s station entry half-valid.
AP stopped passing your data traffic but didn’t send a deauth/disassoc, so your phone stayed “connected” until you toggled Wi-Fi.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 10501
Replies: 126
Voters 2
