Hi @MarekZegarek 

Thanks for posting in our business forum.

1. MR is not an Omada router. I assume that's the home router? 

They don't support Multi-nets NAT. And it would waste your time doing this setup. You won't be able to get Internet in the end.

2. You should not change the default IP address of VLAN 1. If VLAN 1 has been changed, you will lose the connection to the controller. And it enters the heartbeat missed and disconnected status eventually.

Details are explained:

How to Set Up VLAN Interface on the Omada Router

Hi @MarekZegarek 

Thanks for posting in our business forum.

MarekZegarek wrote

Hi @Clive_A , thanks for your answer. 

 

MR200 is a TP-Link router with GSM modem, in my scenario I use it to simply deliver Internet, nothing more. I want my switch TL-SG3428X to handle whole network traffic. 

So I believe that scenario that is described in article that I linked perfectly fits my requirements, whereas MR200 do simply static routing to TL-SG3428X and vice-versa. 

And the thing is that it actually works! I mean, I have internet via my wireless and cable (both are withing VLAN3 from mentioned scenario). Omada controler and EAP's are also on VLAN3 and I can access them all. The only thing that is missing is that TL-SG3428X gets in status 'Disconnected' when I move Controler OR200 from 'Default' port to 'VLAN3', somehow Controler can't reach TL-SG3428X?? So with this setup I can't no longer manage TL-SG3428X as it can't be reached by OR200 (and I can't manage it via web interface as it's already linked to Omada). 

 

Maybe there is simple alternative here, like put only Controler OC200 on 'Default' port, but woulr EAP's be able to reach OC200?

 

Maybe other question, my main intention is to totally separate MR200, meaning treat it only as Internet provider, no DHCP, nothing, all trafic should go to my network managed fully by Omada. Maybe there is some other configuration method? At this moment I don't see bigger added value by buing extra router from Omada that will be acting as gateway. 

 

I read article that you shared, there are multiple scenarios described there, even one of them is linking to article that I was using. 

 

Thanks! 
Marek

You are free to cascade, but we always recommend avoiding double-NAT.

About the OC200, this thing is working based on a simple rule that it has to follow the same subnet. Which means, same VLAN and the subnet gotta be the same because it sends the broadcast(discovery) packets to the subnet.

  @MarekZegarek 

controller can only manage a switch on the switches management vlan.

If switch management vlan is not vlan3, it will not be able to adopt or configure it.

It doesnt matter what vlan is used for management - can be any vlan ID and any private IP range, but all the devices must have their management vlan set to the same - possibly in standalone first before adoption then ensuring that once adopted, the management vlan is re-applied in the controller per device.  Otherwise it gets messy having to find and change controller IP with the discovery tool.

The easiest way i have foind if you want a different management vlan is to set everything up on default 1, then slowly working you way up the chain (device furthest away from controller in terms of how many switches it has to go through) change its management VLAN and IP range.  It will then go disconnected.  Do this one at a time per device all the way up the chain, leaving the controller last.  Then, change the controller management vlan and IP.  Everything should be found and readopted after.

  @MarekZegarek 

Do you mean you cant reserve the switches address in the controller on vlan3 dhcp pool?

Yeah, for some reason you cant do this in the natural way for omada devices - BUT, you can manually add its MAC and the IP address you want it on to DHCP reservations just in case you ever have to factory reset the switch or whatver, it will come back up with its intended IP.

My personal preference is to set all network hardware as statics, and add them manually to DHCP reservation as well.  That way you can always be sure that they get the right IP and that IP is never given to anything else.