Index: stable/8/share/man/man4/altq.4
===================================================================
--- stable/8/share/man/man4/altq.4	(revision 218106)
+++ stable/8/share/man/man4/altq.4	(revision 218107)
@@ -1,185 +1,188 @@
 .\"
 .\" Copyright (c) 2004 Max Laier <mlaier@FreeBSD.org>
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
 .\" $FreeBSD$
 .\"
-.Dd April 14, 2010
+.Dd December 19, 2010
 .Dt ALTQ 4
 .Os
 .Sh NAME
 .Nm ALTQ
 .Nd "alternate queuing of network packets"
 .Sh SYNOPSIS
 .Cd options ALTQ
 .Pp
 .Cd options ALTQ_CBQ
 .Cd options ALTQ_RED
 .Cd options ALTQ_RIO
 .Cd options ALTQ_HFSC
 .Cd options ALTQ_CDNR
 .Cd options ALTQ_PRIQ
 .Sh DESCRIPTION
 The
 .Nm
 framework provides several disciplines for queuing outgoing network packets.
 This is done by modifications to the interface packet queues.
 See
 .Xr altq 9
 for details.
 .Pp
 The user interface for
 .Nm
 is implemented by the
 .Xr pfctl 8
 utility, so please refer to the
 .Xr pfctl 8
 and the
 .Xr pf.conf 5
 manpages for a complete description of the
 .Nm
 capabilities and how to use it.
 .Ss Kernel Options
 The following options in the kernel configuration file are related to
 .Nm
 operation:
 .Pp
 .Bl -tag -width ".Dv ALTQ_DEBUG" -compact
 .It Dv ALTQ
 Enable
 .Nm .
 .It Dv ALTQ_CBQ
 Build the
 .Dq "Class Based Queuing"
 discipline.
 .It Dv ALTQ_RED
 Build the
 .Dq "Random Early Detection"
 extension.
 .It Dv ALTQ_RIO
 Build
 .Dq "Random Early Drop"
 for input and output.
 .It Dv ALTQ_HFSC
 Build the
 .Dq "Hierarchical Packet Scheduler"
 discipline.
 .It Dv ALTQ_CDNR
 Build the traffic conditioner.
 This option is meaningless at the moment as the conditioner is not used by
 any of the available disciplines or consumers.
 .It Dv ALTQ_PRIQ
 Build the
 .Dq "Priority Queuing"
 discipline.
 .It Dv ALTQ_NOPCC
 Required if the TSC is unusable.
 .It Dv ALTQ_DEBUG
 Enable additional debugging facilities.
 .El
 .Pp
 Note that
 .Nm Ns -disciplines
 cannot be loaded as kernel modules.
 In order to use a certain discipline you have to build it into a custom
 kernel.
 The
 .Xr pf 4
 interface, that is required for the configuration process of
 .Nm
 can be loaded as a module.
 .Sh SUPPORTED DEVICES
 The driver modifications described in
 .Xr altq 9
 are required to use a certain network card with
 .Nm .
 They have been applied to the following hardware drivers:
+.Xr ae 4 ,
 .Xr age 4 ,
 .Xr alc 4 ,
 .Xr ale 4 ,
 .Xr an 4 ,
 .Xr ath 4 ,
 .Xr aue 4 ,
 .Xt axe 4 ,
 .Xr bce 4 ,
 .Xr bfe 4 ,
 .Xr bge 4 ,
 .Xr cas 4 ,
 .Xr dc 4 ,
 .Xr de 4 ,
 .Xr ed 4 ,
 .Xr em 4 ,
 .Xr ep 4 ,
 .Xr epair 4 ,
 .Xr fxp 4 ,
 .Xr gem 4 ,
 .Xr hme 4 ,
+.Xr igb 4 ,
 .Xr ipw 4 ,
 .Xr iwi 4 ,
