179458d0bSYaroslav Tykhiy.\" 279458d0bSYaroslav Tykhiy.\" Copyright (c) 2001 Yar Tikhiy 379458d0bSYaroslav Tykhiy.\" All rights reserved. 479458d0bSYaroslav Tykhiy.\" 579458d0bSYaroslav Tykhiy.\" Redistribution and use in source and binary forms, with or without 679458d0bSYaroslav Tykhiy.\" modification, are permitted provided that the following conditions 779458d0bSYaroslav Tykhiy.\" are met: 879458d0bSYaroslav Tykhiy.\" 1. Redistributions of source code must retain the above copyright 979458d0bSYaroslav Tykhiy.\" notice, this list of conditions and the following disclaimer. 1079458d0bSYaroslav Tykhiy.\" 2. Redistributions in binary form must reproduce the above copyright 1179458d0bSYaroslav Tykhiy.\" notice, this list of conditions and the following disclaimer in the 1279458d0bSYaroslav Tykhiy.\" documentation and/or other materials provided with the distribution. 1379458d0bSYaroslav Tykhiy.\" 1479458d0bSYaroslav Tykhiy.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND 1579458d0bSYaroslav Tykhiy.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 1679458d0bSYaroslav Tykhiy.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 1779458d0bSYaroslav Tykhiy.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 1879458d0bSYaroslav Tykhiy.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 1979458d0bSYaroslav Tykhiy.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 2079458d0bSYaroslav Tykhiy.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 2179458d0bSYaroslav Tykhiy.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 2279458d0bSYaroslav Tykhiy.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 2379458d0bSYaroslav Tykhiy.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 2479458d0bSYaroslav Tykhiy.\" SUCH DAMAGE. 2579458d0bSYaroslav Tykhiy.\" 2679458d0bSYaroslav Tykhiy.\" $FreeBSD$ 2779458d0bSYaroslav Tykhiy.\" 2879458d0bSYaroslav Tykhiy.Dd July 25, 2001 2979458d0bSYaroslav Tykhiy.Dt VLAN 4 3079458d0bSYaroslav Tykhiy.Os 3179458d0bSYaroslav Tykhiy.Sh NAME 3279458d0bSYaroslav Tykhiy.Nm vlan 3379458d0bSYaroslav Tykhiy.Nd IEEE 802.1Q VLAN network interface 3479458d0bSYaroslav Tykhiy.Sh SYNOPSIS 359d4fe4b2SBrooks Davis.Cd device vlan 3679458d0bSYaroslav Tykhiy.\" 3779458d0bSYaroslav Tykhiy.Sh DESCRIPTION 3879458d0bSYaroslav TykhiyThe 3979458d0bSYaroslav Tykhiy.Nm 4079458d0bSYaroslav Tykhiydriver demultiplexes frames tagged according to 4179458d0bSYaroslav Tykhiythe IEEE 802.1Q standard into logical 4279458d0bSYaroslav Tykhiy.Nm 4379458d0bSYaroslav Tykhiynetwork interfaces, which allows routing/bridging between 4479458d0bSYaroslav Tykhiymultiple VLANs through a single switch trunk port. 4579458d0bSYaroslav Tykhiy.Pp 4679458d0bSYaroslav TykhiyTo function, a 4779458d0bSYaroslav Tykhiy.Nm 4879458d0bSYaroslav Tykhiyinterface must be assigned a parent interface and 4979458d0bSYaroslav Tykhiynumeric VLAN tag using 5079458d0bSYaroslav Tykhiy.Xr ifconfig 8 . 5179458d0bSYaroslav TykhiyA single parent can be assigned to multiple 5279458d0bSYaroslav Tykhiy.Nm 5379458d0bSYaroslav Tykhiyinterfaces provided they have different tags. 5479458d0bSYaroslav TykhiyThe parent interface is likely to be an ethernet card connected 5579458d0bSYaroslav Tykhiyto a properly configured switch port. 5679458d0bSYaroslav TykhiyThe VLAN tag should match one of those set up in the switched 5779458d0bSYaroslav Tykhiynetwork. 5879458d0bSYaroslav Tykhiy.Pp 5979458d0bSYaroslav TykhiyThe 6079458d0bSYaroslav Tykhiy.Nm 6179458d0bSYaroslav Tykhiydriver supports physical devices that do 6279458d0bSYaroslav Tykhiythe VLAN demultiplexing in firmware. 6379458d0bSYaroslav TykhiyThe 6472ddf849SRuslan Ermilov.Cm link0 6579458d0bSYaroslav Tykhiyflag should be set on a 6679458d0bSYaroslav Tykhiy.Nm 6779458d0bSYaroslav Tykhiyinterface 6879458d0bSYaroslav Tykhiy.Pq Em not on its parent 6979458d0bSYaroslav Tykhiyusing 7079458d0bSYaroslav Tykhiy.Xr ifconfig 8 7179458d0bSYaroslav Tykhiyin that case to indicate that the hardware support for 7279458d0bSYaroslav Tykhiythe 802.1Q VLANs is present in its parent. 7379458d0bSYaroslav Tykhiy.\" 7479458d0bSYaroslav Tykhiy.Ss "Selecting the Right Network Interface Card to Run VLANs Through" 7579458d0bSYaroslav TykhiyBy now, the only NICs that have both hardware support and proper 7679458d0bSYaroslav Tykhiydriver hooks for the 802.1Q VLAN technology in 7779458d0bSYaroslav Tykhiy.Fx 7879458d0bSYaroslav Tykhiyare 792ba5fff2SYaroslav Tykhiy.Xr bge 4 , 8079458d0bSYaroslav Tykhiy.Xr nge 4 , 8179458d0bSYaroslav Tykhiy.Xr ti 4 , 8279458d0bSYaroslav Tykhiyand 8379458d0bSYaroslav Tykhiy.Xr txp 4 . 8479458d0bSYaroslav Tykhiy.Pp 8579458d0bSYaroslav TykhiyThe rest of the ethernet NICs supported by 8679458d0bSYaroslav Tykhiy.Fx 8779458d0bSYaroslav Tykhiycan run 8879458d0bSYaroslav TykhiyVLANs using the software emulation in the 8979458d0bSYaroslav Tykhiy.Nm 9079458d0bSYaroslav Tykhiydriver. 9179458d0bSYaroslav TykhiyHowever, most of them lack the capability 9279458d0bSYaroslav Tykhiyof transmitting and/or receiving oversized frames. 9379458d0bSYaroslav TykhiyUsing such a NIC as a parent interface for a 9479458d0bSYaroslav Tykhiy.Nm 9579458d0bSYaroslav Tykhiyimplies a reduced MTU on the corresponding 9679458d0bSYaroslav Tykhiy.Nm 9779458d0bSYaroslav Tykhiyinterfaces. 9879458d0bSYaroslav TykhiyIn the modern Internet, this is likely to cause 9979458d0bSYaroslav Tykhiy.Xr tcp 4 10079458d0bSYaroslav Tykhiyconnectivity problems due to massive, inadequate 10179458d0bSYaroslav Tykhiy.Xr icmp 4 10279458d0bSYaroslav Tykhiyfiltering that breaks the Path MTU Discovery mechanism. 10379458d0bSYaroslav Tykhiy.Pp 10479458d0bSYaroslav TykhiyThe NICs that support oversized frames are as follows: 10572ddf849SRuslan Ermilov.Bl -tag -width ".Xr fxp 4 " -offset indent 10679458d0bSYaroslav Tykhiy.It Xr de 4 10779458d0bSYaroslav Tykhiyrequires defining 10879458d0bSYaroslav Tykhiy.Dv BIG_PACKET 10979458d0bSYaroslav Tykhiyin the 11079458d0bSYaroslav Tykhiy.Pa /usr/src/sys/pci/if_de.c 11179458d0bSYaroslav Tykhiysource file and rebuilding the kernel 11279458d0bSYaroslav Tykhiyor module. 11379458d0bSYaroslav TykhiyThe hack works only for the 21041, 21140, and 21140A chips. 11479458d0bSYaroslav Tykhiy.It Xr fxp 4 11579458d0bSYaroslav Tykhiysupports long frames for the 11679458d0bSYaroslav Tykhiy.Nm 11779458d0bSYaroslav Tykhiynatively. 11879458d0bSYaroslav Tykhiy.It Xr tl 4 11979458d0bSYaroslav Tykhiydoes support long frames. 12079458d0bSYaroslav Tykhiy.It Xr tx 4 1212ba5fff2SYaroslav Tykhiydoes support long frames. 1222ba5fff2SYaroslav Tykhiy.It Xr wx 4 1232ba5fff2SYaroslav Tykhiydoes support long frames. 12479458d0bSYaroslav Tykhiy.It Xr xl 4 12579458d0bSYaroslav Tykhiysupports long frames only if the card is built on a newer chip 12672ddf849SRuslan Ermilov(Cyclone and above). 12779458d0bSYaroslav Tykhiy.El 12872ddf849SRuslan Ermilov.Pp 12979458d0bSYaroslav TykhiyNote: 13079458d0bSYaroslav TykhiyExcept for 1312ba5fff2SYaroslav Tykhiy.Xr fxp 4 1322ba5fff2SYaroslav Tykhiyand 1332ba5fff2SYaroslav Tykhiy.Xr tx 4 , 13479458d0bSYaroslav Tykhiynone of the above drivers inform the 13579458d0bSYaroslav Tykhiy.Nm 13679458d0bSYaroslav Tykhiydriver about their support for long frames. 13779458d0bSYaroslav TykhiyJust fix the MTU of a 13879458d0bSYaroslav Tykhiy.Nm 13972ddf849SRuslan Ermilovinterface if it appears to be lower than 1500 bytes after 14079458d0bSYaroslav Tykhiyattaching the 14179458d0bSYaroslav Tykhiy.Nm 14279458d0bSYaroslav Tykhiyto a parent interface that is known to support long frames. 14379458d0bSYaroslav Tykhiy.Sh SEE ALSO 14479458d0bSYaroslav Tykhiy.Xr ifconfig 8 14579458d0bSYaroslav Tykhiy.Sh BUGS 14679458d0bSYaroslav TykhiyNo 802.1Q features except VLAN tagging are implemented. 147