Home

Forums

Stories

Knowledge Base

Business Community > Routers > ER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

< Routers

Beta Software ER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

Beta SoftwareER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

Clive_A

2024-05-27 01:41:24 - last edited 2024-07-18 06:04:10

Posts: 5415

Helpful: 2590

Solutions: 1209

Stories: 0

Registered: 2023-06-09

ER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

2024-05-27 01:41:24 - last edited 2024-07-18 06:04:10

Tags: #Firmware Update

Model: ER706W

Hardware Version: V1

Firmware Version: 1.1.0 Build 20240523 (Beta)

This Article Applies to

ER706W(UN) V1 1.1.0_Build 20240523 (Beta)

This firmware supports the wired function of Controller 5.13.
If you use Standalone mode, please make sure that the firmware version is 1.0.4 Build 20240319 before upgrading, otherwise the firmware upgrade will fail.

Release Notes

New Feature/Enhancement

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 or unique 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 Intrusion Detection/Prevention

19. Add support for Deep Packet Inspection in Standalone mode.

20. Add support for enable/disable Flow Control in Controller mode.

21. Add support to modify the rate and duplex of the Ethernet port in Controller mode.

22. Add support for Multicast-to-Unicast Conversion of wireless part.

23. Add support for Client Rate Limit for SSID.

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

ER706W(UN) V1_1.1.0_Build 20240523 (Beta)

Notes:

(1) The above firmware is applied to ER706W V1.

(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.
(4) If you use Standalone mode, please make sure that the firmware version is 1.0.4 Build 20240319 before upgrading, otherwise the firmware upgrade will fail.

Additional Information

All feedback is welcome, including letting us know about successful device upgrades.

If somehow you encounter an issue during or after the ER706W 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 ER706W 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

May 27th, 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]

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.

10 Reply

kogan

LV2

2024-06-02 12:13:53

Posts: 81

Helpful: 15

Solutions: 3

Stories: 0

Registered: 2022-01-15

problems with custom dyndns after upgrade

2024-06-02 12:13:53

@Clive_A

Hello

I use freedns.afraid.org for my dyndns.

After upgrading my ER706W to 1.1.0 Build 20240523 Rel.71270(4555) AND linux controller to V5.14.20 - ddns is broken, since it is sending out only the real WAN IP (which is IP Adress of Fritzbox) and not the public internet IP as it was before the upgrade.

Does someone have same problem? Unfortunately I upgraded both simultanous so I can not say, is it router upgrade or controller upgrade issue.

ps: before the "upgrade" everything worked well.

ps2: the problem with ER706W that is limited to 100Mbit after reboot on WAN2 port still exists. After rebooting again, 1Gbit is working again.

Thanks

MR.S

LV5

2024-06-02 12:58:02

Posts: 2083

Helpful: 754

Solutions: 260

Stories: 0

Registered: 2018-08-17

problems with custom dyndns after upgrade

2024-06-02 12:58:02

@kogan

I did a test here, same router same firmware. connected it behind another router, router gives correct wan ip.
Controller Version: 5.14.20.9
I use no-ip as ddns provider-

kogan

LV2

2024-06-02 13:20:51

Posts: 81

Helpful: 15

Solutions: 3

Stories: 0

Registered: 2022-01-15

problems with custom dyndns after upgrade

2024-06-02 13:20:51

@MR.S

thank for feedback. No-IP service is implemented to the omada. Afraid-DNS not, so only custom dynDNS is possible.... if you could test "custom" DNS on your hardware please?

kogan

LV2

2024-06-02 13:25:42

Posts: 81

Helpful: 15

Solutions: 3

Stories: 0

Registered: 2022-01-15

problems with custom dyndns after upgrade

2024-06-02 13:25:42

@MR.S

I solved the issue on my own:

Afraid DNS custom update URL is:

http://[USERNAME]:[PASSWORD]@freedns.afraid.org/nic/update?hostname=[DOMAIN]&myip=[IP]

that was always working.

I deleted everything after [domain]

http://[USERNAME]:[PASSWORD]@freedns.afraid.org/nic/update?hostname=[DOMAIN]

