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
Hi @Hobbs1210
Thanks for posting in our business forum.
Hobbs1210 wrote
Controller is OC200 1.31.3 version 5.14.26.23 .
After factory reset new firmware worked as expected.
Please prepare a backup of your site. Not the support backup, I require a regular backup. I will send you an email later. Please reply to the email with the backup attachment.
- Copy Link
- Report Inappropriate Content
Hi @Hobbs1210
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240777868, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Hi @paulrob
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240777925, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Hi again. I think I've resolved the problem now, and I comfirm (with the short testing I've done so far) that FW V1.2.2 (Pre-Release) seems to now be working okay for me, but I have a little more reconfiguring to do since I started again from scratch instead of restoring my previous settings.
The basic problem was a local static IP address conflict in my static address pool (the range 192.168.0.2 to 192.168.0.99 is excluded from the DHCP pool for static IP use).
The conflict happened between the Wireguard Server settings and my QNAP NAS. I thought that address 192.168.0.3 was free to move my NAS to (a static IP address makes it easier to access the NAS and PCs locally via SMB on my phone). Looking at the Client List and the DHCP Reservation list, it appeared that this IP was free to use. Problem was I'd forgotten the WireGuard Server was also configured to use that IP, but when I allocated it to the NAS the DHCP Reservation page didn't alert me that this IP was already in use by Wireguard. So: lessons learned (red face). Moving the NAS to a higher free IP number resolved the issues.
By way of suggestion for consideration in future firmware, if I may, it would be helpful if the WireGuard server Local Address was indicated in the Cliient List or the DHCP Reservation list in some way so this doesn't catch others out. Thanks so much, and thanks again for all your assistance. It's been very much appreciated.
I think this ticket can now be considered CLOSED. But if there's any followup you'd like information on, please do let me know.
Best regards,
Paul
- Copy Link
- Report Inappropriate Content
Clive_A wrote
Hi @Hobbs1210
Thanks for posting in our business forum.
Hobbs1210 wrote
This firmware has caused the router to go into a configuration loop. Had to factory reset the router to get it working again with the controller.
What's the firmware of the controller? The version of the controller.
So, in your case, you reset it and it behaved properly again? Not the loop like the above, Adopting > Configuring > Heartbeat Missed > Adoptin.
I've resolved the problem as per my previous post, but FYI: the OC200 V2.0 controller has Firmware Version: 2.14.4 Build 20240304 Rel.54311
See below.
- Copy Link
- Report Inappropriate Content
Hi @paulrob
Thanks for posting in our business forum.
paulrob wrote
Clive_A wrote
Hi @Hobbs1210
Thanks for posting in our business forum.
Hobbs1210 wrote
This firmware has caused the router to go into a configuration loop. Had to factory reset the router to get it working again with the controller.
What's the firmware of the controller? The version of the controller.
So, in your case, you reset it and it behaved properly again? Not the loop like the above, Adopting > Configuring > Heartbeat Missed > Adoptin.
I've resolved the problem as per my previous post, but FYI: the OC200 V2.0 controller has Firmware Version: 2.14.4 Build 20240304 Rel.54311
See below.
Very glad to know that it is resolved by your efforts. And great to know that you have located the reason why. I am aware of them but we still would like to diagnose your backup. Please see the email I sent to you.
We would like to make sure everything's okay before a public release is on schedule.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Clive_A wrote
Very glad to know that it is resolved by your efforts. And great to know that you have located the reason why. I am aware of them but we still would like to diagnose your backup. Please see the email I sent to you.
We would like to make sure everything's okay before a public release is on schedule.
Thanks for your helpful interest. I've sent the Omada .cfg backup file in reply to your email now. This is the settings backup file taken just before the upgrade to V1.2.2 manifested into my difficulties. Hope it helps. And (stating the obvious) please only try it in an isolated test network, don't use it in a production network :) FWIW, my ISP provides dual-stack IPV4/IPV6 and I had it configured for both (and still do with the newly fixed configuration). My 1Gbps WAN is connected theough the SFP+ WAN1 port via a TP-Link 10Gbps Ethernet adapter. Sometimes I have a failover 4G LTE WAN also attached to the another WAN port, but not at that time.
Cheers,
Paul
- Copy Link
- Report Inappropriate Content
Hi Clive,
I have an issue with VPN, regardless of what protocol I use, OpenVPN, Wireguard IpSec etc I get roughly 250mb down 325mb up speeds when running speed test. The site has 3gb/3gb, and remote has 1.5gb/1gb.
Seems very strange when I believe the specs say this router can do over 2000mbps of OpenVPN.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 4403
Replies: 61
Voters 0
No one has voted for it yet.