PERFORCE change 139982 for review
Sam Leffler
sam at FreeBSD.org
Sun Apr 13 18:50:18 UTC 2008
http://perforce.freebsd.org/chv.cgi?CH=139982
Change 139982 by sam at sam_ebb on 2008/04/13 18:49:46
first pass at updating; clean out lots of dreck
Affected files ...
.. //depot/projects/vap/share/man/man4/ath.4#4 edit
.. //depot/projects/vap/share/man/man4/ipw.4#3 edit
.. //depot/projects/vap/share/man/man4/iwi.4#3 edit
.. //depot/projects/vap/share/man/man4/ral.4#3 edit
.. //depot/projects/vap/share/man/man4/rum.4#3 edit
.. //depot/projects/vap/share/man/man4/ural.4#3 edit
.. //depot/projects/vap/share/man/man4/wi.4#4 edit
.. //depot/projects/vap/share/man/man4/wpi.4#3 edit
.. //depot/projects/vap/share/man/man4/zyd.4#3 edit
Differences ...
==== //depot/projects/vap/share/man/man4/ath.4#4 (text+ko) ====
@@ -1,5 +1,5 @@
.\"-
-.\" Copyright (c) 2002-2004 Sam Leffler, Errno Consulting
+.\" Copyright (c) 2002-2008 Sam Leffler, Errno Consulting
.\" All rights reserved.
.\""
.\" Redistribution and use in source and binary forms, with or without
@@ -12,9 +12,6 @@
.\" similar to the "NO WARRANTY" disclaimer below ("Disclaimer") and any
.\" redistribution must be conditioned upon including a substantially
.\" similar Disclaimer requirement for further binary redistribution.
-.\" 3. Neither the names of the above-listed copyright holders nor the names
-.\" of any contributors may be used to endorse or promote products derived
-.\" from this software without specific prior written permission.
.\"
.\" NO WARRANTY
.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
@@ -31,7 +28,7 @@
.\"
.\" $FreeBSD: src/share/man/man4/ath.4,v 1.44 2008/01/28 18:08:40 brueffer Exp $
.\"/
-.Dd December 7, 2006
+.Dd April 13, 2008
.Dt ATH 4
.Os
.Sh NAME
@@ -59,7 +56,7 @@
.Nm
driver provides support for wireless network adapters based on
the Atheros AR5210, AR5211, and AR5212 programming APIs.
-These APIs are used by a wide variety of chips; all chips with
+These APIs are used by a wide variety of chips; most all chips with
a PCI and/or CardBus interface are supported.
Chip-specific support is provided by the Atheros Hardware Access Layer
(HAL), that is packaged separately.
@@ -97,26 +94,32 @@
.Xr ifconfig 8
as shown below.
.Pp
-By default, the
-.Nm
-driver configures the card for BSS operation (aka infrastructure
-mode).
-This mode requires the use of an access point (base station).
-.Pp
-The
-.Nm
-driver also supports the standard IBSS point-to-point mode
-where stations can communicate amongst themselves without the
-aid of an access point.
-.Pp
-The driver may also be configured to operate in hostap mode.
-In this mode a host may function as an access point (base station).
-Access points are different than operating in IBSS mode.
-They operate in BSS mode.
-They allow for easier roaming and bridge all Ethernet traffic such
-that machines connected via an access point appear to be on the local
-Ethernet segment.
-.Pp
+The driver supports
+.Cm station ,
+.Cm adhoc ,
+.Cm adhoc-demo ,
+.Cm hostap ,
+.Cm wds ,
+and
+.Cm monitor
+mode operation.
+Multiple
+.Cm hostap
+virtual interfaces may be configured for simultaneous
+use on cards that use a 5212 part.
+When multiple interfaces are configured each may have a separate
+mac address that is formed by setting the U/L bits in the mac
+address assigned to the underlying device.
+Any number of
+.Cm wds
+virtual interfaces may be configured together with
+.Cm hostap
+interfaces.
+Multiple
+.Cm station
+interfaces may be operated together with
+.Cm hostap
+interfaces to construct a wireless repeater device.
For more information on configuring this device, see
.Xr ifconfig 8 .
.Pp
@@ -127,8 +130,10 @@
.Sh HARDWARE
The
.Nm
-driver supports all Atheros Cardbus or PCI cards,
+driver supports most Atheros Cardbus or PCI cards,
except those that are based on the AR5005VL chipset.
+More recent parts may require a hal that is not part of
+.Fb .
.Pp
A list of cards that are supported can be found at
.Pa http://customerproducts.atheros.com/customerproducts/default.asp .
@@ -144,38 +149,37 @@
.Pp
Join a specific BSS network with WEP encryption:
.Bd -literal -offset indent
-ifconfig ath0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
+ifconfig wlan0 create wlandev ath0
+ifconfig wlan0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
wepmode on wepkey 0x8736639624
.Ed
.Pp
Join/create an 802.11b IBSS network with network name
.Dq Li my_net :
.Bd -literal -offset indent
-ifconfig ath0 inet 192.168.0.22 netmask 0xffffff00 ssid my_net \e
- mode 11b mediaopt adhoc
+ifconfig wlan0 create wlandev ath0 wlanmode adhoc
+ifconfig wlan0 inet 192.168.0.22 netmask 0xffffff00 ssid my_net \e
+ mode 11b
.Ed
.Pp
Create an 802.11g host-based access point:
.Bd -literal -offset indent
-ifconfig ath0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
- mode 11g mediaopt hostap
+ifconfig wlan0 create wlandev ath0 wlanmode hostap
+ifconfig wlan0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
+ mode 11g
.Ed
.Pp
-Create an 802.11a host-based access point with WEP enabled:
+Create two virtual 802.11a host-based access points, one with
+with WEP enabled and one with no security, and bridge them to
+the fxp0 (wired) device:
.Bd -literal -offset indent
-ifconfig ath0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e
- wepmode on wepkey 0x1234567890 mode 11a mediaopt hostap
-.Ed
-.Pp
-Create a host-based wireless bridge to fxp0:
-.Bd -literal -offset indent
-ifconfig ath0 inet up ssid my_ap media DS/11Mbps mediaopt hostap
-sysctl net.inet.ip.check_interface=0
-ifconfig bridge0 create
-ifconfig bridge0 addm ath0 addm fxp0 up
+ifconfig wlan0 create wlandev ath0 wlanmode hostap \e
+ ssid paying-customers wepmode on wepkey 0x1234567890 \e
+ mode 11a up
+ifconfig wlan1 create wlandev ath0 wlanmode hostap bssid \e
+ ssid freeloaders up
+ifconfig bridge0 create addm wlan0 addm wlan1 addm fxp0 up
.Ed
-.Pp
-This will give you the same functionality as an access point.
.Sh DIAGNOSTICS
.Bl -diag
.It "ath%d: unable to attach hardware; HAL status %u"
@@ -252,15 +256,18 @@
This should not happen.
.El
.Sh SEE ALSO
-.Xr altq 4 ,
-.Xr an 4 ,
-.Xr arp 4 ,
.Xr ath_hal 4 ,
-.Xr netintro 4 ,
+.Xr intro 4 ,
+.Xr cardbus 4 ,
.Xr pcic 4 ,
-.Xr wi 4 ,
.Xr wlan 4 ,
+.Xr wlan_ccmp 4 ,
+.Xr wlan_tkip 4 ,
+.Xr wlan_wep 4 ,
+.Xr wlan_xauth 4 ,
+.Xr hostapd 8 ,
.Xr ifconfig 8 ,
+.Xr wpa_supplicant 8 .
.Sh HISTORY
The
.Nm
@@ -281,17 +288,7 @@
.Sh BUGS
There is no software retransmit; only hardware retransmit is used.
.Pp
-The driver does not fully enable power-save operation of the chip;
-consequently power use is suboptimal.
+The driver does not fully enable power-save operation of the chip
+in station mode; consequently power use is suboptimal (e.g. on a laptop).
.Pp
-The driver honors the regulatory domain programmed into the EEPROM of a
-device and does not support overriding this setting.
-This is done to insure compliance with local regulatory agencies when
-operating as an access point.
-Unfortunately this also means that devices purchased for use in one locale
-may not be usable in another.
-Changes are planned to remove this restriction when operating in station mode.
-.Pp
WPA is not supported for 5210 parts.
-.Pp
-Atheros' SuperG functionality is not supported.
==== //depot/projects/vap/share/man/man4/ipw.4#3 (text+ko) ====
@@ -25,7 +25,7 @@
.\"
.\" $FreeBSD: src/share/man/man4/ipw.4,v 1.17 2007/11/13 16:42:22 brueffer Exp $
.\"
-.Dd March 6, 2007
+.Dd April 13, 2008
.Os
.Dt IPW 4
.Sh NAME
@@ -37,27 +37,24 @@
kernel configuration file:
.Bd -ragged -offset indent
.Cd "device ipw"
+.Cd "device ipwfw"
.Cd "device pci"
.Cd "device wlan"
.Cd "device firmware"
.Ed
.Pp
Alternatively, to load the driver as a
-module at boot time, place the following lines in
+module at boot time, place the following line in
.Xr loader.conf 5 :
.Bd -literal -offset indent
if_ipw_load="YES"
-wlan_load="YES"
-firmware_load="YES"
.Ed
.Pp
-In both cases, place the following lines in
+In both cases, place the following line in
.Xr loader.conf 5
-to load the firmware modules:
+to acknowledge the firmware license (see below):
.Bd -literal -offset indent
-ipw_bss_load="YES"
-ipw_ibss_load="YES"
-ipw_monitor_load="YES"
+legal.intel_ipw.license_ack=1
.Ed
.Sh DESCRIPTION
The
@@ -65,19 +62,23 @@
driver provides support for the
.Tn Intel
PRO/Wireless 2100 MiniPCI network adapter.
-.Pp
-By default, the
.Nm
-driver configures the adapter for BSS operation (aka infrastructure mode).
-This mode requires the use of an access point.
-.Pp
+supports
+.Cm station ,
+.Cm adhoc ,
+and
+.Cm monitor
+mode operation.
+Only one virtual interface may be configured at any time.
For more information on configuring this device, see
.Xr ifconfig 8 .
.Pp
-This driver requires firmware to be loaded before it will work.
-For the loaded firmware to work the license at
+This driver requires the firmware built with the
+.Nm ipwfw
+module to work.
+For the loaded firmware to be enabled for use the license at
.Pa /usr/share/doc/legal/intel_ipw/LICENSE
-must be agreed to and the following line be added to
+must be agreed by adding the following line to
.Xr loader.conf 5 :
.Pp
.Dl "legal.intel_ipw.license_ack=1"
@@ -90,22 +91,25 @@
.Sh EXAMPLES
Join an existing BSS network (i.e., connect to an access point):
.Pp
-.Dl "ifconfig ipw0 inet 192.168.0.20 netmask 0xffffff00"
+.Bd -literal -offset indent
+ifconfig wlan create wlandev ipw0 inet 192.168.0.20 \e
+ netmask 0xffffff00
+.Ed
.Pp
Join a specific BSS network with network name
.Dq Li my_net :
.Pp
-.Dl "ifconfig ipw0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net"
+.Dl "ifconfig wlan create wlandev ipw0 ssid my_net up"
.Pp
-Join a specific BSS network with 40-bit WEP encryption:
+Join a specific BSS network with 64-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig ipw0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
- wepmode on wepkey 0x1234567890 weptxkey 1
+ifconfig wlan create wlandev ipw0 ssid my_net \e
+ wepmode on wepkey 0x1234567890 weptxkey 1 up
.Ed
.Pp
-Join a specific BSS network with 104-bit WEP encryption:
+Join a specific BSS network with 128-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig ipw0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
+ifconfig wlan create wlandev ipw0 wlanmode adhoc ssid my_net \e
wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
.Ed
.Sh DIAGNOSTICS
@@ -124,8 +128,9 @@
The driver failed to load the firmware image using the
.Xr firmware 9
subsystem.
-Verify that the necessary firmware modules are loaded and the
-license agreement
+Verify the
+.Xr ipwfw 4
+firmware module is installed and the license agreement
.Xr loader 8
tunable has been set.
.It "ipw%d: could not load microcode"
@@ -136,14 +141,16 @@
This should not happen.
.El
.Sh SEE ALSO
-.Xr altq 4 ,
-.Xr iwi 4 ,
+.Xr ipwfw 4 ,
.Xr pci 4 ,
.Xr wlan 4 ,
-.Xr wpi 4 ,
-.Xr ifconfig 8
+.Xr wlan_ccmp 4 ,
+.Xr wlan_tkip 4 ,
+.Xr wlan_wep 4 ,
+.Xr ifconfig 8 ,
+.Xr wpa_supplicant 8 .
.Sh AUTHORS
-The
+The original
.Nm
driver was written by
.An Damien Bergamini Aq damien at FreeBSD.org .
==== //depot/projects/vap/share/man/man4/iwi.4#3 (text+ko) ====
@@ -25,7 +25,7 @@
.\"
.\" $FreeBSD: src/share/man/man4/iwi.4,v 1.19 2007/11/13 16:42:22 brueffer Exp $
.\"
-.Dd March 6, 2007
+.Dd Apri 13, 2008
.Os
.Dt IWI 4
.Sh NAME
@@ -33,31 +33,28 @@
.Nd "Intel PRO/Wireless 2200BG/2225BG/2915ABG IEEE 802.11 driver"
.Sh SYNOPSIS
To compile this driver into the kernel,
-place the following lines in your
+include the following lines in your
kernel configuration file:
.Bd -ragged -offset indent
.Cd "device iwi"
+.Cd "device iwifw"
.Cd "device pci"
.Cd "device wlan"
.Cd "device firmware"
.Ed
.Pp
Alternatively, to load the driver as a
-module at boot time, place the following lines in
+module at boot time, place the following line in
.Xr loader.conf 5 :
.Bd -literal -offset indent
if_iwi_load="YES"
-wlan_load="YES"
-firmware_load="YES"
.Ed
.Pp
-In both cases, place the following lines in
+In both cases, place the following line in
.Xr loader.conf 5
-to load the firmware modules:
+to acknowledge the firmware license (see below):
.Bd -literal -offset indent
-iwi_bss_load="YES"
-iwi_ibss_load="YES"
-iwi_monitor_load="YES"
+legal.intel_iwi.license_ack=1
.Ed
.Sh DESCRIPTION
The
@@ -65,19 +62,23 @@
driver provides support for
.Tn Intel
PRO/Wireless 2200BG/2915ABG MiniPCI and 2225BG PCI network adapters.
-.Pp
-By default, the
.Nm
-driver configures the adapter for BSS operation (aka infrastructure mode).
-This mode requires the use of an access point.
-.Pp
+supports
+.Cm station ,
+.Cm adhoc ,
+and
+.Cm monitor
+mode operation.
+Only one virtual interface may be configured at any time.
For more information on configuring this device, see
.Xr ifconfig 8 .
.Pp
-This driver requires firmware to be loaded before it will work.
-For the loaded firmware to work the license at
+This driver requires the firmware built with the
+.Nm iwifw
+module to work.
+For the loaded firmware to be enabled for use the license at
.Pa /usr/share/doc/legal/intel_iwi/LICENSE
-must be agreed to and the following line be added to
+must be agreed by adding the following line to
.Xr loader.conf 5 :
.Pp
.Dl "legal.intel_iwi.license_ack=1"
@@ -90,22 +91,25 @@
.Sh EXAMPLES
Join an existing BSS network (i.e., connect to an access point):
.Pp
-.Dl "ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00"
+.Bd -literal -offset indent
+ifconfig wlan create wlandev iwi0 inet 192.168.0.20 \e
+ netmask 0xffffff00
+.Ed
.Pp
Join a specific BSS network with network name
.Dq Li my_net :
.Pp
-.Dl "ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net"
+.Dl "ifconfig wlan create wlandev iwi0 ssid my_net up"
.Pp
Join a specific BSS network with 64-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
- wepmode on wepkey 0x1234567890 weptxkey 1
+ifconfig wlan create wlandev iwi0 ssid my_net \e
+ wepmode on wepkey 0x1234567890 weptxkey 1 up
.Ed
.Pp
Join a specific BSS network with 128-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
+ifconfig wlan create wlandev iwi0 wlanmode adhoc ssid my_net \e
wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
.Ed
.Sh DIAGNOSTICS
@@ -114,7 +118,7 @@
The driver will reset the hardware.
This should not happen.
.It "iwi%d: firmware error"
-The onboard microcontroller crashes for some reason.
+The onboard microcontroller crashed for some reason.
The driver will reset the hardware.
This should not happen.
.It "iwi%d: timeout waiting for firmware initialization to complete"
@@ -124,8 +128,9 @@
The driver failed to load the firmware image using the
.Xr firmware 9
subsystem.
-Verify that the necessary firmware modules are loaded and the
-license agreement
+Verify the
+.Xr iwifw 4
+firmware module is installed and the license agreement
.Xr loader 8
tunable has been set.
.It "iwi%d: could not load boot firmware"
@@ -141,14 +146,16 @@
This should not happen.
.El
.Sh SEE ALSO
-.Xr altq 4 ,
-.Xr ipw 4 ,
+.Xr iwifw 4 ,
.Xr pci 4 ,
.Xr wlan 4 ,
-.Xr wpi 4 ,
-.Xr ifconfig 8
+.Xr wlan_ccmp 4 ,
+.Xr wlan_tkip 4 ,
+.Xr wlan_wep 4 ,
+.Xr ifconfig 8 ,
+.Xr wpa_supplicant 8 .
.Sh AUTHORS
-The
+The original
.Nm
driver was written by
.An Damien Bergamini Aq damien at FreeBSD.org .
==== //depot/projects/vap/share/man/man4/ral.4#3 (text+ko) ====
@@ -15,7 +15,7 @@
.\"
.\" $FreeBSD: src/share/man/man4/ral.4,v 1.13 2007/09/10 17:54:14 brueffer Exp $
.\"
-.Dd September 10, 2007
+.Dd April 13, 2008
.Os
.Dt RAL 4
.Sh NAME
@@ -27,7 +27,10 @@
kernel configuration file:
.Bd -ragged -offset indent
.Cd "device ral"
+.Cd "device ralfw"
.Cd "device wlan"
+.Cd "device wlan_amrr"
+.Cd "device firmware"
.Ed
.Pp
Alternatively, to load the driver as a
@@ -63,6 +66,31 @@
The transmit speed is user-selectable or can be adapted automatically by the
driver depending on the received signal strength and on the number of hardware
transmission retries.
+.Pp
+.Nm
+supports
+.Cm station ,
+.Cm adhoc ,
+.Cm hostap ,
+.Cm wds ,
+and
+.Cm monitor
+mode operation.
+Only one
+.Cm hostap
+virtual interface may be configured at a time.
+Any number of
+.Cm wds
+virtual interfaces may be configured together with a
+.Cm hostap
+interface.
+Multiple
+.Cm station
+interfaces may be operated together with a
+.Cm hostap
+interface to construct a wireless repeater device.
+For more information on configuring this device, see
+.Xr ifconfig 8 .
.Sh HARDWARE
The
.Nm
@@ -163,22 +191,27 @@
.Sh EXAMPLES
Join an existing BSS network (i.e., connect to an access point):
.Pp
-.Dl "ifconfig ral0 inet 192.168.0.20 netmask 0xffffff00"
+.Dl "ifconfig wlan create wlandev ral0 inet 192.168.0.20 netmask 0xffffff00"
.Pp
Join a specific BSS network with network name
.Dq Li my_net :
.Pp
-.Dl "ifconfig ral0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net"
+.Bd -literal -offset indent
+ifconfig wlan create wlandev ral0 inet 192.168.0.20 \e
+ netmask 0xffffff00 ssid my_net
+.Ed
.Pp
Join a specific BSS network with 40-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig ral0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
+ifconfig wlan create wlandev ral0 inet 192.168.0.20 \e
+ netmask 0xffffff00 ssid my_net \e
wepmode on wepkey 0x1234567890 weptxkey 1
.Ed
.Pp
Join a specific BSS network with 104-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig ral0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
+ifconfig wlan create wlandev ral0 inet 192.168.0.20 \e
+ netmask 0xffffff00 ssid my_net \e
wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
.Ed
.Sh DIAGNOSTICS
@@ -194,13 +227,16 @@
This should not happen.
.El
.Sh SEE ALSO
-.Xr altq 4 ,
-.Xr arp 4 ,
+.Xr intro 4 ,
.Xr cardbus 4 ,
-.Xr netintro 4 ,
-.Xr pci 4 ,
.Xr wlan 4 ,
-.Xr ifconfig 8
+.Xr wlan_ccmp 4 ,
+.Xr wlan_tkip 4 ,
+.Xr wlan_wep 4 ,
+.Xr wlan_xauth 4 ,
+.Xr hostapd 8 ,
+.Xr ifconfig 8 ,
+.Xr wpa_supplicant 8 .
.Rs
.%T "Ralink Technology"
.%O http://www.ralinktech.com/
@@ -210,17 +246,8 @@
.Nm
driver first appeared in
.Ox 3.7 .
-.Sh CAVEATS
-PCI
-.Nm
-adapters seem to require a PCI 2.2 compliant motherboard and will likely not
-work with PCI 2.1 only motherboard.
-.Pp
-The
-.Nm
-driver does not implement frame aggregation.
.Sh AUTHORS
-The
+The original
.Nm
driver was written by
.An Damien Bergamini Aq damien at FreeBSD.org .
==== //depot/projects/vap/share/man/man4/rum.4#3 (text+ko) ====
@@ -16,7 +16,7 @@
.\"
.\" $FreeBSD: src/share/man/man4/rum.4,v 1.3 2007/09/07 15:28:39 brueffer Exp $
.\"
-.Dd September 7, 2007
+.Dd April 13, 2008
.Os
.Dt RUM 4
.Sh NAME
@@ -45,11 +45,11 @@
.Sh DESCRIPTION
The
.Nm
-driver supports USB 2.0 and PCI Express Mini Card wireless adapters based on the
-Ralink RT2501USB and RT2601USB chipsets.
+driver supports USB 2.0 and PCI Express Mini Card wireless adapters
+based on the Ralink RT2501USB and RT2601USB chipsets.
.Pp
-Ralink PCI Express Mini Card adapters show up as normal USB 2.0 devices and are
-thus handled by the
+Ralink PCI Express Mini Card adapters show up as normal USB 2.0
+devices and are thus handled by the
.Nm
driver.
.Pp
@@ -58,15 +58,27 @@
It consists of two integrated chips, an RT2571W MAC/BBP and an RT2528 or
RT5226 radio transceiver.
.Pp
-The RT2601USB chipset consists of two integrated chips, an RT2671 MAC/BBP and
-an RT2527 or RT5225 radio transceiver.
-This chipset uses the MIMO (multiple-input multiple-output) technology with
-multiple antennas to extend the operating range of the adapter and to achieve
-higher throughput.
+The RT2601USB chipset consists of two integrated chips, an RT2671
+MAC/BBP and an RT2527 or RT5225 radio transceiver.
+This chipset uses the MIMO (multiple-input multiple-output) technology
+with multiple antennas to extend the operating range of the adapter
+and to achieve higher throughput.
+.Pp
+.Nm
+supports
+.Cm station ,
+.Cm adhoc ,
+.Cm hostap ,
+and
+.Cm monitor
+mode operation.
+Only one virtual interface may be configured at any time.
+For more information on configuring this device, see
+.Xr ifconfig 8 .
.Sh HARDWARE
The
.Nm
-driver supports USB 2.0 and PCI Express Mini Card wireless
+driver supports USB 2.0 wireless
adapters based on the Ralink RT2501USB and RT2601USB chipsets,
including:
.Pp
@@ -108,22 +120,25 @@
.Sh EXAMPLES
Join an existing BSS network (i.e., connect to an access point):
.Pp
-.Dl "ifconfig rum0 inet 192.168.0.20 netmask 0xffffff00"
+.Bd -literal -offset indent
+ifconfig wlan create wlandev rum0 inet 192.168.0.20 \e
+ netmask 0xffffff00
+.Ed
.Pp
Join a specific BSS network with network name
.Dq Li my_net :
.Pp
-.Dl "ifconfig rum0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net"
+.Dl "ifconfig wlan create wlandev rum0 ssid my_net up"
.Pp
-Join a specific BSS network with 40-bit WEP encryption:
+Join a specific BSS network with 64-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig rum0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
- wepmode on wepkey 0x1234567890 weptxkey 1
+ifconfig wlan create wlandev rum0 ssid my_net \e
+ wepmode on wepkey 0x1234567890 weptxkey 1 up
.Ed
.Pp
-Join a specific BSS network with 104-bit WEP encryption:
+Join a specific BSS network with 128-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig rum0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
+ifconfig wlan create wlandev rum0 wlanmode adhoc ssid my_net \e
wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
.Ed
.Sh DIAGNOSTICS
@@ -135,13 +150,18 @@
This should not happen.
.El
.Sh SEE ALSO
-.Xr altq 4 ,
-.Xr arp 4 ,
+.Xr intro 4 ,
.Xr netintro 4 ,
.Xr usb 4 ,
.Xr wlan 4 ,
.Xr wlan_amrr 4 ,
-.Xr ifconfig 8
+.Xr wlan_ccmp 4 ,
+.Xr wlan_tkip 4 ,
+.Xr wlan_wep 4 ,
+.Xr wlan_xauth 4 ,
+.Xr ifconfig 8 ,
+.Xr hostapd 8 ,
+.Xr wpa_supplicant 8 .
.Rs
.%T "Ralink Technology"
.%O http://www.ralinktech.com/
@@ -151,16 +171,8 @@
.Nm
driver first appeared in
.Ox 4.0 .
-.Sh CAVEATS
-.Pp
-The
-.Nm
-driver supports automatic control of the transmit speed in BSS mode only.
-Therefore the use of a
-.Nm
-adapter in Host AP mode is discouraged.
.Sh AUTHORS
-The
+The original
.Nm
driver was written by
.An Niall O'Higgins Aq niallo at openbsd.org
==== //depot/projects/vap/share/man/man4/ural.4#3 (text+ko) ====
@@ -15,7 +15,7 @@
.\"
.\" $FreeBSD: src/share/man/man4/ural.4,v 1.15 2007/09/10 17:54:14 brueffer Exp $
.\"
-.Dd September 10, 2007
+.Dd April 13, 2008
.Os
.Dt URAL 4
.Sh NAME
@@ -52,6 +52,18 @@
The RT2522, RT2523, RT2524, RT2525, RT2525e and RT2526 radio transceivers
operate in the 2.4GHz band (802.11b/g) whereas the RT5222 is a dual-band radio
transceiver that can operate in the 2.4GHz and 5.2GHz bands (802.11a).
+.Pp
+.Nm
+supports
+.Cm station ,
+.Cm adhoc ,
+.Cm hostap ,
+and
+.Cm monitor
+mode operation.
+Only one virtual interface may be configured at any time.
+For more information on configuring this device, see
+.Xr ifconfig 8 .
.Sh HARDWARE
The
.Nm
@@ -94,22 +106,25 @@
.Sh EXAMPLES
Join an existing BSS network (i.e., connect to an access point):
.Pp
-.Dl "ifconfig ural0 inet 192.168.0.20 netmask 0xffffff00"
+.Bd -literal -offset indent
+ifconfig wlan create wlandev ural0 inet 192.168.0.20 \e
+ netmask 0xffffff00
+.Ed
.Pp
Join a specific BSS network with network name
.Dq Li my_net :
.Pp
-.Dl "ifconfig ural0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net"
+.Dl "ifconfig wlan create wlandev ural0 ssid my_net up"
.Pp
-Join a specific BSS network with 40-bit WEP encryption:
+Join a specific BSS network with 64-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig ural0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
- wepmode on wepkey 0x1234567890 weptxkey 1
+ifconfig wlan create wlandev ural0 ssid my_net \e
+ wepmode on wepkey 0x1234567890 weptxkey 1 up
.Ed
.Pp
-Join a specific BSS network with 104-bit WEP encryption:
+Join a specific BSS network with 128-bit WEP encryption:
.Bd -literal -offset indent
-ifconfig ural0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
+ifconfig wlan create wlandev ural0 wlanmode adhoc ssid my_net \e
wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
.Ed
.Sh DIAGNOSTICS
@@ -119,13 +134,18 @@
This should not happen.
.El
.Sh SEE ALSO
-.Xr altq 4 ,
-.Xr arp 4 ,
+.Xr intro 4 ,
.Xr netintro 4 ,
.Xr usb 4 ,
.Xr wlan 4 ,
.Xr wlan_amrr 4 ,
-.Xr ifconfig 8
+.Xr wlan_ccmp 4 ,
+.Xr wlan_tkip 4 ,
+.Xr wlan_wep 4 ,
+.Xr wlan_xauth 4 ,
+.Xr ifconfig 8 ,
+.Xr hostapd 8 ,
+.Xr wpa_supplicant 8 .
.Rs
.%T "Ralink Technology"
.%O http://www.ralinktech.com/
@@ -135,14 +155,8 @@
.Nm
driver first appeared in
.Ox 3.7 .
-.Sh CAVEATS
-.Pp
-The
-.Nm
-driver does not support automatic adaptation of the transmit speed in IBSS
-and HostAP operating modes.
.Sh AUTHORS
-The
+The original
.Nm
driver was written by
.An Damien Bergamini Aq damien at FreeBSD.org .
==== //depot/projects/vap/share/man/man4/wi.4#4 (text+ko) ====
@@ -31,12 +31,12 @@
.\" $FreeBSD: src/share/man/man4/wi.4,v 1.74 2008/01/28 18:08:41 brueffer Exp $
.\" $OpenBSD: wi.4tbl,v 1.14 2002/04/29 19:53:50 jsyn Exp $
.\"
-.Dd July 16, 2005
+.Dd April 13, 2008
.Dt WI 4
.Os
.Sh NAME
.Nm wi
-.Nd "Lucent Hermes, Intersil PRISM and Spectrum24 IEEE 802.11 driver"
+.Nd "Lucent Hermes, and Intersil PRISM IEEE 802.11 driver"
.Sh SYNOPSIS
To compile this driver into the kernel,
place the following lines in your
@@ -55,74 +55,30 @@
.Sh DESCRIPTION
The
.Nm
-driver provides support for wireless network adapters based around
-the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil
-Prism-3, and Symbol Spectrum24 chipsets.
-All five chipsets provide a similar interface to the driver.
-.Pp
-Supported features include 802.11 and 802.3 frames, power management, BSS,
-IBSS, WDS and old-style Lucent ad-hoc operation modes.
-Cards based on the Intersil PRISM chips also support a host-based
-access point mode which allows a card to act as a normal access point
-(with some assistance from the
-.Nm
-driver).
-The Lucent Hermes and Symbol Spectrum24 chipsets do not contain this
-functionality.
-The PRISM family of chips do not support the WDS functionality.
+driver provides support for 802.11b wireless network adapters based around
+the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, and Intersil
+Prism-3 chipsets.
+All chipsets provide a similar interface to the driver.
+Only the Intersil chipsets support access point operation.
+Functionality, such as WPA support, depends on the specific version
+of the firmware used.
All host/device interaction is via programmed I/O, even on those cards
that support a DMA interface.
.Pp
-The
-.Nm
-driver encapsulates all IP and ARP traffic as 802.11 frames, however
-it can receive either 802.11 or 802.3 frames.
-Transmit speed is selectable between 1Mbps, 2Mbps, 5.5 Mbps and 11Mbps
-depending on your hardware.
-Most hardware supports 11Mbps where the signal quality allows, but
-falls back to slower speeds when it does not.
-Except for the Lucent WaveLAN Bronze cards, all cards supported by the
-.Nm
-driver support WEP for encryption.
-To enable encryption, use
-.Xr ifconfig 8
-as shown below.
+For more information on configuring this device, see
+.Xr ifconfig 8 .
.Pp
-By default, the
.Nm
-driver configures the card for BSS operation (aka infrastructure
-mode).
-This mode requires the use of an access point (base station).
-.Pp
-The
-.Nm
-driver also supports a point-to-point mode
-where stations can communicate amongst themselves without the
-aid of an access point.
-Note that there are two possible point-to-point modes.
-One mode, referred to as
-.Dq "ad-hoc demo mode" ,
-or
-.Dq "legacy Lucent ad-hoc mode" ,
-predates the IEEE 802.11 specification and so may not interoperate
-with cards from different vendors.
-The standardized point-to-point mode is called IBSS (or confusingly
-just ad-hoc mode), but is not supported by cards with very old
-firmware revisions.
-If your cards supports IBSS mode, it is recommended that you use it in
-preference to the
-.Dq "ad-hoc demo mode"
-in new installations.
-.Pp
-Cards supported by the driver based on the Intersil PRISM family of chips also
-have a host-based access point mode which allows the card to
-act as an access point (base station).
-Access points are different than operating in IBSS mode.
-They operate in BSS mode.
-They allow for easier roaming and bridge all Ethernet traffic such
-that machines connected via an access point appear to be on the local
-Ethernet segment.
-.Pp
+supports
+.Cm station ,
+.Cm adhoc ,
+.Cm adhoc-demo ,
+.Cm hostap ,
+and
+.Cm monitor
+mode operation.
+Only one
+virtual interface may be configured at a time.
For more information on configuring this device, see
.Xr ifconfig 8 .
.Pp
@@ -151,7 +107,6 @@
.Pp
.Bl -column -compact "Linksys Instant Wireless WPC11 2.5" "Spectrum24" "PCI or PCMCIA"
>>> TRUNCATED FOR MAIL (1000 lines) <<<
More information about the p4-projects
mailing list