Early Access ER8411 V1 1.2.2_Build_20240809 Pre-Release Firmware (Updated on Aug 12th, 2024)
This Article Applies to
ER8411(UN) V1 1.2.2 20240718(Pre-Release)
ER8411(UN) V1 1.2.2 20240809(Pre-Release)
Release Notes
Modifications:
1. Update OpenSSL version.
2. Support OpenVPN GCM algorithm.
Bug Fixed:
1. Fixed the issue that URL filter does not take effect when the browser enabled TLS 1.3 hybridized Kyber support.
2. Fixed some known security vulnerabilities.
3. Fixed some bugs and issues. (Build 20240809)
Firmware Download
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Beta/Pre-released 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.2.2_Build_20240718 (Pre-Release)
ER8411(UN) V1_1.2.2_Build_20240809 (Pre-Release)
Notes:
(1) The above firmware is applied to ER8411(UN) V1.
(2) Your device’s configuration won’t be lost after upgrading.
Additional Information
All feedback is welcome, including letting us know about successful device upgrades.
To get better assistance, you may check Tips For Efficiently Reporting an Issue In The Community.
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 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
Aug 12th, 2024:
Update the firmware.
July 19th, 2024:
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
- Copy Link
- Report Inappropriate Content
Thanks
Updated, havent seen any problems yet. My OC200 immediately saw it and readopted / configured. No looping. All 3 WANs work, all 8 LANs work, all ACLs seem to be working.
- Copy Link
- Report Inappropriate Content
I have had to go back to 1.2.1 official
I was getting no internet connectivity on 3 of my 8 vlans randomly for reasons I cannot determine. With absolutely no config changes and back on 1.2.1, no issues whatsoever
- Copy Link
- Report Inappropriate Content
hmm, that was weird. I haven't noticed any problems. but i only have 5 vlan. Did you reboot the router and switches after the upgrade? I have seen that it can solve strange things?
- Copy Link
- Report Inappropriate Content
yes, several times, and on a schedule too
Nothing in any logs indicate anything going awry when a vlan loses internet connectivity. DHCP is still serving IP addresses, DNS addresses and the gateway just fine. Just that end devices cant go out to the internet. Internal routing (such as access a printer on another VLAN using ACLs) worked fine though.
the moment i reflashed 1.2.1 and rebooted, all was well.
- Copy Link
- Report Inappropriate Content
ok, yes there is a lot that can happen with firmware so it is good that they have started with this Early access program so that we can find the errors as before the definitive release. As I said, I haven't noticed anything here with me yet.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
it doesn't work well when you don't get traffic through the tunnel. I don't know which interface you are talking about either. there is not much to configure on OpenVPN, if you are thinking of a LAN interface, you set it here.
in stand alone you set it here, here you can only use one network.
- Copy Link
- Report Inappropriate Content
Thank you for the fast reply!
Here what I wrought about! Developers just forgot to add OpenVPN interface here....
Also OpenVPN interface not available for Policy_Routing... ((
Best Regards!
- Copy Link
- Report Inappropriate Content
not sure what you are doing over there in the static route.
i think you are going too deep down the rabbit hole. Just follow the guide. Most important thing is to have your OpenVPN on a different subnet. So if everything is 192.168.1.0 etc, your OpenVPN needs to be something different than anything else 192.168.20.0 etc. getting it to work is easy if you follow the guide. You can complicate it by setting different acls and vlans after. More complicated is attempting to get anything over 250-300mbs throughput.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5149
Replies: 61
Voters 0
No one has voted for it yet.