tagged vlan not working if same as native

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

tagged vlan not working if same as native

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
tagged vlan not working if same as native
tagged vlan not working if same as native
2022-05-03 09:09:16

i've recently moved into the omada ecosystem using the self-hosted controller.

I own EAP620HD & EAP225 AP's, and over the weekend i've added a pair of SG2210P (v5) switches, with a SFP port LACP LAG group between them.

 

i've also a pair of Netgear switches (GS724T & GS108Ev3), which the SG2210P's are replacing the GS724T.

 

620HD was connected to GS724T, EAP225 remains untouched on the GS108Ev3. 620HD is now connected to one of the SG2210P switches.

 

AP's are in mesh with identical SSID's broadcasted. 4 SSID's on different vlans. my primary SSID is on vlan1, as is all management interfaces.

 

the problem i'm seeing is that when the 620HD is connected to the SG2210P switches, vlan1 SSID does not work unless i untick vlan in the omada SSID config.

This was not a requirement of the 620HD on the GS724T, and also breaks the vlan1 SSID on the EAP225. So as a workaround I've copied the wifi group. one with SSID vlan1 configured (for EAP225), the other without (for 620HD).

 

SG2210P port profile is set to 'all' for the 620HD interface.

 

I don't think I've a way to prove things more, but i also have other ports (servers) running with 'all' profile to trunk the vlans without issues so it does appear specific to having a device both with an omada management IP and access/edge service on that device, using the same vlan.

 

based on the above, i've come to the conclusion that there's something incorrect with my SG2210P configuration. I cannot see anything i can change that would help so it's either a well hidden/non-obvious setting, or theres a bug i've encountered

  0      
  0      
#1
Options
2 Reply
Re:tagged vlan not working if same as native
2022-05-04 06:53:52

  @veehexx 

 

It is important to pay attention to the setting of egress rules, for example, the ports connected between switches should be set to tagged, and the ports connected between switches and EAPs should also be set to tagged.

  0  
  0  
#2
Options
Re:tagged vlan not working if same as native
2022-05-04 07:42:04 - last edited 2022-05-04 07:43:24

edit: sorry for external links; seems to be a known issue with the forum and it not submitting some posts correctly; cant embed screenshots directly so using imgur...

 

as far as i know, it is configured that way. trunks to carry everything on the appropriate interfaces.

vlan config:

https://imgur.com/z5M9dVf

 

'All' profile. since this is default, i cannot edit it.

 

 

https://imgur.com/GEOhw2T

 

STP enabled 'all' profile.

 

https://imgur.com/W2gxKSn

 

 

SG2210P switch1 (opnsense handles DHCP). as mentioned, port 9&10 SFP is LACP'd to the second 2210P switch. LAG1 group uses a 'all-STP' profile as screenshot above

 

https://imgur.com/KoQ0K8X

 

2nd SG2210P. 

 

https://imgur.com/EqWQF7M

 

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 174

Replies: 2

Related Articles