and NOW the public IP is coming correctly.

MR.S

LV5

2024-06-02 13:29:37

Posts: 2083

Helpful: 754

Solutions: 260

Stories: 0

Registered: 2018-08-17

problems with custom dyndns after upgrade

2024-06-02 13:29:37

@kogan

I have no custom ddns to test, my bee tp-link can help you with that.

I did a test here as I was a bit scared by what you wrote this function is important to me. but with no-ip it still works.

MR.S

LV5

2024-06-02 13:31:03

Posts: 2083

Helpful: 754

Solutions: 260

Stories: 0

Registered: 2018-08-17

problems with custom dyndns after upgrade

2024-06-02 13:31:03

@kogan

So glad that it worked out

Rephot

LV1

2024-07-15 06:20:12

Posts: 2

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2024-02-15

Re:ER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

2024-07-15 06:20:12

@Clive_A

Not sure if this is an overarching issue or expected functionality however i have an issue with port forwarding with this firmware loaded

It seems when selecting Source IP - Any, all internal traffic to the port-forward destination will route via the WAN IP

For example:

I have 2 VLANs with no ACLs in place

If I have port forwarding OFF I can connect via ServerLANIP:Port from ClientLAN and wireshark shows the connection with the source IP as ClientLANIP

However if i turn ON the port forwarding I can still input the ServerLANIP:Port and connect however wireshark shows the source IP as WANIP

Wireshark is captured at the destination

Clive_A

2024-07-17 02:53:43

Posts: 5415

Helpful: 2590

Solutions: 1209

Stories: 0

Registered: 2023-06-09

Re:ER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

2024-07-17 02:53:43

Hi @Rephot

Thanks for posting in our business forum.

Rephot wrote

@Clive_A

Not sure if this is an overarching issue or expected functionality however i have an issue with port forwarding with this firmware loaded

It seems when selecting Source IP - Any, all internal traffic to the port-forward destination will route via the WAN IP

For example:

I have 2 VLANs with no ACLs in place

If I have port forwarding OFF I can connect via ServerLANIP:Port from ClientLAN and wireshark shows the connection with the source IP as ClientLANIP

However if i turn ON the port forwarding I can still input the ServerLANIP:Port and connect however wireshark shows the source IP as WANIP

Wireshark is captured at the destination

NAT hairpin. Do you experience a problem with this?

Rephot

LV1

2024-07-17 03:37:16

Posts: 2

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2024-02-15

Re:ER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

2024-07-17 03:37:16

@Clive_A

From what i understand hairpinning is when I can connect from an internal IP to my WANIP and get routed via port-forward back to an internal IP.

In my case it is internal to internal getting routed via wan. It indeed sounds like it is being caught by the hairpin but I believe it shouldn't

Curiously it only happens in inter-vlan routing, whereas when the 2 IPs are in the same VLAN it works as i would expect

I'm having client identification issues since it keeps routing everything via my WAN

#10

Clive_A

2024-07-17 08:24:39

Posts: 5415

Helpful: 2590

Solutions: 1209

Stories: 0

Registered: 2023-06-09

Re:ER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

2024-07-17 08:24:39

Hi @Rephot

Thanks for posting in our business forum.

Rephot wrote

@Clive_A

From what i understand hairpinning is when I can connect from an internal IP to my WANIP and get routed via port-forward back to an internal IP.

In my case it is internal to internal getting routed via wan. It indeed sounds like it is being caught by the hairpin but I believe it shouldn't

Curiously it only happens in inter-vlan routing, whereas when the 2 IPs are in the same VLAN it works as i would expect

I'm having client identification issues since it keeps routing everything via my WAN

It is the NAT hairpin(AKA loopback). Expected behavior.

#11

Beta Software ER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

Beta Software ER706W V1_1.1.0 Build 20240523 Beta Firmware for Omada Controller v5.13 (Released on May 27th, 2024)

This Article Applies to

Release Notes

New Feature/Enhancement

Firmware Download

Before the Upgrade

Firmware Download Link

Additional Information

Update Log

May 27th, 2024:

Recommended Threads

Information

Voters 1

Tags