| wlan.4 (192139) | wlan.4 (195618) |
|---|---|
| 1.\" 2.\" Copyright (c) 2003 Tom Rhodes 3.\" All rights reserved. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" 1. Redistributions of source code must retain the above copyright --- 9 unchanged lines hidden (view full) --- 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 24.\" SUCH DAMAGE. 25.\" | 1.\" 2.\" Copyright (c) 2003 Tom Rhodes 3.\" All rights reserved. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" 1. Redistributions of source code must retain the above copyright --- 9 unchanged lines hidden (view full) --- 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 24.\" SUCH DAMAGE. 25.\" |
| 26.\" $FreeBSD: head/share/man/man4/wlan.4 192139 2009-05-15 10:11:54Z brueffer $ | 26.\" $FreeBSD: head/share/man/man4/wlan.4 195618 2009-07-11 15:02:45Z rpaulo $ |
| 27.\" | 27.\" |
| 28.Dd May 15, 2009 | 28.Dd July 8, 2009 |
| 29.Dt WLAN 4 30.Os 31.Sh NAME 32.Nm wlan 33.Nd generic 802.11 link-layer support 34.Sh SYNOPSIS 35.Cd "device wlan" 36.Sh DESCRIPTION --- 6 unchanged lines hidden (view full) --- 43.Nm 44module is required by all native 802.11 drivers as well as the 45.Xr ndis 4 46support. 47.Pp 48.Nm 49supports multi-mode devices capable of 50operating in both 2.4GHz and 5GHz bands and supports numerous | 29.Dt WLAN 4 30.Os 31.Sh NAME 32.Nm wlan 33.Nd generic 802.11 link-layer support 34.Sh SYNOPSIS 35.Cd "device wlan" 36.Sh DESCRIPTION --- 6 unchanged lines hidden (view full) --- 43.Nm 44module is required by all native 802.11 drivers as well as the 45.Xr ndis 4 46support. 47.Pp 48.Nm 49supports multi-mode devices capable of 50operating in both 2.4GHz and 5GHz bands and supports numerous |
| 51802.11 standards: 802.11a, 802.11b, 802.11g, and 802.11n. | 51802.11 standards: 802.11a, 802.11b, 802.11g, 802.11n, and 802.11s (Draft 3.0). |
| 52The WPA, 802.11i, and 802.1x security protocols are supported 53through a combination of in-kernel code and user-mode applications. 54The WME/WMM multi-media protocols are supported entirely within 55the 56.Nm 57module but require a suitably capable hardware device. 58Likewise the 802.11h specification is supported only by suitably 59capable devices. --- 18 unchanged lines hidden (view full) --- 78.Nm 79interfaces that may be created: 80.Bl -tag -width monitor 81.It Cm sta 82A client station in an infrastructure bss 83(i.e. one that associates to an access point). 84.It Cm hostap 85An access point in an infrastructure bss. | 52The WPA, 802.11i, and 802.1x security protocols are supported 53through a combination of in-kernel code and user-mode applications. 54The WME/WMM multi-media protocols are supported entirely within 55the 56.Nm 57module but require a suitably capable hardware device. 58Likewise the 802.11h specification is supported only by suitably 59capable devices. --- 18 unchanged lines hidden (view full) --- 78.Nm 79interfaces that may be created: 80.Bl -tag -width monitor 81.It Cm sta 82A client station in an infrastructure bss 83(i.e. one that associates to an access point). 84.It Cm hostap 85An access point in an infrastructure bss. |
| 86.It Cm mesh 87A mesh station in an MBSS network. |
|
| 86.It Cm adhoc 87A station in an IBSS network. 88.It Cm ahdemo 89A station operating in ``adhoc demo mode''. 90This is essentially an IBSS station that does not use management 91frames (e.g. no beacons are transmitted). 92An 93.Cm ahdemo --- 16 unchanged lines hidden (view full) --- 110.Cm hostap 111interface but that is not guaranteed; one may need to create a 112.Cm hostap 113interface that does not send beacon frames before 114.Cm wds 115interfaces may be created. 116.El 117.Pp | 88.It Cm adhoc 89A station in an IBSS network. 90.It Cm ahdemo 91A station operating in ``adhoc demo mode''. 92This is essentially an IBSS station that does not use management 93frames (e.g. no beacons are transmitted). 94An 95.Cm ahdemo --- 16 unchanged lines hidden (view full) --- 112.Cm hostap 113interface but that is not guaranteed; one may need to create a 114.Cm hostap 115interface that does not send beacon frames before 116.Cm wds 117interfaces may be created. 118.El 119.Pp |
| 118More types are planned to support 119802.11s mesh nodes (station and ap). | |
| 120Note that an interface's type cannot be changed once it is created. 121.Pp 122.Nm 123defines several mechanisms by which plugin modules may 124be used to extend its' functionality. 125Cryptographic support such as WEP, TKIP, and AES-CCMP are implemented 126as standalone modules (if not statically configured into a system) 127that register with --- 28 unchanged lines hidden (view full) --- 156defines the initial value of the debugging flags for each cloned 157.Nm 158interface; this is useful to enable debug messages during interface creation. 159.Sh COMPATIBILITY 160The module name of 161.Nm 162was used to be compatible with 163.Nx . | 120Note that an interface's type cannot be changed once it is created. 121.Pp 122.Nm 123defines several mechanisms by which plugin modules may 124be used to extend its' functionality. 125Cryptographic support such as WEP, TKIP, and AES-CCMP are implemented 126as standalone modules (if not statically configured into a system) 127that register with --- 28 unchanged lines hidden (view full) --- 156defines the initial value of the debugging flags for each cloned 157.Nm 158interface; this is useful to enable debug messages during interface creation. 159.Sh COMPATIBILITY 160The module name of 161.Nm 162was used to be compatible with 163.Nx . |
| 164.Pp 165Mesh stations follow the 802.11s Draft 3.0 specification which is 166not ratified and subject to change. 167Beware that this specification is incompatible with earlier drafts; 168and stations implementing earlier drafts (e.g. Linux) 169may not interoperate. |
|
| 164.Sh SEE ALSO 165.Xr an 4 , 166.Xr ath 4 , 167.Xr bwi 4 , 168.Xr ipw 4 , 169.Xr iwi 4 , 170.Xr iwn 4 , 171.Xr malo 4 , --- 36 unchanged lines hidden --- | 170.Sh SEE ALSO 171.Xr an 4 , 172.Xr ath 4 , 173.Xr bwi 4 , 174.Xr ipw 4 , 175.Xr iwi 4 , 176.Xr iwn 4 , 177.Xr malo 4 , --- 36 unchanged lines hidden --- |