Hi @Burdarper 

Thanks for posting in our business forum.

Change this.

Hello @Clive_A ,

thanks a lot for reading through my topic.

 

However I cannot find anything similar to your image in my ER707-M2.
Could you please tell me, where this pictures is taken ? My LAN / VLAN Settings are looking different.

Furthermore: From which point on should the router be adopted in Omada ?
 

 

  @Burdarper 

 

Clive provided you screenshot from Omada controller.

You are providing screenshot from Standalone Router config page.

 

You should go to your controller, prepare the configuration there (configure non-existing - yet - router, it's LAN, WAN etc) and ther adopt the actual device. So the moment it receive settings from Omada controller, those are already Pre-configured.

 

Do you have controller at all? It is software version (self hosted) or hardware (oc200/300)?

 

Best Regards

RR

  @RaRu   @Clive_A 

Hello All,

thanks a lot for your answers and apologize my late response.

 

Shortly after reading and implementing your answer, I unfortunately had a cable break in the building's fiber optic cable.
As it is in a very rural location, the system was almost constantly offline. I subsequently purchased a Zyxel NR7302 5G router to establish a somewhat unstable internet connection via WAN6-Port on the ER707-M2.

The fiber optic connection has still not been repaired by the provider, so I can actually move the hardware while the system is running:

 

Regarding your question: yes of course I use Omada.

Since something has changed in the meantime, I will now explain the initial situation again and the problem that I have not yet been able to solve:

 

The old setup consisted of:

 

Router: Fritz.box 7490

Switch(POE) GS728TPV2

9 TP-Link Omada APs

There were 2 nets : VLAN1 (Default) and VLAN20(Guest): The guest network is tagged on the switchports linked to the Omada-AP ports in order to provide guest Wifi managed via Omada.
Since Fritzbox is not able to use VLANs I used its default guest LAN Port4 als guest-network uplink to a VLAN20 untagged port on the netgear switch.

The Omada controller is running in software version on a Proxmox server. (both in VLAN1 of course) .

 

Due to the fact that Fritzbox is not VLAN capable and that I really like the Omada management software I wanted to get rid of the Fritz.Box and the Netgear switch; replacing everything with Omada-capable hardware.

 

So I bought : 
 

Gateway: ER707-M2 v1.20
(Main)Switch: SG3428X-M2 v1.20

POE Switch: SG2210XMP-M2 v1.0

and created the following VLAN Interfaces:

 

1_old_LAN(Default)

192.168.178.1 / 24

 

20_old_guest

192.168.179.1 / 24

 

13_Heim

192.168.13.1 / 24

 

23_Gast

192.168.23.1 / 24

 

33_IOT

192.168.33.1 / 24

 

43_SERVER

192.168.43.1 / 24

 

99_MGMT

192.168.99.1 / 24

 

 

So the target architecture should be:
Omada Gateway/Switches and AP should have a dedicated management network VLAN99. 
Existing devices in VLAN1 should be transferred to the respective VLANS in the new structure.

I managed to put all Omada devices in VLAN99.
However as you can see, the Gateway still has its IP adress from VLAN1(default) :


(Don´t mind those offline Wifi-APs, they are not that important currently since everything´s mostly offline.I will fix later later on.)

And whatever steps I made I lose Gateway and or the omada controller in VLAN1.

Currently the uplink from the mainswitch to the gateway is working with switchprofile (all) on the uplink port which surely sets PVID VLAN1 (default)
The respective uplink for on the Gateway is set to "old_lan"-VLAN1.

I assumed that creating a switch-profile using VLAN99 as native/untagged VLAN, while having all other nets tagged and assign this "uplink-profile" to the switch port while changing a free port on the gateway to PVID-VLAN99 would solve this and let the gateway take the 192.168.99.1. (after removing the cable-patch from the existing (1) <-> (1) connection to (99) <-> (99).

But after doing that Omada is not accessible anymore and the gateway is not changing to 192.168.99.1. 

 

 

I would like to ask you to suggest a way to bring the gateway into the VLAN99.
Does VLAN1 have to remain default? I have not found a way to change the default lan setting..

Furthermore, it would of course be important that the Omada controller remains accessible in VLAN1.

I would then subsequently move the Omada controller (together with Proxmox and the other servers) to VLAN 43.

When everything has been shifted VLAN1 and 20 should be deleted.

P.S.: Are there any 5g Outdoor modems from TP-link (Omada) ? (haven´t found any. prefereable with external antennas ;-) 

Many thanks in advance for your time and efforts.


Greetings

  @GRL 

thanks a lot for your reply, I will answer your questions/remarks one by one:

1. Gateway is not and can not be a DHCP client - you HAVE to specify its IP addresses in settings > LAN (where indicated on Clives screenshot)

This is understood, and the settings were already made like this :

Settings -> Networks::

 

Each network is set up in the same way.
The third octet of the IP address always corresponds to the VLAN and xxx.1 is always set as the gateway.

Furthermore, DHCP is activated in each network from xxx.xxx.xxx.140 - 240 and all LAN interfaces are activated.

So as an example you may see the 99_MGMT in detail :

2. The routers network ports are also not controlled by switch profiles, they must be manually adjusted by

 

1) assigning LANs to router ports, same screen as setting the LAN IP for each interface

This was also already done before:
Settings-> Devices-> Gateway-> Ports

LAN2 is set to VLAN1 (I guess the other LAN ports activated in LAN settings are then counted as tagged(?)



Port 3 then was configured to have untagged VLAN99 assuming this would change the gateways IP adress:



The main switch of course has been prepared the same way ( Current uplink port 24 , VLAN1untagged, rest tagged (default profile (ALL)   //   future uplink Port 23, VLAN99untagged, rest tagged.


 

2) settng PVIDs on each port as required - you cannot set port PVIDs until the router is adopted though because you cannot access the necessary config screen until its in connected status on the device page

ok this is also understood and done as you can see in the pictures above.
My assumption was, that if I unpatch GW_Port2 - SwitchP24 and patch GW_Port3 - SwitchP23, that the gateway would take over the IP Adresse 192.168.99.1

But instead I lose the connection to Omada and all VLAN1 I guess.

Right after patching back OMada is reacheable again and GW remains at 192.168.178.1

 

 

Hello all, 

 

In the meantime I discovered, that for whatever reason the gateway is now assigning 192.168.99.xxx adresses to Wifi-clients in VLAN1 . ( This should be 192.168.1.xxx ) .

I changed the IP-Address of the omada management from 192.168.43.34 ( from 192.168.1.34 ) .

The Portal was working fine afterwards.
Then I again decided to patch from (GW Port_2 / VLAN1 <-> Switch 1/28 / VLAN1)   to  (GW Port_3 / VLAN99 <-> Switch 1/27 / VLAN99 +all nets tagged)  and give it more time.

The omada portal stays accessible and all clients are still able to reach internet, however Omada lost all its devices and is not recovering




I hope that someone here would have an idea how to handle this situation. (WLAN1 (default) getting IPs from net 99 and Omada behaving like that.

For now I did not power-off - on (reboot ) the Gateway. Maybe it only changes its adress whiel beeing rebooted I may try that after finishing work today

  @Burdarper

Burdarper wrote

Hello all, 

 

In the meantime I discovered, that for whatever reason the gateway is now assigning 192.168.99.xxx adresses to Wifi-clients in VLAN1 . ( This should be 192.168.1.xxx ) .

I changed the IP-Address of the omada management from 192.168.43.34 ( from 192.168.1.34 ) .

The Portal was working fine afterwards.
Then I again decided to patch from (GW Port_2 / VLAN1 <-> Switch 1/28 / VLAN1)   to  (GW Port_3 / VLAN99 <-> Switch 1/27 / VLAN99 +all nets tagged)  and give it more time.

The omada portal stays accessible and all clients are still able to reach internet, however Omada lost all its devices and is not recovering




I hope that someone here would have an idea how to handle this situation. (WLAN1 (default) getting IPs from net 99 and Omada behaving like that.

For now I did not power-off - on (reboot ) the Gateway. Maybe it only changes its adress whiel beeing rebooted I may try that after finishing work today

Omada Controller is supposed to stay in the same subnet as other devices.

If they cannot communicate for 10 minutes, they will turn into a disconnected status.

In your pic, they are not in the same VLAN. That's the reason. There are other guides about how it works.

What should I do when the Omada Controller (V4) fails to adopt the devices?