1.\" $NetBSD: vlan.4,v 1.22 2003/04/16 09:59:40 wiz Exp $ 2.\" 3.\" Copyright (c) 2000 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Jason R. Thorpe of Zembu Labs, Inc. 8.\" 9.\" Redistribution and use in source and binary forms, with or without 10.\" modification, are permitted provided that the following conditions 11.\" are met: 12.\" 1. Redistributions of source code must retain the above copyright 13.\" notice, this list of conditions and the following disclaimer. 14.\" 2. Redistributions in binary form must reproduce the above copyright 15.\" notice, this list of conditions and the following disclaimer in the 16.\" documentation and/or other materials provided with the distribution. 17.\" 3. All advertising materials mentioning features or use of this software 18.\" must display the following acknowledgement: 19.\" This product includes software developed by the NetBSD 20.\" Foundation, Inc. and its contributors. 21.\" 4. Neither the name of The NetBSD Foundation nor the names of its 22.\" contributors may be used to endorse or promote products derived 23.\" from this software without specific prior written permission. 24.\" 25.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 26.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 27.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 28.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS 29.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 30.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 31.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 32.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 33.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 34.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 35.\" POSSIBILITY OF SUCH DAMAGE. 36.\" 37.Dd March 19, 2003 38.Dt VLAN 4 39.Os 40.Sh NAME 41.Nm vlan 42.Nd IEEE 802.1Q Virtual LAN network device 43.Sh SYNOPSIS 44.Cd "pseudo-device vlan" 45.Sh DESCRIPTION 46The 47.Nm 48interface provides support for IEEE 802.1Q Virtual LANs. This allows the 49trunking of more than one network on a single network interface. 50This is particularly useful on routers or on hosts which must be 51connected to many different networks. 52.Pp 53To use a 54.Nm vlan 55interface, the administrator must first create the interface and then 56specify the VLAN tag and physical interface associated with the VLAN. 57This can be done by using the 58.Xr ifconfig 8 59.Sq create , 60.Sq vlan , 61and 62.Sq vlanif 63subcommands, or 64.Dv SIOCSIFCREATE 65and 66.Dv SIOCSIFVLAN 67ioctls. 68.Pp 69To be compatible with others 802.1Q devices, the 70.Nm 71interface shall support a 1500 bytes MTU, which means that the parent 72interface will have to handle frames that are 4 bytes larger than the 73Ethernet MTU. Drivers supporting this increased MTU are: 74.Pp 75.Bl -dash -compact 76.It 77drivers using the dp8390 core (such as 78.Xr ec 4 , 79.Xr ne 4 , 80.Xr we 4 , 81and possibly others) 82.It 83.Xr bge 4 84.It 85.Xr ea 4 86.It 87.Xr eb 4 88.It 89.Xr epic 4 90.It 91.Xr ex 4 92.It 93.Xr fxp 4 94.It 95.Xr gem 4 96.It 97.Xr hme 4 98.It 99.Xr le 4 100.It 101.Xr sip 4 102.It 103.Xr ste 4 104.It 105.Xr stge 4 106.It 107.Xr ti 4 108.It 109.Xr tl 4 110.It 111.Xr tlp 4 112.It 113.Xr wm 4 114.It 115.Xr xi 4 116.El 117.Pp 118.Nm 119can be used with devices not supporting the 802.1Q MTU, but then the MTU of the 120.Nm 121interface will be 4 bytes too small and will not interoperate properly with 122other 802.1Q devices, unless the MTU of the remote end is also lowered. 123.Sh SEE ALSO 124.Xr ifconfig 8 125.Sh HISTORY 126The 127.Nm 128device first appeared in 129.Nx 1.5.1 . 130.Sh AUTHORS 131The 132.Nm 133driver was integrated by 134.An Andrew Doran 135.Aq ad@NetBSD.org 136and 137.An Jason R. Thorpe 138.Aq thorpej@zembu.com . 139It was derived from a VLAN implementation that appeared in 140.Fx 141and 142.Ox . 143.Sh BUGS 144The 145.Nm 146interfaces do not currently inherit changes made to the physical 147interfaces's MTU. 148