ER707-M2 - Unable to connect to WAN through WAN/LAN3

I initially configured WAN/LAN3 to be a LAN port. I have tried to reconfigure it as a WAN with IPV4, Dynamic IP (no IPV6 configured) but when I select Connect on the interface it fails, no connection is made, no IP address is displayed. I have confirmed that the same network works without issue if it is connacted to WAN/LAN2.
I can return WAN/LAN3 to operate as a LAN port and it provides a connection and works without issue, when set to WAN it does not provide a LAN connection.
I previously had a ER605 and I was able to configure those ports without issue, so it seems unlikely to be operator error.
Any suggestions as to what is going on?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Clive_A I am unsure as to the underlying issue. I "forgot" the original router (605) I was replacing. I adopted the new router, using the workaround with logging into the management page of the unit in Standalone Mode and and manually setting SYSTEM> Controller Settings, Controller Inform URL, specifying the IP address of the controller to allow the adoption to take place. At this point I also set WAN/LAN3 to LAN mode with the presumption I could adjust it later once the unit had been adopted by the Omada controller software.
The unit was fully operational with the exception of if a port was changed from LAN ro WAN the modfied port would not connect to the WAN side equipment and did not obtain an ip address etc.
I was able to negociate some addtional network down time and today I :-
a) Forgot the ER707-M2 from the site
b) Did a reset on the unit using the hardware reset switch, pressed for 5+ seconds with power cycle.
c) Entered a new user and password
d) Excuted the adoption failure workaround
e) Re-adopted the unit
I was then able to change the ports from WAN/LAN2 onwards between WAN and LAN operation without issue.
- Copy Link
- Report Inappropriate Content
Are you facing the same issue as this?
If you have switched to a new product, it is best to readopt it. Or reboot the system after the adoption.
- Copy Link
- Report Inappropriate Content
@Clive_A I am unsure as to the underlying issue. I "forgot" the original router (605) I was replacing. I adopted the new router, using the workaround with logging into the management page of the unit in Standalone Mode and and manually setting SYSTEM> Controller Settings, Controller Inform URL, specifying the IP address of the controller to allow the adoption to take place. At this point I also set WAN/LAN3 to LAN mode with the presumption I could adjust it later once the unit had been adopted by the Omada controller software.
The unit was fully operational with the exception of if a port was changed from LAN ro WAN the modfied port would not connect to the WAN side equipment and did not obtain an ip address etc.
I was able to negociate some addtional network down time and today I :-
a) Forgot the ER707-M2 from the site
b) Did a reset on the unit using the hardware reset switch, pressed for 5+ seconds with power cycle.
c) Entered a new user and password
d) Excuted the adoption failure workaround
e) Re-adopted the unit
I was then able to change the ports from WAN/LAN2 onwards between WAN and LAN operation without issue.
- Copy Link
- Report Inappropriate Content
tda2806 wrote
@Clive_A I am unsure as to the underlying issue. I "forgot" the original router (605) I was replacing. I adopted the new router, using the workaround with logging into the management page of the unit in Standalone Mode and and manually setting SYSTEM> Controller Settings, Controller Inform URL, specifying the IP address of the controller to allow the adoption to take place. At this point I also set WAN/LAN3 to LAN mode with the presumption I could adjust it later once the unit had been adopted by the Omada controller software.
The unit was fully operational with the exception of if a port was changed from LAN ro WAN the modfied port would not connect to the WAN side equipment and did not obtain an ip address etc.
I was able to negociate some addtional network down time and today I :-
a) Forgot the ER707-M2 from the site
b) Did a reset on the unit using the hardware reset switch, pressed for 5+ seconds with power cycle.
c) Entered a new user and password
d) Excuted the adoption failure workaround
e) Re-adopted the unit
I was then able to change the ports from WAN/LAN2 onwards between WAN and LAN operation without issue.
Do you still have the backup before you change the WAN/LAN port?
The backup is when the issue exists. We need the original backup before we can locate the reason.
If you'd follow this up, please reply back and I will notify you how to send the backup.
- Copy Link
- Report Inappropriate Content
@tda2806 Same issue here, I can't get a WAN connection on the WAN 3-6 ports. I'm on 1.3.0 firmware from April.
- Copy Link
- Report Inappropriate Content
insomniac wrote
@tda2806 Same issue here, I can't get a WAN connection on the WAN 3-6 ports. I'm on 1.3.0 firmware from April.
There are two ways for you to go now.
1. Follow the instructions which is marked as the solution.
2. Provide a backup privately. We will require you to work with us in your problematic environment. A remote session may be needed.
This appears to be more of a problem when upgrading from an old controller or firmware, as the stored/synced config seems to be wrong on the router. We need more details and analysis before we can make a conclusion.
- Copy Link
- Report Inappropriate Content
@Clive_A happy to provide a backup privately if it helps
- Copy Link
- Report Inappropriate Content
@insomniac Just a quick note, I didn't pursue this further as I didn't have a backup of the non working, refusing to change LAN to WAN and WAN to LAN configuration. Once I got a working configuration that was stable I have left it alone, the old saying "let sleeping dogs lie" came to mind.
- Copy Link
- Report Inappropriate Content
insomniac wrote
@Clive_A happy to provide a backup privately if it helps
Since the beginning of 2025, we no longer create email tickets for the user. To assist and figure it out efficiently, we recommend submitting a support ticket via email.
Please include:
1. Your Forum ID;
2. Your community nickname;
3. A detailed description of the issue and result if I have suggested anything on the thread, and the troubleshooting steps you've taken in the subject line or body of your email.
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 314
Replies: 8
Voters 0
No one has voted for it yet.