Early Access EAP773 | EAP783 v1.1.1 Pre-release Firmware (Released on 19th Aug, 2025)
This Article Applies to:
EAP783 V1, Fully Adapted to Omada SDN Controller v5.14 or above;
EAP773 V1, Fully Adapted to Omada SDN Controller v5.14 or above;
Release Notes:
New Feature/ Enhancement:
- Supported Portal Logout.
- Supported cluster deployment in Local Controller mode (Omada Central doesn’t support).
- Supported RADIUS Proxy(Global View> Server Settings> Radius Proxy Server).
- Supported OWE.
- Supported upgrading firmware through cloud in standalone mode.
- Supported Rate Limit with Portal Authentication.
- Supported disabling HTTP protocol in Standalone mode.
- Supported DHCP Option43.
- Supported multiple Radius servers when using MAC-Based Authentication (Site View Settings>MAC-Based Authentication).
- Added support for configuring NAS ID with WPA-Enterprise encryption.
- Supported DNS Queries (Network Tools>Network Check>DNSLookup).
- Supported DNS Adoption.
- Supported configuring the Device Name in Controller mode.
- Supported viewing status information and simple configuration through standalone management page when devices managed by the Controller.
- Supported displaying the maximum associated clients range in Controller mode(EAP Config>Advanced>Load Balance).
- Supported displaying the bandwidth of the EAP in Controller mode.
- Added Support for 11 a/n mixed mode for 5GHz radio in Controller mode.
- Supported multicast and broadcast data statistics.
- Supported disabling HTTP, HTTPS and APP discovery in Controller mode (Only with Pro controller).
- Supported Non-stick Roaming function.
- Supported authentication type of EKMS and Generic Radius with Unbound MAC for PPSK with Radius.
- Supports 1024 PPSK entries.
- Supported Multicast Filtering with IPv6 address.
- Supported Multicast/Broadcast Rate Limit
- Supported displaying Configuration Result.
- Optimized roaming function.
- Optimized Automatic Power Optimization function.
- Optimized the configuration of Beacon Interval.
- Optimized Portal Function.
- Optimized MLO connection stability.
- Improved Device and Network security.
- Improved time to configure SSID.
- Improved stability.
Bug Fixed：
- Fixed the issue that RSSI display error in WLAN Optimization.
- Fixed the issue that URL Filtering cannot work properly after TLS1.3 is enabled in the browser.
- Fixed the issue that HTTPS Redirection and Pre-Authentication Access don’t take effect when use portal.
- Fixed the issue that IPv4 multicast packets can’t be transmitted from mesh AP to root AP.
- Fixed the issue that one hop mesh AP’s client on SSID with VLAN would have slow Network speed.
- Fixed the issue that CoA doesn’t take effect with some MLO clients.
Pre-release Firmware Download
Attention
Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
EAP773_V1_1.1.1_20250818 (Pre-release)
EAP783_V1_1.1.1_20250818 (Pre-release)
Notes:
(1) The above firmware is applied to EAP773&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
19th Aug, 2025
Provide the following pre-release link:
EAP773_V1_1.1.1_20250818 (Pre-release)
EAP783_V1_1.1.1_20250818 (Pre-release)
19th Aug, 2025
Update the release note.
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
Hi everyone,
I am the one who posted recently about the MLO issue.
After updating my iPhone 17 Pro to iOS 26.0.1 and enabling MLO on the EAP783, the issue still persists in my environment.
When I try to connect to the MLO SSID, I still receive the error message: “Unable to join the network ‘M**_A’.”* and the connection fails.
However, if I disable MLO, the iPhone 17 pro can connect successfully over 6 GHz without any problem.
For your reference, the channel width of each band is set to “Auto.”
- Copy Link
- Report Inappropriate Content
Are you using all three bands? I get the same issue unless I remove 2.4GHz from the MLO enabled SSID.
- Copy Link
- Report Inappropriate Content
Myself I use all three bands, it works. However, I did not try with 6 Ghz bandwidth on Auto.
- Copy Link
- Report Inappropriate Content
Vincent-TP wrote
For security reasons, shell access is no longer supported on EAP devices.
This is disappointing to see. Shell access is already secured by access to the Oamada Controller interface in order to set the password, so this doesn't break any security boundaries and makes debugging the devices significantly more difficult. If you're worried about local privilege escalation and someone being able to gain persistence on the device, perhaps fixing the insecure setuid binaries and outdated kernels with security vulnerabilities would be more useful, as this also protects against other exploits that may be able to achieve RCE as an unprivileged user.
- Copy Link
- Report Inappropriate Content
hi @the901
Yes, I am using all three bands. I include 2.4 GHz because it helps with coverage, and I have not seen any documentation for the EAP783 stating that the 2.4 GHz band cannot be used with MLO.
- Copy Link
- Report Inappropriate Content
I'll have to do some additional testing with this iPhone 17PM to see if it supports tri-band MLO since client side matters as well.
- Copy Link
- Report Inappropriate Content
Thanks for your reply, I’d really appreciate it if you could test that.
I’d like to do more testing myself, but unfortunately our EAP783 units are already deployed and in operation with many devices connected, so it’s not an easy environment for experiments.
That said, we’ve been getting multiple complaints from employees about unstable connections, so I really want to find a way to solve this.
- Copy Link
- Report Inappropriate Content
I was able to get tri-band working. I had to forget the ssid on my phone after adding the third band and join the ssid again.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3734
Replies: 38
Voters 0
No one has voted for it yet.