How Netgate 6100s handle VLANs & "Default VLAN"
-
Hey there,
I'm trying to understand how Netgate 6100s handle tagged & untagged traffic. I've read up on the VLAN documentation, but wasn't able to find an answer to my specific question, probably because I'm overthinking this a bit.
Do the discrete LAN ports on the 6100 act as a trunk port would on a switch? Say the LAN1 (igc0) interface is configured statically for 192.168.0.0/24. Then you create virtual interfaces for vlans 10 & 20 (192.168.10.0/24, 192.168.20.0/24, respectively) with igc0 as the parent interface. Does the router then treat 192.168.0.0/24 as the native vlan for that port, tagging any untagged traffic with the native vlan?
Say I connect an endpoint device directly to LAN1 and statically assign it an IP of 192.168.10.10, with a gateway of the VLAN 10 interface. What happens dot1q wise, if anything, to that traffic?
Appreciate anyone's input on this.
-
@vlandrummer said in How Netgate 6100s handle VLANs & "Default VLAN":
Do the discrete LAN ports on the 6100 act as a trunk port would on a switch?
The ports on the 6100 are no different than any other ethernet device -- they work on the vlan you assign to it. Not having a VLAN tagged on the interface means it's "native".
CORE is native.
The others are tagged on LAGG1. Substitute igc0-3 for your interface ports on the 6100.