+.Xr ixgbe 4 ,
 .Xr jme 4 ,
 .Xr le 4 ,
 .Xr msk 4 ,
 .Xr mxge 4 ,
 .Xr my 4 ,
 .Xr nfe 4 ,
 .Xr nge 4 ,
 .Xr npe 4 ,
 .Xr nve 4 ,
 .Xr ral 4 ,
 .Xr re 4 ,
 .Xr rl 4 ,
 .Xr rum 4 ,
 .Xr sf 4 ,
 .Xr sge 4 ,
 .Xr sis 4 ,
 .Xr sk 4 ,
 .Xr ste 4 ,
 .Xr stge 4 ,
 .Xr txp 4 ,
 .Xr udav 4 ,
 .Xr ural 4 ,
 .Xr vge 4 ,
 .Xr vr 4 ,
 .Xr wi 4 ,
 and
 .Xr xl 4 .
 .Pp
 The
 .Xr ndis 4
 framework also has support for
 .Nm
 and thus all encapsulated drivers.
 .Pp
 The
 .Xr tun 4
 and
 .Xr ng_iface 4
 pseudo drivers also do support
 .Nm .
 .Sh SEE ALSO
 .Xr pf 4 ,
 .Xr pf.conf 5 ,
 .Xr ipfw 8 ,
 .Xr pfctl 8 ,
 .Xr altq 9
Index: stable/8/share/man/man4/ixgbe.4
===================================================================
--- stable/8/share/man/man4/ixgbe.4	(revision 218106)
+++ stable/8/share/man/man4/ixgbe.4	(revision 218107)
@@ -1,125 +1,126 @@
 .\" Copyright (c) 2001-2008, Intel Corporation
 .\" All rights reserved.
 .\" 
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions are met:
 .\"
 .\" 1. Redistributions of source code must retain the above copyright notice,
 .\"    this list of conditions and the following disclaimer.
 .\"
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\"
 .\" 3. Neither the name of the Intel Corporation nor the names of its
 .\"    contributors may be used to endorse or promote products derived from
 .\"    this software without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
 .\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
 .\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
 .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
 .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
 .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
 .\" * Other names and brands may be claimed as the property of others.
 .\"
 .\" $FreeBSD$
 .\"
-.Dd June 11, 2008
+.Dd December 19, 2010
 .Dt IXGBE 4
 .Os
 .Sh NAME
 .Nm ixgbe
 .Nd "Intel(R) 10Gb Ethernet driver for the FreeBSD operating system"
 .Sh SYNOPSIS
 To compile this driver into the kernel,
 place the following line in your
 kernel configuration file:
 .Bd -ragged -offset indent
 .Cd "device ixgbe"
 .Ed
 .Pp
 Alternatively, to load the driver as a
 module at boot time, place the following line in
 .Xr loader.conf 5 :
 .Bd -literal -offset indent
 if_ixgbe_load="YES"
 .Ed
 .Sh DESCRIPTION
 The
 .Nm
 driver provides support for PCI 10Gb Ethernet adapters based on
 the Intel 82598EB Intel(R) Network Connections.
 The driver supports Jumbo Frames, MSIX, TSO, and RSS.
 .Pp
 For questions related to hardware requirements,
 refer to the documentation supplied with your Intel 10GbE adapter.
 All hardware requirements listed apply to use with
 .Fx .
 .Pp
 Support for Jumbo Frames is provided via the interface MTU setting.
 Selecting an MTU larger than 1500 bytes with the
 .Xr ifconfig 8
 utility configures the adapter to receive and transmit Jumbo Frames.
 The maximum MTU size for Jumbo Frames is 16114.
 .Pp
 This driver version supports VLANs.
 For information on enabling VLANs, see
 .Xr ifconfig 8 .
 .Sh HARDWARE
 The
 .Nm
 driver supports the following cards:
 .Pp
 .Bl -bullet -compact
 .It
 Intel(R) 10 Gigabit XF SR/AF Dual Port Server Adapter 
 .It
 Intel(R) 10 Gigabit XF SR/LR Server Adapter
 .It
 Intel(R) 82598EB 10 Gigabit AF Network Connection
 .It
 Intel(R) 82598EB 10 Gigabit AT CX4 Network Connection                  
 .El
 .Sh DIAGNOSTICS
 .Bl -diag
 .It "ixgbe%d: Unable to allocate bus resource: memory"
 A fatal initialization error has occurred.
 .It "ixgbe%d: Unable to allocate bus resource: interrupt"
 A fatal initialization error has occurred.
 .It "ixgbe%d: watchdog timeout -- resetting"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
 .El
 .Sh SUPPORT
 For general information and support,
 go to the Intel support website at:
 .Pa http://support.intel.com .
 .Pp
 If an issue is identified with the released source code on the supported kernel
 with a supported adapter, email the specific information related to the
 issue to
 .Aq freebsdnic@mailbox.intel.com .
 .Sh SEE ALSO
