vconfig(8) [debian man page]

VCONFIG(8)						      System Manager's Manual							VCONFIG(8)

NAME

       vconfig - VLAN (802.1q) configuration program.

SYNOPSIS

       vconfig [lots of long options]

DESCRIPTION

       The  vconfig program allows you to create and remove vlan-devices on a vlan enabled kernel. Vlan-devices are virtual ethernet devices which
       represents the virtual lans on the physical lan.

OPTIONS

       add [interface-name] [vlan-id]
	      Creates a vlan-device on [interface-name]. The resulting vlan-device will be called according to the nameing convention set.

       rem [vlan-device]
	      Removes the named vlan-device.

       set_flag [vlan-device] 0 | 1
	      When 1 (the default since 2.6.18), ethernet header reorders are turned on.  Dumping the device will  appear  as  a  common  ethernet
	      device  without  vlans.  When  0	however, ethernet headers are not reordered, which results in vlan tagged packets when dumping the
	      device. Usually the default gives no problems, but some packet filtering programs might have problems with it.

       set_egress_map [vlan-device] [skb-priority] [vlan-qos]
	      This flags that outbound packets with a particular skb-priority should be tagged with the particular  vlan  priority  vlan-qos.  The
	      default vlan priority is 0.

       set_ingress_map [vlan-device] [skb-priority] [vlan-qos]
	      This  flags  that  inbound  packets  with the particular vlan priority vlan-qos should be queued with a particular skb-priority. The
	      default skb-priority is 0.

       set_name_type VLAN_PLUS_VID | VLAN_PLUS_VID_NO_PAD | DEV_PLUS_VID | DEV_PLUS_VID_NO_PAD
	      Sets the way vlan-device names are created. Use vconfig without arguments to see the different formats.

       NOTES  VLAN will use Broadcom's NICE interface when the network device supports it. This is necessary, since usually the hardware of  these
	      devices  already	removes the vlan tag from the ethernet packet. The set_flag option on vlan-devices created on such a physical net-
	      work device will be ignored.  Dumping the network-device will show only untagged(non-vlan) traffic,  and	dumping  the  vlan-devices
	      will only show traffic intended for that vlan, without the tags.

FILES

       /proc/net/vlan/config
       /proc/net/vlan/[vlan-device]

SEE ALSO

       ip(8), ifconfig(8)

AUTHORS

       This manual page was written by Ard van Breemen <ard@kwaak.net>
       The vlan patch is written by Ben Greear <greearb@candelatech.com>

																	VCONFIG(8)

VLAN(4) 						   BSD Kernel Interfaces Manual 						   VLAN(4)

NAME

     vlan -- IEEE 802.1Q VLAN network interface

SYNOPSIS

     To compile this driver into the kernel, place the following line in your kernel configuration file:

	   device vlan

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   if_vlan_load="YES"

DESCRIPTION

     The vlan driver demultiplexes frames tagged according to the IEEE 802.1Q standard into logical vlan network interfaces, which allows rout-
     ing/bridging between multiple VLANs through a single switch trunk port.

     Each vlan interface is created at runtime using interface cloning.  This is most easily done with the ifconfig(8) create command or using the
     cloned_interfaces variable in rc.conf(5).

     To function, a vlan interface must be assigned a parent interface and numeric VLAN tag using ifconfig(8).	A single parent can be assigned to
     multiple vlan interfaces provided they have different tags.  The parent interface is likely to be an Ethernet card connected to a properly
     configured switch port.  The VLAN tag should match one of those set up in the switched network.

     vlan initially assumes the same minimum length for tagged and untagged frames.  This mode is selected by setting the sysctl(8) variable
     net.link.vlan.soft_pad to 0 (default).  However, there are network devices that fail to adjust frame length when it falls below the allowed
     minimum due to untagging.	Such devices should be able to interoperate with vlan after changing the value of net.link.vlan.soft_pad to 1.	In
     the latter mode, vlan will pad short frames before tagging them so that their length is not less than the minimum value after untagging by
     the non-compliant devices.

HARDWARE

     The vlan driver supports efficient operation over parent interfaces that can provide help in processing VLANs.  Such interfaces are automati-
     cally recognized by their capabilities.  Depending on the level of sophistication found in a physical interface, it may do full VLAN process-
     ing or just be able to receive and transmit long frames (up to 1522 bytes including an Ethernet header and FCS).  The capabilities may be
     user-controlled by the respective parameters to ifconfig(8), vlanhwtag, and vlanmtu.  However, a physical interface is not obliged to react
     to them: It may have either capability enabled permanently without a way to turn it off.  The whole issue is very specific to a particular
     device and its driver.

     At present, these devices are capable of full VLAN processing in hardware: ae(4), age(4), alc(4), ale(4), bce(4), bge(4), bxe(4), cxgb(4),
     cxgbe(4), em(4), igb(4), ixgb(4), ixgbe(4), jme(4), msk(4), mxge(4), nxge(4), nge(4), re(4), sge(4), stge(4), ti(4), txp(4), and vge(4).

     Other Ethernet interfaces can run VLANs using software emulation in the vlan driver.  However, some lack the capability of transmitting and
     receiving long frames.  Assigning such an interface as the parent to vlan will result in a reduced MTU on the corresponding vlan interfaces.
     In the modern Internet, this is likely to cause tcp(4) connectivity problems due to massive, inadequate icmp(4) filtering that breaks the
     Path MTU Discovery mechanism.

     These interfaces natively support long frames for vlan: axe(4), bfe(4), cas(4), dc(4), et(4), fwe(4), fxp(4), gem(4), hme(4), le(4), nfe(4),
     rl(4), sf(4), sis(4), sk(4), ste(4), tl(4), tx(4), vr(4), vte(4), and xl(4).

     The vlan driver automatically recognizes devices that natively support long frames for vlan use and calculates the appropriate frame MTU
     based on the capabilities of the parent interface.  Some other interfaces not listed above may handle long frames, but they do not advertise
     this ability.  The MTU setting on vlan can be corrected manually if used in conjunction with such a parent interface.

SEE ALSO

     ifconfig(8), sysctl(8)

BUGS

     No 802.1Q features except VLAN tagging are implemented.

BSD
								   June 4, 2012 							       BSD