Hi @Fabfab74 

Thanks for posting in our business forum.

Fabfab74 wrote

  @Fabfab74 

Sorry for my search but I'm French, some terms are difficult for me

After the following configuration, your example Vlan 20/30 does not work. I would like to put the tables if you see an error

 

 

Make sure you reply to my post, not yours. I did not see your last reply.

The key problem is that your uplink is not tagged to be a trunk. See this KB in the Omada switch. I will later post this to the SOHO switch.

Here's the explanation:

Hi  @Fabfab74 

Fabfab74 wrote

  @Clive_A 

I'm afraid that if I change the setting in my vlan, it will bring down my entire network?

 

 

Er605 config on VLAN 20 :

 

 

Depends on what you do.

Admin VLAN should be applied to the network devices if you need them to be in admin VLAN. During thechanges, it will be disconnected for a while but will join back as soon as you place them in the correct and same VLAN.

Hi @Fabfab74 

Thanks for posting in our business forum.

Fabfab74 wrote

  @Clive_A 

In my config currently I have:

 

192.168.0.xxx LAN by default (all my omada devices)

 

Vlan 20: 192.168.20.xxx: the entire administrative network

 

Vlan 30: 192.168.30.xxx: the entire educational network

 

Vlan 40: reserved for extension

 

For the omada system I have not tagged any vlan. the swtichs and AP manage them alone I wouldn't want to disrupt the omada network

As long as they are located in the default VLAN where all your Omada devices are located, it does not affect the operation of the controller. Should be good.

From what you described, it just adds a new VLAN, and it does not impact the connectivity of the core network where all devices operate.