+.Xr altq 4 ,
 .Xr arp 4 ,
 .Xr netintro 4 ,
 .Xr ng_ether 4 ,
 .Xr polling 4 ,
 .Xr vlan 4 ,
 .Xr ifconfig 8
 .Sh HISTORY
 The
 .Nm
 device driver first appeared in
 .Fx 7.0 .
 .Sh AUTHORS
 The
 .Nm
 driver was written by
 .An Intel Corporation Aq freebsdnic@mailbox.intel.com .
Index: stable/8/share/man/man4/miibus.4
===================================================================
--- stable/8/share/man/man4/miibus.4	(revision 218106)
+++ stable/8/share/man/man4/miibus.4	(revision 218107)
@@ -1,185 +1,188 @@
 .\" Written by Tom Rhodes for the FreeBSD Project.
 .\" Please see the /usr/src/COPYRIGHT file for copyright information.
 .\"
 .\" This document takes information from the IEEE 802.3 Standard
 .\" along with various comments from Peter Wemm, Robert Watson, and Bill Paul.
 .\" Originally this file looked much like the NetBSD mii(4) manual page, but
 .\" I doubt you would ever notice due to large differences.
 .\"
 .\" $FreeBSD$
 .\"
 .Dd January 15, 2011
 .Dt MIIBUS 4
 .Os
 .Sh NAME
 .Nm miibus
 .Nd IEEE 802.3 Media Independent Interface network bus
 .Sh SYNOPSIS
 For most network interface cards (NIC):
 .Cd "device miibus"
 .Sh DESCRIPTION
 The
 .Nm
 driver provides an interconnection between the Media Access Control (MAC)
 sublayer, the Physical Layer entities (PHY), Station Management (STA)
 entities, and the PHY Layer as defined by the IEEE 802.3 Standard.
 .Pp
 The
 .Nm
 layer allows network device drivers to share common support
 code for various external PHY devices.
 Most 10/100 network interface cards either use an MII transceiver
 or have built-in transceivers that can be programmed using an MII
 interface.
 The
 .Nm
 driver currently handles all of the media detection,
 selection, and reporting using the ifmedia interface.
 A generic driver has been included for all PHYs that are not
 handled by a specific driver, this is possible because all
 10/100 PHYs implement the same general register set along with
 their vendor specific register set.
 .Pp
 The following network device drivers use the
 .Nm
 interface:
 .Pp
 .Bl -tag -compact -width ".Xr fxp 4"
+.It Xr ae 4
+Attansic/Atheros L2 Fast Ethernet
 .It Xr age 4
 Attansic/Atheros L1 Gigabit Ethernet
 .It Xr alc 4
 Atheros AR8131/AR8132 PCIe Ethernet
 .It Xr ale 4
 Atheros AR8121/AR8113/AR8114 PCIe Ethernet
 .It Xr aue 4
 ADMtek USB Ethernet
 .It Xr axe 4
 ASIX Electronics AX88172 USB Ethernet
 .It Xr bce 4
 Broadcom NetXtreme II Gigabit Ethernet
 .It Xr bfe 4
 Broadcom BCM4401 Ethernet
 .It Xr bge 4
 Broadcom BCM570xx Gigabit Ethernet
 .It Xr cas 4
 Sun Cassini/Cassini+ and National Semiconductor DP83065 Saturn
 .It Xr dc 4
 DEC/Intel 21143 and various workalikes
 .It Xr ed 4
 NE[12]000, SMC Ultra, 3c503, DS8390 cards
 .It Xr et 4
 Agere ET1310 Gigabit Ethernet
 .It Xr fxp 4
 Intel EtherExpress PRO/100B
 .It Xr gem 4
 Sun ERI, Sun GEM and Apple GMAC Ethernet
 .It Xr hme 4
 Sun HME Ethernet
 .It Xr jme 4
 JMicron JMC250 Gigabit/JMC260 Fast Ethernet
 .It Xr lge 4
 Level 1 LXT1001 NetCellerator Gigabit Ethernet
 .It Xr msk 4
 Marvell/SysKonnect Yukon II Gigabit Ethernet
 .It Xr nfe 4
 NVIDIA nForce MCP Networking Adapter
 .It Xr nge 4
 National Semiconductor DP83820/DP83821 Gigabit Ethernet
 .It Xr nve 4
 NVIDIA nForce MCP Networking Adapter
 .It Xr pcn 4
 AMD Am79C97x PCI 10/100
 .It Xr re 4
 RealTek 8139C+/8169/8169S/8110S
 .It Xr rl 4
 RealTek 8129/8139
 .It Xr rue 4
 RealTek RTL8150 USB To Fast Ethernet
 .It Xr sf 4
 Adaptec AIC-6915
 .It Xr sge 4
 Silicon Integrated Systems SiS190/191 Ethernet
 .It Xr sis 4
 Silicon Integrated Systems SiS 900/SiS 7016
 .It Xr sk 4
 SysKonnect SK-984x and SK-982x Gigabit Ethernet
 .It Xr ste 4
 Sundance ST201 (D-Link DFE-550TX)
 .It Xr stge 4
 Sundance/Tamarack TC9021 Gigabit Ethernet
 .It Xr tl 4
 Texas Instruments ThunderLAN
 .It Xr tx 4
 SMC EtherPower II (83c170)
 .It Xr udav 4
 Davicom DM9601 USB Ethernet
 .It Xr vge 4
 VIA VT612x PCI Gigabit Ethernet
 .It Xr vr 4
 VIA Rhine, Rhine II
 .It Xr wb 4
 Winbond W89C840F
 .It Xr xl 4
 3Com 3c90x
 .El
 .Sh COMPATIBILITY
 The implementation of
 .Nm
 was originally intended to have similar API interfaces
 to
 .Bsx 3.0
 and
 .Nx ,
 but as a result are not well behaved newbus device drivers.
 .Sh SEE ALSO
