Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

vlan(4) [netbsd man page]

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

NAME
vlan -- IEEE 802.1Q Virtual LAN network device SYNOPSIS
pseudo-device vlan DESCRIPTION
The vlan interface provides support for IEEE 802.1Q Virtual Local Area Networks (VLAN). This supports the trunking of more than one network on a single network interface. This is particularly useful on routers or on hosts which must be connected to many different networks through a single physical interface. To use a vlan interface, the administrator must first create the interface and then specify the VID (VLAN identifier, the first 12 bits from a 16-bit integer which distinguishes each VLAN from any others) and physical interface associated with the VLAN. This can be done by using the ifconfig(8) create, vlan, and vlanif subcommands from a shell command line or script. From within a C program, use the ioctl(2) system call with the SIOCSIFCREATE and SIOCSIFVLAN arguments. To be compatible with other IEEE 802.1Q devices, the vlan interface supports a 1500 byte MTU, which means that the parent interface will have to handle packets that are 4 bytes larger than the original Ethernet standard. Drivers supporting this increased MTU are: - drivers using the DP8390 core (such as ec(4), ne(4), we(4), and possibly others) - bge(4) - bnx(4) - ea(4) - eb(4) - epic(4) - etherip(4) - ex(4) - fxp(4) - gem(4) - hme(4) - le(4) - sip(4) - ste(4) - stge(4) - ti(4) - tl(4) - tlp(4) - vge(4) - vr(4) - wm(4) - xi(4) vlan can be used with devices not supporting the IEEE 802.1Q MTU, but then the MTU of the vlan interface will be 4 bytes too small and will not interoperate properly with other IEEE 802.1Q devices, unless the MTU of the other hosts on the VLAN are also lowered to match. EXAMPLES
The following will create interface vlan0 with VID six, on the Ethernet interface tlp0: ifconfig vlan0 create ifconfig vlan0 vlan 6 vlanif tlp0 After this set up, IP addresses (and/or other protocols) can be assigned to the vlan0 interface. All other hosts on the Ethernet connected to tlp0 which configure a VLAN and use VID six will see all traffic transmitted through vlan0. The same VLAN can be created at system startup time by placing the following in /etc/ifconfig.vlan0: create vlan 6 vlanif tlp0 SEE ALSO
ifconfig(8) HISTORY
The vlan device first appeared in NetBSD 1.5.1, and was derived from a VLAN implementation that appeared in FreeBSD and OpenBSD. BUGS
The vlan interfaces do not currently inherit changes made to the physical interfaces' MTU. BSD
December 16, 2010 BSD

Check Out this Related Man Page

IFCFG-VLAN(5)						       Network configuration						     IFCFG-VLAN(5)

NAME
ifcfg-vlan - virtual LAN interface configuration SYNOPSIS
/etc/sysconfig/network/ifcfg-vlan* Virtual LANs (802.1q) To setup a vlan interface you need a configuration file that contains at least the mandatory ETHERDEVICE variable with the real interface used for the virtual LAN. Further, it may contain the optional VLAN_ID variable that specifies the VLAN ID. By default and when the VLAN_ID variable is not set, the number at the end of the interface name is the VLAN ID. Preferably the interface name and the configuration file follow the VLAN interface name scheme (type), that is either: ifcfg-vlan<VLAN-ID> (e.g. ifcfg-vlan42) or ifcfg-name.<VLAN-ID> (e.g. ifcfg-eth0.42) The VLAN-ID can be also 0-padded (e.g. ifcfg-vlan0042 or ifcfg-eth0.0042). Also in case of custom names, trailing digits are interpreted as VLAN-ID by default (e.g. ifcfg-dmz42). When VLAN_ID is set in the config, the interface name have any name (e.g. ifcfg-foobar). Note: The drawback of custom interface names and VLAN_ID usage is, that a rename of the interface is required and that they violate the name scheme. The real interface will be set UP automatically and doesn't need a config file in case of a physical interface. But without a config file YaST will consider this interface as unused, if will not follow hotplug events and you're unable to apply any settings, e.g. ETH- TOOL_OPTIONS. To avoid that, provide an config file with at least STARTMODE='auto'. The rest of the VLAN interface IP and routes configuration do not differ from ordinary interfaces. See also man ifcfg and man routes for details. EXAMPLES
Sets up vlan3 vlan interface on top of eth0: ifcfg-vlan3 STARTMODE='auto' ETHERDEVICE='eth0' IPADDR='192.168.3.27/24' Sets up eth0.3 vlan interface on top of eth0: ifcfg-eth0.3 STARTMODE='auto' ETHERDEVICE='eth0' IPADDR='192.168.3.27/24' Sets up lan1 vlan interface with ID 42 on top of eth0: ifcfg-lan1 STARTMODE='auto' ETHERDEVICE='eth0' VLAN_ID='42' IPADDR='192.168.3.27/24' BUGS
Please report bugs at <http://www.suse.de/feedback> AUTHOR
Christian Zoz <zoz@suse.de> Michal Svec <msvec@suse.cz> Bjoern Jacke Mads Martin Joergensen <mmj@suse.de> Michal Ludvig <mludvig@suse.cz> Marius Tomaschewski <mt@suse.de> SEE ALSO
routes(5), ifcfg(5), ifup(8). sysconfig August 2004 IFCFG-VLAN(5)
Man Page