I'm running a couple of VLANs via a Firewalla Purple and a Netgear GS724T, a pretty straightforward setup with default (VLAN1) for most things and then Guest, VoIP and IoT VLANs to isolate potential problem devices. However I've run into a problem with VLAN1, I was expecting to make the switch port on which it's connected to the Purple, port 1, a trunk/tagged port, 'T' in Netgear terms, but doing so knocks VLAN1 traffic offline. It's only when I make port 1 an untagged port, 'U' in Netgear terms, that everything works normally.
Just to clarify, in VLAN1 I've got port 1 marked as 'U', in VLAN-Guest, VLAN-VoIP, and VLAN-IoT I've got port 1 marked as 'T'. I assume the issue above occurs because anything not on the Guest, VoIP, and IoT VLANs is untagged and I'd need to explicitly tag it for VLAN1 if VLAN1 port 1 was a 'T' port? Since I've currently got VLAN1 port 1 marked as a 'U' port and things seem to be working as expected, is there any downside to leaving it like this?
Please sign in to leave a comment.