Beta Software ER8411 V1_1.1.1 Build 20231030 Beta Firmware for Omada Controller V5.13 (Released on Oct 31th, 2023)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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 @Clive_A
Regarding IPSec performance, it's not speed that's the issue but rather loading or maintaining sessions both HTTP and SSH. It can take 5 minutes to load a page which otherwise takes about 30 seconds maximum over OpenVPN. Likewise SSH, it won't drop the session but it hangs for some time then catches it self back up again.
If there are any specific tests you would like me to run please let me know and I'll be more than happy to do so. I've re-enabled the HTTP sensors on our network monitoring server to get a record of how often it's reporting a loss of connection.
Regarding the port forwarding, I think I've figured out what the issue might be.
The setup is:
Existing Rule 1:
Source: Any
Interface: All
WAN IP: Blank (Unable to specify IP xxx.xxx.xxx.194)
Source Port: 80
Destination IP: xx.xx.xx.2
Destination Port: 80
Protocol: All
Desired Rule 2:
Source: Any
Interface: All
WAN IP: xxx.xxx.xxx.195
Source Port: 80
Destination IP: xx.xx.xx.6
Destination Port: 80
Protocol: All
Is the issue because there isn't a WAN IP set on the existing record meaning it's applied to all IP Alias rather than just the interface IP of .194?
Many thanks
- Copy Link
- Report Inappropriate Content
Hi @Jamie_S
Thanks for posting in our business forum.
Jamie_S wrote
Hi @Clive_A
Regarding the port forwarding, I think I've figured out what the issue might be.
The setup is:
Existing Rule 1:
Source: Any
Interface: All
WAN IP: Blank (Unable to specify IP xxx.xxx.xxx.194)
Source Port: 80
Destination IP: xx.xx.xx.2
Destination Port: 80
Protocol: All
Is the issue because there isn't a WAN IP set on the existing record meaning it's applied to all IP Alias rather than just the interface IP of .194?
Many thanks
If there is no WAN IP specified, it will apply to all of them.
If you cannot specify it, have you checked if this WAN Alias working? Effective?
Pick up the specific port that shares the Alias on Interface, will it work?
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
Have had more opportunity to test this further.
So HTTP and HTTPS ports which were currently not set to a specific alias are now working on a specific alias (.195) as expected and do not show up on the other aliases confirming that it's working as expected in that respect. Omada still will not however allow for us to assign 80 and 443 to a different server using another alias (.196), still shows the same error that they are allocated on the interface already.
Many thanks
- Copy Link
- Report Inappropriate Content
Hi @Jamie_S
Thanks for posting in our business forum.
Jamie_S wrote
Hi @Clive_A
Have had more opportunity to test this further.
So HTTP and HTTPS ports which were currently not set to a specific alias are now working on a specific alias (.195) as expected and do not show up on the other aliases confirming that it's working as expected in that respect. Omada still will not however allow for us to assign 80 and 443 to a different server using another alias (.196), still shows the same error that they are allocated on the interface already.
Many thanks
The dev can provide a beta to address this. Let me know what you think.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Clive_A I installed this Beta firmware to my ER8411:
Hardware Version:
ER8411 v1.0
Firmware Version:
1.1.1 Build 20231030 Rel.66520
The feature I've been awaiting is the WAN Alias (multihomed IP on WAN ports). I was able to add a secondary IP, however when I went to the Transmission > NAT > Virtual Servers to configure a secondary web server behind the firewall listening to the WAN Alias IP, I received an error message saying the port was already configured for another service. Am I doing something wrong here? I would assume this is how I would configure a secondary web server to listen on a specific WAN Alias IP...?
Thanks,
-Aldo
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
darkknight_sdr wrote
@Clive_A I installed this Beta firmware to my ER8411:
Hardware Version:
ER8411 v1.0
Firmware Version:
1.1.1 Build 20231030 Rel.66520
The feature I've been awaiting is the WAN Alias (multihomed IP on WAN ports). I was able to add a secondary IP, however when I went to the Transmission > NAT > Virtual Servers to configure a secondary web server behind the firewall listening to the WAN Alias IP, I received an error message saying the port was already configured for another service. Am I doing something wrong here? I would assume this is how I would configure a secondary web server to listen on a specific WAN Alias IP...?
Thanks,
-Aldo
Do you have something similar to the #45? If so, this has been submitted to the dev, and plan to change this on V5.15.
- Copy Link
- Report Inappropriate Content
@Clive_A Yes it does appear to be the same issue as post #45. Any idea when we can give V5.15 a try?
Thanks,
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 9443
Replies: 58
Voters 1
