NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ngappr
Apr 20, 2024Aspirant
WAX214v1: Trunking LAN port
Hi all, I have connected a WAX214v1 AP to a GS308EPP switch. Both have current firmware (WX214 2.1.1.3, GS308EPP 1.0.1.1). My idea was to have several SSID from the WAX and separate them via VLANs ...
schumaku
Apr 21, 2024Guru - Experienced User
There is no need to configure the default management VLAN and the as Tagged. Leave it as untagged, perfectly fine, and less prone to errors.
In case you really desire to operate the management VLAN for the WAX as Tagged, you first must define the management VLAN to the VLAN ID you want to use for the management VLAN - before defining the port for that VLAN as [T]agged. Otherwise confusion is predictable.
ngappr
Apr 21, 2024Aspirant
Hi schumaku,
thanks for your response.
My goal was to separate the WLAN SSID also within the wired network.
My understanding is, that if I do not configure trunking on the LAN port but simply within the WLAN portion, all traffic from the different WLAN SSIDs will go into the same (single) network that the LAN port (IP) lives in. This means the VLANs configured within the WLAN portion do not lead to an separation of those SSIDs within the wired network.
Is my understanding wrong?
When trunking works, configuring a VLAN ID for the management would be a logical next step. But as long as there is no trunking, it does not make much sense.
Kind regards
-ngappr
- schumakuApr 21, 2024Guru - Experienced User
ngappr wrote:
My goal was to separate the WLAN SSID also within the wired network.
That's perfectly OK.
ngappr wrote:
My understanding is, that if I do not configure trunking on the LAN port but simply within the WLAN portion, all traffic from the different WLAN SSIDs will go into the same (single) network that the LAN port (IP) lives in. This means the VLANs configured within the WLAN portion do not lead to an separation of those SSIDs within the wired network.
Not really. You don't have to force everything to a tagged connection. Correct, the management remains untagged for now, perfectly fine and easy to handle, or for example just to connect a normal computer. All the SSIDs can be tagged to your needs, to assign these to the VLANs by defining the port [T]agged by VLAN. Nothing that stops you from operating one network (and IP subnet) along with one or multiple tagged VLAN. A trunk does not imply that all traffic needs to be tagged, there seems to be a misunderstanding. Tagging is just to allow segregation.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!