WAX214v1: Trunking LAN port

Question

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 also within the wired network.Seemingly the WAX214 is not able to do VLAN trunking on the LAN port. I did not see something in the configuration UI.&nbsp;Is it correct, that WAX214v1 cannot do VLAN trunking at the LAN port?&nbsp;The VLAN IDs which I can configure for the SSIDs seemingly are only to separate the WLAN SSID from each other within the WAX214.How can the 4 SSIDs that the WAX214 is capable to distribute be separeted in the wired LAN. Currently I am out of ideas.Any help is welcome.If the WAX214 is not the right product for this, which AP would be?&nbsp;Kind regards and thx in advance-ngappr

schumaku · Answer

Hello&nbsp;ngappr&nbsp;
&nbsp;
ngappr&nbsp;wrote:
Is it correct, that WAX214v1 cannot do VLAN trunking at the LAN port?

No, wrong impression.
&nbsp;
ngappr&nbsp;wrote:
If the WAX214 is not the right product for this, which AP would be?

Of course it's possible to map any of the four SSID entries to any VLAN ID.
&nbsp;
Disputable if the WAX214/218 is intuitive enough on the subject, it does allow what you want to configure.
&nbsp;
Go to the Wireless Settings, and [Edit] the SSID entry you want to configure mapped to a VLAN:&nbsp;
&nbsp;

&nbsp;
The&nbsp;NETGEAR WiFi 6 AX1800/AX3600 Dual Band PoE/PoE+ Access Points, WAX214 and WAX218&nbsp;User Manual does show this on p.51:

&nbsp;
Regards,
-Kurt.
&nbsp;
PS. Not a secret, there is an issue in the WAX214&nbsp;2.1.1.3: In case you tick the [Guest Network] and/or use OWD Security, the VLAN config is greyed and can't be enabled, and only the default VLAN is available:
&nbsp;

&nbsp;
Bug report filed months ago, ...

ngappr · Answer

Hi schumaku,&nbsp;thanks for your detailed response.I found this possibility within the GUI. The VLAN IDs which I can configure there seem to lead to an isolation of the SSIDs from each other. To have 4 different VLAN IDs (for four SSIDs) the be reachable from the wired LAN -to my impression- the LAN port needs to be in Trunk mode (so several VLAN IDs).&nbsp;I found no place within the WAX214 GUI where I could configure the LAN port to be a Trunk.&nbsp;When I configure the port on the GS308EPP switch where the WAX214 is connected to, to be a trunk, I cannot reach the WAX any more.&nbsp;Further help would be very much appreciated.Thanks for your assistance.&nbsp;-ngappr

schumaku · Answer

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.
&nbsp;
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 · Answer

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?&nbsp;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.&nbsp;Kind regards-ngappr

schumaku · Answer

ngappr&nbsp;wrote:
My goal was to separate the WLAN SSID also within the wired network.

That's perfectly OK.
&nbsp;
ngappr&nbsp;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.&nbsp; 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.
&nbsp;
&nbsp;
&nbsp;

Forum Discussion

WAX214v1: Trunking LAN port

5 Replies

Related Content

GS108Ev3 Port Trunking

Trunk Port

Port Trunking

GS305E Trunking tagged and untagged vlans

Port Trunking auf Switch GS748TS

NETGEAR Academy

ProSupport for Business