Early Access ER707-M2 V1 1.3.0 Build 20250428 Pre-Release Firmware (Released on May 6th, 2025)
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
ER707-M2 V1
Release Notes
Version Info:
Adapted Model: ER707-M2 V1
Fully Adapted Controller Version: SDNC 5.15.20.X - Omada SDN Controller_V5.15.20.7 Pre-Release Firmware Windows
Minimum Firmware Version for Update: 1.2.2 Build 20240324 and above.
New Features:
1. Add support to SD-WAN.
2. Add support to Content Filter.
3. Add support to Virtual WAN.
4. Add support to Disable NAT.
5. Add support to Google LDAP.
6. Add support to LAN DNS.
7. Add support to FQDN/wildcards in ACL.
8. Add support to WAN DHCP Option.
Enhancement:
1. OpenVPN/Wireguard VPN: add support connecting to remote server/peer via domain name.
2. Optimized CPU utilization.
3. Optimized the time to enable the backup link.
4. Optimized booting time.
5. Optimized the time to dial up the WAN link.
6. Optimized the time to upgrade FW.
7. Optimized the time to generate an OpenVPN profile.
Bug Fixed:
1. Fixed the HTTPS redirection exception in standalone.
2. Fixed the static route for L2TP VPN doesn't take effect after re-enabling L2TP VPN.
3. Fixed the WOL exception when dropping some unknown unicast packets.
4. Fixed the issue that the manual ISP profile for USB modem cannot be saved
5. Fixed the issue that the PPTP VPN would disconnect occasionally
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
ER707-M2(UN)_V1_1.3.0_Build20250428
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
Arp 29th, 2025:
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
RBL wrote
@Clive_A since the latest upgrade of the ER707-M2 I have a strange issue. It happened last week and yesterday it happened again.
As I am using two internet lines, one via RJ45 (backup) and one via SFP (primary), therefor it took some time before I noticed the primary stopped working.
At first I thought there was a problem with the connection, but after contact with the provider we came to the conclusion there was no outage on the fiber channel. It just went offline.
Troubleshooting steps last week:
reboot router (ER707=M2 v1 1.3.0) --> no luck
reboot controller (OC200 V1 v1.35.7) --> no luck
Power cycle ER707-M2 --> SFP connection back online.
This was done last week. Yesterday, I was facing the same issue. tried the same steps and but before power cycling the router I made a screenshot of my WAN settings and there I noticed something strange, there was no <CONNECT> button visible in my WAN settings. See below:
Backup Connection:
Primary connection which fails:
I have no idea what triggered the issue. And the current workaround is power cycling the router.
Link down means the SFP or the peer terminal is not connected/active. This indicates more of a physical problem.
You wanna check:
1. Your fiber terminal if it is on or active while this happens.
2. When it is down, if you connect your computer or other device to the fiber terminal, will that give you Internet?
3. Simply reconnect the SFP on 707-M2, will it recover the link?
My assumption so far is that this might not be a problem with the firmware. If you wanna further test that, you could try the downgrade.
In the further investigation, Device Info may be needed. Will ask you for that if I need it.
- Copy Link
- Report Inappropriate Content
Clive_A wrote
You wanna check:
1. Your fiber terminal if it is on or active while this happens.
2. When it is down, if you connect your computer or other device to the fiber terminal, will that give you Internet?
3. Simply reconnect the SFP on 707-M2, will it recover the link?
My assumption so far is that this might not be a problem with the firmware. If you wanna further test that, you could try the downgrade.
In the further investigation, Device Info may be needed. Will ask you for that if I need it.
@Clive_A
1. Yes it is active
2. SFP is directly in the ER707-M2
3.a "normal" reboot cycle does not solve the issue, a power cycle of the ER707-M2 does.
- Copy Link
- Report Inappropriate Content
RBL wrote
Clive_A wrote
You wanna check:
1. Your fiber terminal if it is on or active while this happens.
2. When it is down, if you connect your computer or other device to the fiber terminal, will that give you Internet?
3. Simply reconnect the SFP on 707-M2, will it recover the link?
My assumption so far is that this might not be a problem with the firmware. If you wanna further test that, you could try the downgrade.
In the further investigation, Device Info may be needed. Will ask you for that if I need it.@Clive_A
1. Yes it is active2. SFP is directly in the ER707-M2
3.a "normal" reboot cycle does not solve the issue, a power cycle of the ER707-M2 does.
Point 3, you mean unplug it out, plug it back in, that does not recover it as well?
What does the log say about the WAN? The online detection or WAN-related logs.
- Copy Link
- Report Inappropriate Content
Clive_A wrote
3.a "normal" reboot cycle does not solve the issue, a power cycle of the ER707-M2 does.
Point 3, you mean unplug it out, plug it back in, that does not recover it as well?
What does the log say about the WAN? The online detection or WAN-related logs.
@Clive_A
No I mean hitting the reboot button of the router:
Removing the powerline and reinserting resolves the issue.
Checking the log does not show anything at all, not even the scheduled weekly reboot at monday morning (which should also trigger this event right?) (Maybe due to an upgrade of the controller to the latest version?):
- Copy Link
- Report Inappropriate Content
RBL wrote
Clive_A wrote
3.a "normal" reboot cycle does not solve the issue, a power cycle of the ER707-M2 does.
Point 3, you mean unplug it out, plug it back in, that does not recover it as well?
What does the log say about the WAN? The online detection or WAN-related logs.
@Clive_A
No I mean hitting the reboot button of the router:
Removing the powerline and reinserting resolves the issue.
Checking the log does not show anything at all, not even the scheduled weekly reboot at monday morning (which should also trigger this event right?) (Maybe due to an upgrade of the controller to the latest version?):
No logs about the WAN online detection? Strange enough if you say the WAN is down, but it does not detect that.
If you reconnect the fiber module instead of rebooting it, will it work?
What does the LED status when it is down and displayed as "disconnected"?
(Disconnected means the link is down. Either unplugged or local or peer port is disabled/down.)
- Copy Link
- Report Inappropriate Content
Clive_A wrote
If you reconnect the fiber module instead of rebooting it, will it work?
What does the LED status when it is down and displayed as "disconnected"?
(Disconnected means the link is down. Either unplugged or local or peer port is disabled/down.)
@Clive_A Will give it a try if it happens again. Currently it is running.
- Copy Link
- Report Inappropriate Content
after upgrading to 1.3.0 mDNS seems not working anymore... After rollback to 1.2.4 its working.
- Copy Link
- Report Inappropriate Content
mainkowitsch wrote
after upgrading to 1.3.0 mDNS seems not working anymore... After rollback to 1.2.4 its working.
Is that possible for you to Wireshark and locate this?
- Copy Link
- Report Inappropriate Content
Hi, i captured and analyzed the traffic with firmware 1.2.4 and 1.3.0
in 1.2.4 i could see mDNS responses
e.g.
192.168.10.1 → 224.0.0.251 MDNS Response with data from 192.168.30.x
however, after upgrade to 1.3.0 without changing anything in my config, these responses are missing.
after rolling back to 1.2.4 a second time... the mDNS responses reappeared.
- Copy Link
- Report Inappropriate Content
mainkowitsch wrote
Hi, i captured and analyzed the traffic with firmware 1.2.4 and 1.3.0
in 1.2.4 i could see mDNS responses
e.g.
192.168.10.1 → 224.0.0.251 MDNS Response with data from 192.168.30.x
however, after upgrade to 1.3.0 without changing anything in my config, these responses are missing.
after rolling back to 1.2.4 a second time... the mDNS responses reappeared.
Regardless the mDNS is working or not, it should send it anyway.
So, you are saying that the router or the port you mirrored cannot even see a packet coming to the router?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 5829
Replies: 40
Voters 1