+.Xr ae 4 ,
 .Xr age 4 ,
 .Xr alc 4 ,
 .Xr ale 4 ,
 .Xr arp 4 ,
 .Xr aue 4 ,
 .Xr axe 4 ,
 .Xr bce 4 ,
 .Xr bfe 4 ,
 .Xr bge 4 ,
 .Xr cas 4 ,
 .Xr dc 4 ,
 .Xr ed 4 ,
 .Xr et 4 ,
 .Xr fxp 4 ,
 .Xr gem 4 ,
 .Xr hme 4 ,
 .Xr jme 4 ,
 .Xr lge 4 ,
 .Xr msk 4 ,
 .Xr netintro 4 ,
 .Xr nfe 4 ,
 .Xr nge 4 ,
 .Xr nve 4 ,
 .Xr pcn 4 ,
 .Xr re 4 ,
 .Xr rgephy 4 ,
 .Xr rl 4 ,
 .Xr rue 4 ,
 .Xr sf 4 ,
 .Xr sge 4 ,
 .Xr sis 4 ,
 .Xr sk 4 ,
 .Xr ste 4 ,
 .Xr stge 4 ,
 .Xr tl 4 ,
 .Xr tx 4 ,
 .Xr udav 4 ,
 .Xr vge 4 ,
 .Xr vr 4 ,
 .Xr wb 4 ,
 .Xr xl 4
 .Sh STANDARDS
 More information on MII can be found in the IEEE 802.3 Standard.
 .Sh HISTORY
 The
 .Nm
 driver first appeared in
 .Fx 3.3 .
 .Sh AUTHORS
 This manual page was written by
 .An Tom Rhodes Aq trhodes@FreeBSD.org .
Index: stable/8/share/man/man4/vlan.4
===================================================================
--- stable/8/share/man/man4/vlan.4	(revision 218106)
+++ stable/8/share/man/man4/vlan.4	(revision 218107)
@@ -1,201 +1,206 @@
 .\"
 .\" Copyright (c) 2001 Yar Tikhiy
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
 .\" $FreeBSD$
 .\"
