Early Access ER8411 V1 1.3.0 Build 20250305 Pre-Release Firmware (Released on Mar 14th, 2025)

This Article Applies to
ER8411(UN) V1
Release Notes
Version Info:
Adapted Model: ER8411(UN) V1
Fully Adapted Controller Version: SDNC 5.15.20.X - Omada SDN Controller_V5.15.20.7 Pre-Release Firmware Windows
Minimum Firmware Version for Update: 1.2.3 Build 20241121 and above.
New Features:
1. Add support to SD-WAN.
2. Add support to Content Filter.
3. Add support to Virtual WAN.
4. Add support to Disable NAT.
5. Add support to Google LDAP.
6. Add support to LAN DNS.
7. Add support to FQDN/Wildcards WAN DHCP Option.
Enhancement:
1. OpenVPN/Wireguard VPN: add support connecting to remote server/peer via domain name.
2. Optimized CPU utilization.
3. Optimized the time to enable the backup link.
4. Optimized booting time.
5. Optimized the time to dial up the WAN link.
6. Optimized the time to upgrade firmware.
7. Optimized the time to generate an OpenVPN profile.
Bug Fixed:
1. Fixed the HTTPS redirection exception in standalone.
2. Fixed the static route for L2TP VPN doesn't take effect after re-enabling L2TP VPN.
3. Fixed the WOL exception when dropping some unknown unicast packets.
4. Fixed the issue that the manual ISP profile for USB modem cannot be saved
5. Fixed the issue that the PPTP VPN would disconnect occasionally.
Firmware Download
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
(2) You may follow the following guide to upgrade your Omada devices. How to Upgrade/Downgrade Omada Gateways
Firmware Download Link
ER8411(UN)_V1_1.3.0_Build20250305
Notes:
(1) The above firmware applies to the described models.
(2) Your device’s configuration won’t be lost after upgrading.
(3) If you have disabled the HTTPS port, please enable the HTTPS port before upgrading the firmware.
Additional Information
All feedback is welcome, including letting us know about successful device upgrades.
If somehow you encounter an issue during or after the router upgrade, it's suggested to contact us with the following info:
- Omada Controller version
- Device Firmware version with Build number (previous and current)
If your rollback encounters trouble, try to use the CLI mode to roll back.
If your router gets bricked during the firmware upgrade, you may follow the guide below to recover the firmware.
How to use the Emergency Mode to recover the firmware for Omada Gateways
Update Log
Mar 14th, 2025:
Release of this post.
Recommended Threads
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Current Available Solutions to Omada Router Related Issues [Actively Updated, Post for Subscription]
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I have narrowed down the issue with switch vlan routing and the gateway static routes
If i re-do my switch vlans so the switch default routes point to the management vlan router interface, and match the gateway static route to the switch SVI on the management vlan, it all works.
As soon as the gateway static route is changed to any switch SVI that is NOT on the management vlan -it fails, instantly.
- Copy Link
- Report Inappropriate Content
Thanks for the quick reply.
I did a factory reset, updated in standalone mode and then adopted it and its working again. I don't know what happened..
As for the ACL rule it was a GW rule to block Home network to Default network (I know that that is the purpose of the ACL) but the problem was that when i tried to connect to my Plex server via my domain URL plex.mydomain... it wouldn't respond and time out. That was all while connected to my Home network (wifi or eth) but If I disconnected from my wifi for example then it worked without any issue. Same thing happened with my controller URL (omada.mydomain...).
What's really strange is that my Nextcloud and Vaultwarden URL's worked without a problem on wifi/eth on Home network or LTE/5G.
I'll keep you posted if anything goes bad again
Thank you !
- Copy Link
- Report Inappropriate Content
Hi @n0sh1t
Thanks for posting in our business forum.
n0sh1t wrote
Thanks for the quick reply.
I did a factory reset, updated in standalone mode and then adopted it and its working again. I don't know what happened..
As for the ACL rule it was a GW rule to block Home network to Default network (I know that that is the purpose of the ACL) but the problem was that when i tried to connect to my Plex server via my domain URL plex.mydomain... it wouldn't respond and time out. That was all while connected to my Home network (wifi or eth) but If I disconnected from my wifi for example then it worked without any issue. Same thing happened with my controller URL (omada.mydomain...).
What's really strange is that my Nextcloud and Vaultwarden URL's worked without a problem on wifi/eth on Home network or LTE/5G.
I'll keep you posted if anything goes bad again
![]()
Thank you !
Consider the LAN DNS which might affect your local domains now.
- Copy Link
- Report Inappropriate Content
Is there a guide for how to properly do the "Disable NAT" feature when being used with a controller? I feel like I have to be doing something incorrectly because as soon as I try to implement, it takes down the whole network due to IP conflicts with the device in front of it. I've gone as far to reset it and go standalone mode, but as soon as I try to add it to the controller is keeps picking up the x.x.x.1 and conflicting with the other router.
- Copy Link
- Report Inappropriate Content
Hi @W38122077
Thanks for posting in our business forum.
W38122077 wrote
Is there a guide for how to properly do the "Disable NAT" feature when being used with a controller? I feel like I have to be doing something incorrectly because as soon as I try to implement, it takes down the whole network due to IP conflicts with the device in front of it. I've gone as far to reset it and go standalone mode, but as soon as I try to add it to the controller is keeps picking up the x.x.x.1 and conflicting with the other router.
Got a guide in standalone. It should be the same for the controller mode.
- Copy Link
- Report Inappropriate Content
Clive_A wrote
Hi @W38122077
Thanks for posting in our business forum.
W38122077 wrote
Is there a guide for how to properly do the "Disable NAT" feature when being used with a controller? I feel like I have to be doing something incorrectly because as soon as I try to implement, it takes down the whole network due to IP conflicts with the device in front of it. I've gone as far to reset it and go standalone mode, but as soon as I try to add it to the controller is keeps picking up the x.x.x.1 and conflicting with the other router.
Got a guide in standalone. It should be the same for the controller mode.
Yeah, I saw it. It didn't work. So I reset to standalone and tried readopting, then disabling NAT. That didn't work, so I'm back to having just reset to standalone mode and trying to figure out next steps before adding it again...
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 1066
Replies: 36
Voters 0
No one has voted for it yet.