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
Hello @Clive_A
probably I focused at the secondary features while wrighting my reply, sorry..
Overaly I IMPRESSED by enhacements in 1.3.0 and suggest this fw to few mates that have issues about CPU efficiency.
the feature I requested (OpenVPN Client interface) should be very useful! For example pptp client already have interface,
l2tp client also have interface. openvpn and wg - not. Of cource i'm not insist at this feature to be primary -- some
users faced the bugs that made them to roll back this fw... they have to be in the priority!
Thank you! Best Regards.
- Copy Link
- Report Inappropriate Content
Hi @Sathiya
Sathiya wrote
@Clive_A I'm unable to select WAN Interface for the Virtual WAN even though I have 3 WAN ports configured.
https://community.tp-link.com/en/business/forum/topic/762178?replyId=1498288
https://community.tp-link.com/en/business/forum/topic/762178?replyId=1498290
Based on the reply from #8 and #9, they report that there is no issue with the Virtual WAN.
Can you confirm that this issue persists?
Edit: I read that you resolved by upgrading to the proper version of the controller. Please always do and read the release notes. It really helps.
- Copy Link
- Report Inappropriate Content
Hi @MR.S
MR.S wrote
It's SD-WAN that I've been looking forward to the most, so hopefully it will come to the other routers in beta soon.
Too bad you had problems with your upgrade, hopefully a fix will come pretty soon.
If normal firmware downgrade does not work, that means there are some changes in the system path. So, a simple downgrade like that does not work.
This cannot be optimized.
- Copy Link
- Report Inappropriate Content
Hi @n0sh1t
n0sh1t wrote
Updated to 1.3.0 without any issue by using the 'Firmware' section in Global view. Had to rollback the firmware cause I had issues with inter-vlan routing and couldn't figure it out but the rollback feature doesn't work, I tried 3 times and it failed. I had to go with the How to use the Emergency Mode to recover the firmware for Omada Gateways way and it worked like a charm.
So the inter-vlan routing problem.. I updated without changing any config at all and after the update my Home vlan (10) was not able to reach any URL/ip address from my network (I use NPM as reverse proxy). The only way that it worked is if I disable the ACL rule that prevents my Home network to communicate with my Default network. With the 1.2.3 version everything works but with 1.3.0 it doesn't work and couldn't figure it out so I'll wait for the stable version or a new update for EA and try it again. Is there a new feature that could cause this ?
Also the temps that are shown from the gateway are not accurate at all. Before the update (1.2.3) my temps were in the 60-62C, after the update (1.3.0) they were like 75-77C !! And the fan doesn't kick in at these temps wich I find odd since they kick in when the temps reach 65C with the 1.2.3 version.
On the good side, I tried the Content filter feature and that's pretty nice to have and works well. The LAN DNS works well too. Didn't try the other features cause the wife and kids couldn't access Plex from the TV or phones so had to go back to 1.2.3.
About the ACL, what kind of ACL? SW or GW?
If it can be resolved by disabling the ACL, I presume that this is not a problem with the firmware. Something might conflict.
But I still require the following information:
1. Diagram of your network with the IP specified and your reverse proxy.
2. Backup of your config. Not the support backup.
3. ACL config screenshots.
Send them in the mail template.
- Copy Link
- Report Inappropriate Content
Clive_A wrote
Hi @MR.S
MR.S wrote
It's SD-WAN that I've been looking forward to the most, so hopefully it will come to the other routers in beta soon.
Too bad you had problems with your upgrade, hopefully a fix will come pretty soon.
If normal firmware downgrade does not work, that means there are some changes in the system path. So, a simple downgrade like that does not work.
This cannot be optimized.
Ok, there was a new function on the router console called roll-back that worked so there are options to roll back. Otherwise everything works very well for me, many things are faster, such as rebooting which took forever before.
- Copy Link
- Report Inappropriate Content
Hi @iWelna
iWelna wrote
Hello,
After upgrade to 1.3.0 my IP TV services stopped working, i have two STB (diff manufacturer) and both couldnt get started.
Had to downgrade to 1.2.3 and all started to work again :(
Please look into it b4 releasing this as stable, since this is crucial service with Omada ecosystem for me.
OC200 ER8411 v1.0
SX3008F v1.20
SG3210X-M2 v1.0
3x SG3210 v3.20
2x EAP773(EU) v1.0
Greets
Details of your network diagram.
IPTV settings screenshots.
Device Info exported and attach it in the email.
Regarding this problem, are you able to use Wireshark on the IPTV service port by port mirroring?
We might need a remote session to locate the reason.
Send an email with the information I require: Email template.
- Copy Link
- Report Inappropriate Content
Hi @MR.S
Thanks for posting in our business forum.
MR.S wrote
Clive_A wrote
Hi @MR.S
MR.S wrote
It's SD-WAN that I've been looking forward to the most, so hopefully it will come to the other routers in beta soon.
Too bad you had problems with your upgrade, hopefully a fix will come pretty soon.
If normal firmware downgrade does not work, that means there are some changes in the system path. So, a simple downgrade like that does not work.
This cannot be optimized.
Ok, there was a new function on the router console called roll-back that worked so there are options to roll back. Otherwise everything works very well for me, many things are faster, such as rebooting which took forever before.
For the normal way to downgrade, which we use the web GUI and upload the firmware, it does not work, that's the reason I gave in the last reply.
If that new feature can roll back easily, that'd be great.
Will update the contents to let people know about it. Thanks!
If you can upload a screenshot of this feature, that'd be wonderful. I have not got an 8411 from the warehouse yet.
- Copy Link
- Report Inappropriate Content
To downgrade the firmware, you need to log in to the router's console using SSH, then type these commands.
enable (Turn on privileged commands)
roll-back (Roll back to the previous software version)
Press Y
wait 10 minutes and you will be back to the old version
- Copy Link
- Report Inappropriate Content
backup sent
I am currently back on 1.3.0 with a rebuilt network using only gateway switched vlans and this works fine. A few other things that I have noticed for feedback
1) Termperature is reporting 7 degrees higher than on 1.2.3 in the exact same conditions
2) Very nice how much faster it boots now
3) Content filter working well
4) Bummer! Why cant i set a virtual WAN vlan tag the same as i can an internal LAN? You can do this on a normal WAN, just not a virtual ?
5) Resolved my L2TP issue - seems gateway ACLs are working slightly differently now when blocking traffic on WAN IN
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 851
Replies: 29
Voters 0
No one has voted for it yet.