VLAN Question
-
*** Welcome to pfSense 2.3.1-RELEASE-p1 (amd64 full-install) on pfSense ***
WAN (wan) -> em0 -> v4/DHCP4: 172.16.1.32/24
LAN (lan) -> em1 -> v4: 192.168.1.1/24
VLAN10 (opt1) -> em1_vlan10 -> v4: 192.168.2.1/24
VLAN20 (opt2) -> em1_vlan20 -> v4: 192.168.3.1/24
VLAN30 (opt3) -> em1_vlan30 -> v4: 192.168.4.1/24If you add VLANS to an existing interface as above does it trunk everything and the 192.168.1.0/24 interface would be native and anything else would be tagged ?
-
The LAN interface works just like it would without the VLANs. The VLANs are transmitted on the same wire but the ethernet frames have the appropriate VLAN tags in them. I'm not sure what you mean by "trunking" though.
-
Thanks.
Trunking is carrying multiple vlans down a single interface.
-
I'm used to "trunk ports" that are switch ports that carry only tagged traffic, what you're referring to as "trunking" is the basic use of VLANs, just more than one VLAN on an interface.
-
@kpa:
The LAN interface works just like it would without the VLANs. The VLANs are transmitted on the same wire but the ethernet frames have the appropriate VLAN tags in them. I'm not sure what you mean by "trunking" though.
Cisco (and a few other vendors) uses the term "trunking" to refer to an interface that carries VLAN tagged frames from multiple VLANs, which I think is were the confusion is coming from.
