VLAN and SSID Tagged / Untagged Connections

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

VLAN and SSID Tagged / Untagged Connections

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
VLAN and SSID Tagged / Untagged Connections
VLAN and SSID Tagged / Untagged Connections
2023-02-24 11:32:18 - last edited 2023-02-24 11:34:28
Hardware Version: V1
Firmware Version: ER7206 Beta 1.2.3 Build 20230208

Please advise if the connection method below is correct, as I am experiencing conflict DHCP behavior and the OC200 is not accessible from time to time via the cloud even though I have updated to the ER7206 to BETA 1.2.3 Build 20230208 Rel.68558 hoping to resolve the DHCP issues. 

 

The physical cables between the router, switch and EAP are through VLAN 10 - Tagged from ER7206 Port 4 (PVID10), tagged to the switch (PVID10) then untagged to the EAP. THe OC200 is also on VLAN10, untagged. All the other SSID VLANS are tagged on the switch and ER7206. I am only usign VLAN10 for the physciall connection and the OC200. 

 

Interfaces are made in Router and Switch as:
10.0.10.0/24 for VLAN10
10.0.6.0/24 for VLAN6
10.0.7.0/24 for VLAN7

10.0.3.0/24 for VLAN3

 

Management VLAN is default and is not set to VLAN10. Omada SDN is only being used for the EAPS, not the ER7206 or the switch. 

 

I have read conflicting information that the physical EAP ports for VLAN10 ont he switch should either be tagged or untagged. If I make them tagged, the EAP's stop working. Please advise what is the correct method of Tagged/Untagged ports for the physical connection of the EAP VLAN10 and Management VLAN setting for this setup via Omada SDN. 

 

Thanks in advance. This is such a great community. 

 

  0      
  0      
#1
Options
1 Reply
Re:VLAN and SSID Tagged / Untagged Connections
2023-02-24 14:36:14

  @gkonstantin 

1st I'm no expert, I generally do a fair bit of: try and test approach

you obviously must have some reason for why the whole lot is not using omada...

 

But if management vlan is default, that sounds like vlan 1 then , ie no tag.

If so then I'd try allowing vlan1 on the switch to the APs and to the oc200.

Probably going to need another subnet for that, with the switch, OC200, APs each having their IP address on.

 

See what that does.

  0  
  0  
#2
Options