Beta Software ER8411 V1_1.1.1 Build 20231030 Beta Firmware for Omada Controller V5.13 (Released on Oct 31th, 2023)
This Article Applies to
ER8411(UN) V1_1.1.1 Build 20231030 Beta
Release Notes:
New Features & Enhancements:
1. Add ACL support for IPv6 data.
2. Add support for IPv6 RA (Router Advertisement) configuration for LAN.
3. Add support for configuring multiple IP addresses on the WAN port.
4. Add support for monitoring session limits in controller mode.
5. Add support for configuring the MSS (Maximum Segment Size) of WAN port.
6. Add support for Gateway Tools in Controller mode.
-
Ping.
-
Traceroute.
-
Terminal
7. Add support for the ability to download device info of Gateway in Controller mode.
8. Add support for Location Group in Gateway ACL.
9. Add support for allow list of MAC filtering in Controller mode.
10. Add support for tagging same VLAN ID on different WAN port.
11. Increased security of communication between Gateway and Controller.
12. Add support for DNS cache, which can improve domain name resolution speed by handling recent address resolutions locally before sending request to Internet .
13. Add support for DH 14 and DH 15 for PFS.
14. Add support for 0.0.0.0/0 IP range of local network when using IPsec IKEv2 for Client-to Site VPN.
15. Add support for DDNS custom intervals (1~60 minutes).
16. Add support for link-local addresses of IPv6 DNS on the LAN side.
17. Log Enhancements.
-
Show the source IP address of TCP no-Flag /ping of death attacks.
-
Show the log of link backup switching.
-
Show the log of DDNS update.
-
Logs can be saved when the device is down. You need to short press the reset button within 5s, and after releasing the reset button, the sys light will be on for 3 seconds to indicate that the downtime log is saved successfully.
18. Add support for Deep Packet Inspection.
19. Add support for enable/disable Flow Control in Controller mode.
20. Add support to modify the rate and duplex of the Ethernet port in Controller mode.
21. Add support GRE function in Standalone mode.
22. Add RIP and OSPF dynamic routing function in Standalone mode.
23. Add LDAP Authentication for PPTP/L2TP/OpenVPN and Web Authentication. Web Authentication only support in Standalone mode.
Bug Fixed:
1. Fix the bug that ICMP type 13 packets cannot be intercepted
2. Fix the bug that VPN Client cannot access the other side through IPsec when the device act as a PPTP/L2TP/OpenVPN Server and also establishes IPsec VPN with other devices.
3. Fix the bug that VPN client cannot proxy Internet access when VPN IP Pool and LAN IP are in the same network segment.
4. Fix the bug of CPU abnormality caused by enabling more VLAN Interface.
5. Fix the bug of high latency in ISP Load in Controller mode.
6. Fix the bug of frequent reconnection with Omada Controller.
7. Fix the bug that the VLAN configuration of IPTV is affected by the VLAN configuration of WAN port in Controller mode.
8. Fix the bug that the device does not support proxy internet access as Wireguard VPN client.
9. Fix the bug that Port Forwarding does not take effect under multiple WAN ports.
10. Fix the bug that the port status display is abnormal in Controller mode.
11. Fix bugs related to OpenVPN:
-
OpenVPN clients cannot proxy Internet access through the device.
-
OpenVPN IP pool cannot be configured.
-
When the device is used as an OpenVPN Server and the option is Split mode, OpenVPN clients cannot access the Internet normally.
-
Remote IP error displayed in the OpenVPN Tunnel interface when the device connects successfully as an OpenVPN Client.
-
When the device acts as an OpenVPN Client, OpenVPN fails to start when there are unsupported fields in the OVPN file.
12. Fix the bug that cloud access could not connect successfully when PPPoE dialup was performed on the WAN port.
13. Fix the bug that after the device connects to the Server as a WireGuard VPN Client, the peer cannot access the device via WireGuard Interface IP.
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.1.1_Build 20231030 (Beta)
Notes:
(1) The above firmware is applied to ER8411 V1/1.6.
(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.
If somehow you encounter an issue during or after the ER605 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 ER8411 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. 20th, 2023:
Update the format and incorrect description in the release note.
Oct. 31st, 2023:
Post the ER8411 V1 1.1.1_Build 20231030 (Beta) firmware for early access.
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 @Dan15
Thanks for posting in our business forum.
Dan15 wrote
Clive_A wrote
Hi @Dan15
Thanks for posting in our business forum.
Dan15 wrote
16. Add support for link-local addresses or unique local addresses of IPv6 DNS on the LAN side.
This doesn't appear to work in the web UI. I get an error "Invalid format":
It works fine if I modify the JavaScript to not perform the validation though.
Can provide a beta for you if needed. Let me know this and will send it to you.
Yes please.
Another bug report: When configuring IPv6 via the Omada controller, the "RA Valid Lifetime" and "RA Preferred Lifetime" fields don't have default values.
Got a confirmation that this(what you said bug report) requires V5.13 controller.
- Copy Link
- Report Inappropriate Content
Tanks for the updated beta,
after a short test it looks like the issue introduced in this firmware is fixed,
I will let you know if I discover any problems other than those that are already well known for a long time..
- Copy Link
- Report Inappropriate Content
Hi @MR.S
Thanks for posting in our business forum.
MR.S wrote
Tanks for the updated beta,
after a short test it looks like the issue introduced in this firmware is fixed,
I will let you know if I discover any problems other than those that are already well known for a long time..
Feel free to let me know if there is any issue with it. Will pass it to the dev team. :)
- Copy Link
- Report Inappropriate Content
t's not a big deal. there are two devices connected to the ER8411 but I see it switching between one and two devices after the upgrade.
The CPU has also gone up a lot, but that shouldn't necessarily be a problem, maybe it has started to work with somthing :-)
- Copy Link
- Report Inappropriate Content
@Clive_A after upgraded it to this build with Early Access Omada SDN Controller_V5.13 Beta (Updated on Nov 21st, 2023), I lost my network traffic information. FYI, all graphs are now shown as 0 (only client information is working and valid)
- Copy Link
- Report Inappropriate Content
Hi @byrallier
Thanks for posting in our business forum.
byrallier wrote
@Clive_A after upgraded it to this build with Early Access Omada SDN Controller_V5.13 Beta (Updated on Nov 21st, 2023), I lost my network traffic information. FYI, all graphs are now shown as 0 (only client information is working and valid)
What else? Is this all the information you could give to me? I am confused. Any description or screenshots to illustrate the issue? At least make yourself clear.
The issue is only the graph is missing. Other stuff work correctly?
- Copy Link
- Report Inappropriate Content
@Clive_A Other stuffs work correctly. Charts are loaded properly, the issue is information part is missing :) everything seems "0" on charts. I am not sure is it related 8411 or Omada Controller. If there is a way to test "traffic information" from an api endpoint of router, I can test it
If you need further information please let me know.
- Copy Link
- Report Inappropriate Content
WAN interface doesn't accept /252 saying my gateway address is a broadcast address. Changing to /248 works but obviously not
correct. Other routers have no issue
with /252, and its not just this version, all versions have same problem.
The MSS feature - where do I find this setting? I think I briefly see it appear on WAN page when loading, but then it disappears. I need to clamp MSS for use with Azure VPN connections over IPSec.
Also any plans to support AES256-GCM on IPsec?
- Copy Link
- Report Inappropriate Content
Hi @Crannog
Thanks for posting in our business forum.
Crannog wrote
WAN interface doesn't accept /252 saying my gateway address is a broadcast address. Changing to /248 works but obviously not
correct. Other routers have no issue
with /252, and its not just this version, all versions have same problem.
The MSS feature - where do I find this setting? I think I briefly see it appear on WAN page when loading, but then it disappears. I need to clamp MSS for use with Azure VPN connections over IPSec.
Also any plans to support AES256-GCM on IPsec?
/252 is only offering two valid IP addresses. You and your gateway. Is this expected to be normal? Your ISP requires to be /252?
Site view > Settings > Wired Networks > Internet > PPPoE > Settings.
No information I am aware of.
- Copy Link
- Report Inappropriate Content
Correct - single IP address for customer endpoint, and next hop gateway.
The MSS feature, we are using static IP not PPPoE? Can MSS be applied to IPsec tunnel directly? What is default MTU/MSS applied on IPSec tunnels?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 9251
Replies: 58