2 .\" Copyright (c) 2001 Yar Tikhiy
3 .\" All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
14 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
15 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
17 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
18 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33 .Nd "IEEE 802.1Q VLAN network interface"
35 To compile this driver into the kernel,
36 place the following lines in your
37 kernel configuration file:
38 .Bd -ragged -offset indent
43 Alternatively, to load the driver as a
44 module at boot time, place the following line in
46 .Bd -literal -offset indent
52 driver demultiplexes frames tagged according to
53 the IEEE 802.1Q standard into logical
55 network interfaces, which allows routing/bridging between
56 multiple VLANs through a single switch trunk port.
60 interface is created at runtime using interface cloning.
62 most easily done with the
72 interface must be assigned a parent interface and
73 numeric VLAN tag using
75 A single parent can be assigned to multiple
77 interfaces provided they have different tags.
78 The parent interface is likely to be an Ethernet card connected
79 to a properly configured switch port.
80 The VLAN tag should match one of those set up in the switched
85 assumes the same minimum length for tagged and untagged frames.
86 This mode is selected by the
89 .Va net.link.vlan.soft_pad
91 However, there are network devices that fail to adjust frame length,
92 should it fall below the allowed minimum due to untagging.
93 Such devices should be able to interoperate with
95 after changing the value of
96 .Va net.link.vlan.soft_pad
100 will pad short frames before tagging them
101 so that their length stays not less than the minimum value
102 after untagging by the non-compliant devices.
106 driver supports efficient operation over parent interfaces that can provide
107 help in processing VLANs.
108 Such interfaces are automatically recognized by their capabilities.
109 Depending on the level of sophistication found in a physical
110 interface, it may do full VLAN processing or just be able to
111 receive and transmit frames exceeding the maximum Ethernet frame size
112 by the length of a 802.1Q header.
113 The capabilities may be user-controlled by the respective parameters to
118 However, a physical interface is not obliged to react to them:
119 It may have either capability enabled permanently without
120 a way to turn it off.
121 The whole issue is very specific to a particular device and its driver.
123 By now, the list of physical interfaces able of full VLAN processing
124 in the hardware is limited to the following devices:
136 The rest of the Ethernet interfaces can run
137 VLANs using software emulation in the
140 However, most of them lack the capability
141 of transmitting and receiving oversized frames.
142 Assigning such an interface as the parent to
144 will result in a reduced MTU on the corresponding
147 In the modern Internet, this is likely to cause
149 connectivity problems due to massive, inadequate
151 filtering that breaks the Path MTU Discovery mechanism.
153 The interfaces that support oversized frames are as follows:
154 .Bl -tag -width ".Xr fxp 4 " -offset indent
156 supports long frames for
160 supports long frames for
167 .Pa /usr/src/sys/pci/if_de.c
168 source file and rebuilding the kernel
170 The hack works only for the 21041, 21140, and 21140A chips.
172 supports long frames for
176 supports long frames for
180 supports long frames for
184 supports long frames for
188 supports long frames for
192 supports long frames for
196 supports long frames for
200 supports long frames for
204 has support for long frames.
206 supports long frames for
210 supports long frames only if the card is built on a newer chip
216 driver automatically recognizes devices that natively support oversized frames
219 use and calculates the appropriate frame MTU based on the
220 capabilities of the parent interface.
221 The other interfaces listed above can handle oversized frames,
222 but they do not advertise this ability of theirs.
225 can be corrected manually if used in conjunction with such parent interface.
232 No 802.1Q features except VLAN tagging are implemented.
237 interface will be sent through
239 only if the parent interface uses
241 for link state notification.