summaryrefslogtreecommitdiffstats
path: root/share/man/man4/vlan.4
Commit message (Collapse)AuthorAgeFilesLines
* tl(4) appears to support long frames.yar2007-05-091-0/+1
| | | | Tested by: Peter Jeremy <peterjeremy at optushome dot com dot au>
* Tell that nve(4) has got support for VLAN_MTU.yar2007-05-071-1/+2
| | | | Touch Dd.
* Update info on VLAN support in hardware:yar2007-05-021-0/+4
| | | | | - bce(4) and cxgb(4) can do hardware acceleration; - fwe(4) and nfe(4) can handle long frames.
* Having finished with vlan(4) for today, touch .Dd.yar2007-04-241-1/+1
|
* We shouldn't say that most Ethernet drivers don't support long frames,yar2007-04-241-1/+1
| | | | as it's no longer true.
* "Long frame" is the well-known term found in h/w documentationyar2007-04-241-5/+5
| | | | from several vendors, so prefer it over other synonyms.
* Now that we list hardware that supports vlan(4) natively,yar2007-04-241-57/+19
| | | | we don't need to repeat that for each device listed.
* xl(4) can support long frames on all chip revisions now.yar2007-04-241-2/+3
|
* de(4) ceased to support the BIG_PACKET hack.yar2007-04-241-8/+0
|
* tl(4) in fact has no signs of long frame support.yar2007-04-241-2/+0
|
* vr(4) gained VLAN_MTU support.yar2007-04-241-0/+4
|
* Add msk(4) to the list of devices supporting full VLAN processingyongari2006-12-131-1/+2
| | | | in the hardware.
* Fix incorrect .Xr syntax I introduced in the previous commit.yar2006-08-121-1/+1
| | | | | Noticed by: ru X-MFC with: rev. 1.31
* Optionally pad outgoing frames to the minimum of 60 bytes (excl. FCS)yar2006-08-111-2/+24
| | | | | | | | | | before tagging them. This can help to work around brain-damage in some switches that fail to pad a frame after untagging it if its length drops below the minimum. This option is blessed by IEEE Std 802.1Q (2003 Ed.), paragraph C.4.4.3.b. It's controlled by sysctl net.link.vlan.soft_pad. Idea by: az MFC after: 1 week
* Add stge(4) to the list of devices supporting full VLAN processingyongari2006-07-251-1/+2
| | | | in the hardware.
* Add le(4) to the list of devices supporting VLAN-sized frames natively.marius2006-01-311-1/+5
|
* Record sk(4) as having native support for extended VLAN frames.yar2005-10-111-0/+4
| | | | | PR: kern/79998 MFC after: 1 month
* Work around an apparent mdoc(7) bug.trhodes2005-10-071-6/+4
| | | | | Spotted by: marius Discussed with: ru
* Add gem(4) to the list of devices supporting VLAN-sized frames nativelymarius2005-08-281-1/+5
| | | | | | (since sys/dev/gem/if_gem.c rev. 1.34). MFC after: 1 week
* Break long lines and kill a few instances of EOL whitespace.trhodes2005-07-211-1/+2
| | | | Noticed by: ru
* Add a "Load module on start up" comment, similar to mac_*.4 pages[1].trhodes2005-07-191-5/+17
| | | | | | | | Quote .Cd and .Nd text. Bump doc date. Requested by: some user through ru Supported by: ru, dwmalone, brueffer
* Bump the document date since its content has changed.yar2005-01-301-1/+1
|
* Revise the part on VLAN support in physical interfaces.yar2005-01-301-19/+32
| | | | MFC after: 1 week
* Update the list of VLAN-aware interface types.yar2005-01-301-1/+3
| | | | MFC after: 3 days
* (fast) ethernet -> (Fast) Ethernetbrueffer2004-12-211-2/+2
| | | | MFC after: 3 days
* BUGS should stay below SEE ALSO.yar2004-11-151-4/+4
| | | | Pointed out by: ru (wearing the mdoc(7) police hat on his head)
* Mention in the BUGS section that EVFILT_NETDEV eventsyar2004-11-151-3/+13
| | | | | | on vlan(4) will be noticed only if the parent uses miibus(4). Pointed out by: John-Mark Gurney <gurney_j -at- resnet.uoregon.edu>
* gx(4) is gone, remove any referencesbrueffer2004-11-081-1/+0
|
* Bump the date.yar2004-10-041-1/+1
| | | | Reminded by: ru
* Document that vlan(4) requires miibus(4) now.yar2004-10-041-0/+2
|
* Touch .Dd because the content of the manpage has been updated.yar2004-05-271-1/+1
| | | | Pointed out by: ru
* Update the status of VLAN support in interface drivers.yar2004-05-261-0/+9
|
* Mention that hme(4) natively supports oversized frames.joerg2004-05-061-0/+4
|
* document auto-recognition of device capabilitiessam2002-11-151-19/+8
|
* Language style and grammar fixes.yar2002-08-271-23/+17
| | | | | | tx(4) has gained native support for vlan(4). MFC after: 3 days
* Update the section on NIC driver support status.yar2002-08-271-3/+9
| | | | MFC after: 3 days
* Document the fact that these devices are allocated at runtime usingbrooks2002-05-291-0/+12
| | | | cloning and point to two common methods of doing so.
* Add VLAN for the dc(4) driver (ie long frame). The patch is 2 parts.ambrisko2002-01-161-0/+4
| | | | | | | | | | | | | | | | One to notify the system that the MTU for VLAN can be 1500 so the vlan will automatically be configured with a 1500 MTU the other is to ignore the error case if the received frame is to long. The frame size notification came from code in the SIS driver, and the support for long frames derived from the NetBSD Tulip driver. Tested on: 4 port D-Link adapter DFE-570TX 4 Intel 21143 Netgear card with 82c169 PNIC 10/100BaseTX Reviewed by: ru (manpage), wpaul (not objected to), archie Approved by: imp Obtained from: NetBSD
* Note sis(4) VLAN support.jhay2001-12-051-1/+6
| | | | MFC after: 7 days
* Update the status of VLAN support in the ethernet drivers.yar2001-10-051-2/+7
|
* Make vlan(4) loadable, unloadable, and clonable. As a side effect,brooks2001-09-051-1/+1
| | | | | | | interfaces must now always enable VLAN support. Reviewed by: jlemon MFC after: 3 weeks
* Removed comments that simply describe what is seen by ``cvs di -rRELENG_4''ru2001-08-171-3/+0
| | | | of that file. (xtp(4) has already been MFC'ed.)
* mdoc(7) police: markup nits.ru2001-08-081-4/+5
|
* Finally add the manpage for the IEEE 802.1Q VLANyar2001-07-281-0/+143
network interface.
OpenPOWER on IntegriCloud