Early Access ER8411 V1 1.2.3 Build 20241121 Pre-Release Firmware (Released on Dec 9th, 2024)
Early Access ER8411 V1 1.2.3 Build 20241121 Pre-Release Firmware (Released on Dec 9th, 2024)
This Article Applies to
ER8411(UN) V1
Release Notes
Bug Fixed:
1. Fixed the issue that the DPI doesn’t take effect on the latest version of Edge browser.
2. Fixed the issue that cannot set the same external port forwarding on different WAN IPs of WAN IP Alias.
3. Fixed the exception of EoGRE packets transmission.
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.2.3_Build20241121
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 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
Nov 26th, 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
When I migrate from ER6120 to 7206 and to 8411 among several years I found bug in 8411 that not present on 7206 and 6120:
under port map and under vpn sometimes cant connect to end service via port map or via vpn.
And after 2-3 minutes all works.
Sample 1:
I establish L2TP VPN from client to 8411 (or SSLVPN in second sample) but sometimes cant connect through vpn to service to end server into local network
I wait 2-3 minutes and all after that service works
Sample2:
There are port map configured for 20 services into local network
When I try connect to end services via portmap I found that some connections do not want establish
After several minutes i can establish connect to this services.
At all - sometimes all services connect good but sometime - does not want to work
But on 6120, 7206, 605 this problem absent and only 8411 wont work perfectly
IPS/IDS enabled but I try disable it - no effect
Same configuration but on other brand routers works correctly
Problem 2:
Wery bad web inteface productivity
Problem 3:
a)Address Reservation in DHCP section cant be sorted
b)Export/Import does not work too - try to export some config and import it...
c)IP Group List, IP Address List, VPN IP Pool List, Service Type List, Virtual Server List,IP-MAC Binding, MAC Filtering Deny List
cant bo sorted by columnts,be exported/imported
d)ARP List - no found string
e)Access Control List - columns is to short, no 'console list' present
f)All Web interface is not adapted for screen resolution
g)To my mind not all real blocks are listed in Threat Management
h)VPN User Account List (and in SSLVPN too) - cant be sorted/exported/imported - on huge editing/modifiyng it is a serious problem as in 7206 where this section is very buggy
h1) SSLVPN must be better - VPN must work only on the WAN interface, instead of working on traffic sent between LAN and WAN. Why you set SSLVPN as 'portmap' mode?
i)Tunnel Resources cant be sort by ID or simple movements can not be possible
j)Very poor System Status, Traffic Statistics, Diagnostic instruments
k)System log is only present for 'tag' - no search,export,sort by Level or by searched string
l)TP-Link logo in upper left cornet is to big end eat the screen size
m)If you does not plan ssh access- you can do web interface most faster,comfortable,etc to use but from product to product you can not do this
and if you plan be better - this products to my mind is not 'home usage' or soho products and in enterprise sector there are much admin friendly products present now
But to my mind ssh/sftp/tftp and etc services must be in corporate products
n) Try to administrate your products with nearest 200 VPN clients, 500+ DHCP lines on one device, 500+...1200Mbit real traffic with IDS/IPS on - all usage improvements be on top
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 1444
Replies: 11