1.\" $NetBSD: otus.4,v 1.3 2010/11/04 13:22:20 wiz Exp $ 2.\" $OpenBSD: otus.4,v 1.14 2010/08/18 18:49:36 damien Exp $ 3.\" 4.\" Copyright (c) 2009 Damien Bergamini <damien.bergamini@free.fr> 5.\" 6.\" Permission to use, copy, modify, and distribute this software for any 7.\" purpose with or without fee is hereby granted, provided that the above 8.\" copyright notice and this permission notice appear in all copies. 9.\" 10.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES 11.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF 12.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR 13.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES 14.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN 15.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF 16.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 17.\" 18.Dd November 4, 2010 19.Dt OTUS 4 20.Os 21.Sh NAME 22.Nm otus 23.Nd Atheros USB IEEE 802.11a/g/n wireless network device 24.Sh SYNOPSIS 25.Cd "otus* at uhub? port ?" 26.Sh DESCRIPTION 27The 28.Nm 29driver supports USB 2.0 wireless network devices based on Atheros 30Communications AR9001U chipset. 31.Pp 32The AR9001U chipset is made of an AR9170 MAC/Baseband 33and an AR9101 (1T2R), AR9102 (2T2R) or AR9104 (dual-band 2T2R) 34Radio. 35.Pp 36These are the modes the 37.Nm 38driver can operate in: 39.Bl -tag -width "IBSS-masterXX" 40.It BSS mode 41Also known as 42.Em infrastructure 43mode, this is used when associating with an access point, through 44which all traffic passes. 45This mode is the default. 46.It monitor mode 47In this mode the driver is able to receive packets without 48associating with an access point. 49This disables the internal receive filter and enables the card to 50capture packets from networks which it wouldn't normally have access to, 51or to scan for access points. 52.El 53.Pp 54The 55.Nm 56driver can be configured to use 57Wired Equivalent Privacy (WEP) or 58Wi-Fi Protected Access (WPA-PSK and WPA2-PSK). 59WPA is the de facto encryption standard for wireless networks. 60It is strongly recommended that WEP 61not be used as the sole mechanism 62to secure wireless communication, 63due to serious weaknesses in it. 64.Pp 65The 66.Nm 67driver can be configured at runtime with 68.Xr ifconfig 8 69or on boot with 70.Xr ifconfig.if 5 . 71.Sh FILES 72The driver needs at least version 1.0 of the following firmware files, 73which are loaded when an interface is attached: 74.Pp 75.Bl -tag -width Ds -offset indent -compact 76.It /libdata/firmware/if_otus/otus-init 77.It /libdata/firmware/if_otus/otus-main 78.El 79.Pp 80Although these firmware files are freely redistributable, their usage 81is restricted. 82.Sh HARDWARE 83The following adapters should work: 84.Pp 85.Bl -tag -width Ds -offset indent -compact 86.It Arcadyan WN7512 87.\" .It AVM FRITZ!WLAN USB Stick N 88.It CACE AirPcap \&Nx 89.It D-Link DWA-130 rev \&D1 90.It D-Link DWA-160 rev A1 91.It D-Link DWA-160 rev A2 92.It IO-Data WN-GDN/US2 93.It NEC Aterm WL300NU-G 94.It Netgear WNDA3100 95.It Netgear WN111 v2 96.It Planex GW-US300 97.It TP-Link TL-WN821N 98.It Ubiquiti SR71 USB 99.It Unex DNUA-81 100.It Z-Com UB81 101.It Z-Com UB82 102.It ZyXEL NWD-271N 103.El 104.Sh EXAMPLES 105The following 106.Xr ifconfig.if 5 107example configures otus0 to join whatever network is available on boot, 108using WEP key 109.Dq 0x1deadbeef1 , 110channel 11, obtaining an IP address using DHCP: 111.Bd -literal -offset indent 112nwkey 0x1deadbeef1 chan 11 113dhcp 114.Ed 115.Pp 116Join an existing BSS network, 117.Dq my_net : 118.Bd -literal -offset indent 119# ifconfig otus0 192.168.1.1 netmask 0xffffff00 nwid my_net 120.Ed 121.Pp 122To use WPA, see 123.Xr wpa_supplicant 8 124and 125.Xr wpa_supplicant.conf 5 . 126.Sh DIAGNOSTICS 127.Bl -diag 128.It "otus%d: error %d, could not read firmware %s" 129For some reason, the driver was unable to read the microcode file from the 130filesystem. 131The file might be missing or corrupted. 132.It "otus%d: device timeout" 133A frame dispatched to the hardware for transmission did not complete in time. 134The driver will reset the hardware. 135This should not happen. 136.El 137.Sh SEE ALSO 138.Xr arp 4 , 139.Xr ifmedia 4 , 140.\" .Xr intro 4 , 141.Xr netintro 4 , 142.Xr usb 4 , 143.Xr wpa_supplicant.conf 5 , 144.Xr ifconfig 8 , 145.Xr wpa_supplicant 8 , 146.Pp 147Atheros Communications AR9001U-2NX/AR9001U-2NG/AR9001U-NG: 148.Pa http://www.atheros.com/pt/bulletins/AR9001USBBulletin.pdf 149.Sh HISTORY 150The 151.Nm 152driver first appeared in 153.Ox 4.6 . 154It was ported to 155.Nx 156by Anon Ymous and first appeared in 157.Nx 6.0 . 158.Sh AUTHORS 159The 160.Nm 161driver was written by 162.An Damien Bergamini Aq damien@openbsd.org 163based on source code licensed under the ISC released in 2008 by Atheros 164Communications for Linux. 165.Sh CAVEATS 166The AVM FRITZ!WLAN USB Stick N adapter is currently not supported. 167.Pp 168The 169.Nm 170driver does not support any of the 802.11n capabilities offered by the 171AR9001U chipset. 172Additional work is required in 173.Xr ieee80211 9 174before those features can be supported. 175.Pp 176The 177.Nm 178driver also does not currently support EDCA as this is missing in the 179.Nx 180network stack. 181The hooks for it are in the driver code. 182