NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
S350 GS308T - Not getting VLANs correctly
Hello, recently I purchased S350 Smart Switch (GS308T) for home usage. This is my first managed switch and main reason for purchasing it was to better manage my homelab and learn about VLANs.
I created a VLAN from my pfSense router (which is a VM) and put some FW rules. This VLAN has an ID of 96. The same VLAN is created on the switch (refer to screenshot below):
Here is a screenshot of the VLAN Membership page:
Port 8 is connected to the pfSense and port 3 is connected to my company provided computer.
Problem is: According to Netgear's documentation:https://kb.netgear.com/31026/How-to-configure-a-VLAN-on-a-NETGEAR-managed-switch
"Ports which connect to client devices such as PCs should be marked as untagged (U). This is also known as an access port."
In my case, this does not work. When I set the port as untagged (U), the Windows 10 Pro 64x based laptop cannot get connection to anything. I've tried rebooting it, disabling the Ethernet adapter, setting manual IPs and DHCP, but nothing works. With setting the port as tagged (T), it works just like a charm.
Question is, why in my case this does not work? As far as I'm aware, Windows should not be VLAN aware (without additional modifications?).
Thank you.
scotrod wrote:
Problem is: According to Netgear's documentation:https://kb.netgear.com/31026/How-to-configure-a-VLAN-on-a-NETGEAR-managed-switch
"Ports which connect to client devices such as PCs should be marked as untagged (U). This is also known as an access port."
In my case, this does not work. When I set the port as untagged (U), the Windows 10 Pro 64x based laptop cannot get connection to anything. I've tried rebooting it, disabling the Ethernet adapter, setting manual IPs and DHCP, but nothing works. With setting the port as tagged (T), it works just like a charm.
Question is, why in my case this does not work? As far as I'm aware, Windows should not be VLAN aware (without additional modifications?).
The documentation is correct For an untagged port, and you want the port on VLAN 96 [U]ntagged, you have to set the PVID to 96, too - otherwise the untagged incoming frames will be sent to the VLAN 1, the default PVID. Just setting the port to [U]tagged for the VLAN 96 alone isn't sufficient.
Scroll down a little bit until you get the "Configure port PVID settings for untagged ports:" section.
Worth reading? S350 Series 8-Port Gigabit Ethernet Smart Switch Models GS308T and GS310TP User Manual - Configuration Examples - VLAN Configuration Examples p.334/335
The KB entry referred above applies to the Managed Switches and almost all VLAN capable switches.
10 Replies
scotrod wrote:
Problem is: According to Netgear's documentation:https://kb.netgear.com/31026/How-to-configure-a-VLAN-on-a-NETGEAR-managed-switch
"Ports which connect to client devices such as PCs should be marked as untagged (U). This is also known as an access port."
In my case, this does not work. When I set the port as untagged (U), the Windows 10 Pro 64x based laptop cannot get connection to anything. I've tried rebooting it, disabling the Ethernet adapter, setting manual IPs and DHCP, but nothing works. With setting the port as tagged (T), it works just like a charm.
Question is, why in my case this does not work? As far as I'm aware, Windows should not be VLAN aware (without additional modifications?).
The documentation is correct For an untagged port, and you want the port on VLAN 96 [U]ntagged, you have to set the PVID to 96, too - otherwise the untagged incoming frames will be sent to the VLAN 1, the default PVID. Just setting the port to [U]tagged for the VLAN 96 alone isn't sufficient.
Scroll down a little bit until you get the "Configure port PVID settings for untagged ports:" section.
Worth reading? S350 Series 8-Port Gigabit Ethernet Smart Switch Models GS308T and GS310TP User Manual - Configuration Examples - VLAN Configuration Examples p.334/335
The KB entry referred above applies to the Managed Switches and almost all VLAN capable switches.
Yes, this worked. Thank you!
If I may use the comment, why would this setup works when the port is set as "tagged"? I understand the logic of working when the port to my laptop is set as untagged - Windows does not tag the packets, so the switch is expecting untagged packets, and depending of my setup, it tags them with the correct VLAN ID - like right now.
But previously it worked just fine while the port was set as "tagged", however the traffic coming from the Windows laptop were not tagged.
scotrod wrote:
But previously it worked just fine while the port was set as "tagged", however the traffic coming from the Windows laptop were not tagged.
Whatever was in place and active before. Was the data path flowing over a switch which has done the proper tagging for example? As you say, normally a Windows client does not tag the traffic on it's own. Or you had configured the Windows network adapter for explicit tagging? Or the port was connected to another trunk port, probably configured for a trunk, for example on your security appliance?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
