Hi @arife35,

The link to the firmware looked like a pre-release (beta) so it's not going to be visible by default; I doubt it's a firmware issue anyway.  I'm assuming that everything is factory defaulted (no vlans in use).  I think items 1-3 are all related.  Based on the information provided, I'm guessing that the gateway's default interface is not enabled on the ports connected to the switch and the 650.  If you can share more details about the er707's interface's configuration and the ports what ports your using for the modem, NAS, AP and switch it would help.

  @D-C How do I collect details of the ER707-M2's configuration? Is there a specific page / tab in the Omada Controller Web App that I should go to?

  @D-C 

Modem connected to WAN/Port 1 of the ER707-M2.

LAN/Port 2 of ER707-M2 connected to Port 1 of EAP650-Desktop

LAN/Port 4 of ER707-M2 connected to Port 1 of TL-SG105-M2 Switch

LAN/Port 5 of ER707-M2 connected to Synology NAS

LAN/Port 2 of the TL-SG105-M2 switch connected to Desktop PC

LAN/Port 3 of the TL-SG105-M2 switch connected to Port 1 of second EAP650-Desktop

@arife35, in the controller, once you select the site, look in Settings->LAN.  If this is all new, you should only see one interface.  Click the edit icon to see the config.

  @D-C 

I'm trying to use the ER707 in standalone mode, to better isolate the problem. The set up is: ISP's optical network router connected to WAN Port 1 of ER707, LAN Port 2 of ER707 direct connection to laptop

In case it makes a difference, the ONR is set to bridge mode. I still don't get any internet. Here are the screenshots from the ER707 settings page.

@arife35,

Try setting the Default Gateway in the LAN settings to 192.168.0.1

Default Gateway

 - (Optional) Enter the default gateway which is assigned by the DHCP server. It is recommended to enter the IP address of the LAN port.

Hopefully DHCP was working, but if you have a static IP on the laptop, make sure that the static address is using 192.168.0.1 for the Default Gateway setting.

  @arife35 

I am having the same issue with the omada 220 model set it up in standalone mode and it see's the tp-link ER707-M2 v1.20 and imports it the it goes into adopting mode and nothing works. It loses my wan connection and resets the lan from 192.168.88.1 to 192.168.0.1 on the  tp-link ER707-M2 v1.20 I have dhcp set in relay mode. There is no such option on the omada 220. So I turn dhcp off and set my lan Ip on it to 192.168.88.1, when I check connected device it reverts the ip to 192.168.0.1.

The problem is I have 27 containers all on static address with 1 year dhcp timeouts on anything not on static ip.

When I tested omada on my pc as local host it gave me none of these problems, So I am at a bit of a loss as to why it is happening now.

arife35 wrote

 

I've set up the hardware as per the above topology and installed the Omada software controller on my Synology NAS. I  can see the ER707-M2 in the Omada controller, which I have adopted. I've run into 3 issues, which may or may not be connected:

 

1. I cannot connect to the default SSID of either of the EAP650s. I can see the default SSID in my phone's WIFI section but it gets stuck while connecting.
2. There is no internet access for my Desktop PC.
3. I cannot see any of the other devices (ie. the TL-SG105-M2 switch or the APs) in the Omada controller, I only see the ER707-M2.

 

I've tried to update the firmware of the ER707-M2 (downloaded from https://community.tp-link.com/en/business/forum/topic/718232) but I received an error message on the Omada controller:

 

 

I've also tried resetting the ER707-M2 to factory settings, rebooting all of the hardware, etc. But nothing works.

 

Any help is most appreciated.