-.Dd April 14, 2010
+.Dd December 19, 2010
 .Dt VLAN 4
 .Os
 .Sh NAME
 .Nm vlan
 .Nd "IEEE 802.1Q VLAN network interface"
 .Sh SYNOPSIS
 To compile this driver into the kernel,
 place the following lines in your
 kernel configuration file:
 .Bd -ragged -offset indent
 .Cd "device vlan"
 .Ed
 .Pp
 Alternatively, to load the driver as a
 module at boot time, place the following line in
 .Xr loader.conf 5 :
 .Bd -literal -offset indent
 if_vlan_load="YES"
 .Ed
 .Sh DESCRIPTION
 The
 .Nm
 driver demultiplexes frames tagged according to
 the IEEE 802.1Q standard into logical
 .Nm
 network interfaces, which allows routing/bridging between
 multiple VLANs through a single switch trunk port.
 .Pp
 Each
 .Nm
 interface is created at runtime using interface cloning.
 This is
 most easily done with the
 .Xr ifconfig 8
 .Cm create
 command or using the
 .Va cloned_interfaces
 variable in
 .Xr rc.conf 5 .
 .Pp
 To function, a
 .Nm
 interface must be assigned a parent interface and
 numeric VLAN tag using
 .Xr ifconfig 8 .
 A single parent can be assigned to multiple
 .Nm
 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.
 .Pp
 Initially
 .Nm
 assumes the same minimum length for tagged and untagged frames.
 This mode is selected by the
 .Xr sysctl 8
 variable
 .Va net.link.vlan.soft_pad
 set to 0 (default).
 However, there are network devices that fail to adjust frame length,
 should it fall below the allowed minimum due to untagging.
 Such devices should be able to interoperate with
 .Nm
 after changing the value of
 .Va net.link.vlan.soft_pad
 to 1.
 In the latter mode,
 .Nm
 will pad short frames before tagging them
 so that their length stays not less than the minimum value
 after untagging by the non-compliant devices.
 .Sh HARDWARE
 The
 .Nm
 driver supports efficient operation over parent interfaces that can provide
 help in processing VLANs.
 Such interfaces are automatically recognized by their capabilities.
 Depending on the level of sophistication found in a physical
 interface, it may do full VLAN processing 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
 .Xr ifconfig 8 ,
 .Cm vlanhwtag
 and
 .Cm 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.
 .Pp
 By now, the list of physical interfaces able of full VLAN processing
 in the hardware is limited to the following devices:
 .Xr ae 4 ,
 .Xr age 4 ,
 .Xr alc 4 ,
 .Xr ale 4 ,
 .Xr bce 4 ,
 .Xr bge 4 ,
 .Xr cxgb 4 ,
 .Xr em 4 ,
+.Xr igb 4 ,
 .Xr ixgb 4 ,
+.Xr ixgbe 4 ,
 .Xr jme 4 ,
 .Xr msk 4 ,
+.Xr mxge 4 ,
+.Xr nxge 4 ,
 .Xr nge 4 ,
 .Xr re 4 ,
 .Xr sge 4 ,
 .Xr stge 4 ,
 .Xr ti 4 ,
 .Xr txp 4 ,
 and
 .Xr vge 4 .
 .Pp
 The rest of the Ethernet interfaces can run
 VLANs using software emulation in the
 .Nm
 driver.
 However, some of them lack the capability
 of transmitting and receiving long frames.
 Assigning such an interface as the parent to
 .Nm
 will result in a reduced MTU on the corresponding
 .Nm
 interfaces.
 In the modern Internet, this is likely to cause
 .Xr tcp 4
 connectivity problems due to massive, inadequate
 .Xr icmp 4
 filtering that breaks the Path MTU Discovery mechanism.
 .Pp
 The following interfaces support long frames for
 .Nm
 natively:
 .Xr bfe 4 ,
 .Xr cas 4 ,
 .Xr dc 4 ,
+.Xr et 4 ,
 .Xr fwe 4 ,
 .Xr fxp 4 ,
 .Xr gem 4 ,
 .Xr hme 4 ,
 .Xr le 4 ,
 .Xr nfe 4 ,
 .Xr nve 4 ,
 .Xr rl 4 ,
 .Xr sf 4 ,
 .Xr sis 4 ,
 .Xr sk 4 ,
 .Xr ste 4 ,
 .Xr tl 4 ,
 .Xr tx 4 ,
 .Xr vr 4 ,
 and
 .Xr xl 4 .
 .Pp
 The
 .Nm
 driver automatically recognizes devices that natively support long frames
 for
 .Nm
 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 of theirs.
 The MTU setting on
 .Nm
 can be corrected manually if used in conjunction with such a parent interface.
 .Sh SEE ALSO
 .Xr ifconfig 8 ,
 .Xr sysctl 8
 .Sh BUGS
 No 802.1Q features except VLAN tagging are implemented.
Index: stable/8/share/man/man4
===================================================================
--- stable/8/share/man/man4	(revision 218106)
+++ stable/8/share/man/man4	(revision 218107)

Property changes on: stable/8/share/man/man4
___________________________________________________________________
Modified: svn:mergeinfo
## -0,0 +0,1 ##
   Merged /head/share/man/man4:r216576,216578-216581,217974