USB IEEE 802.11a/b/g wireless network device
uath* at uhub? port ?
driver supports USB 2.0 wireless network
devices based on Atheros Communications fifth generation AR5005UG and AR5005UX
The AR5005UG chipset is made of an AR5523 multiprotocol MAC/baseband processor
and an AR2112 Radio-on-a-Chip that can operate between 2300 and 2500 MHz
The AR5005UX chipset is made of an AR5523 multiprotocol MAC/baseband processor
and an AR5112 dual band Radio-on-a-Chip that can operate between 2300 and 2500
MHz (802.11b/g) or 4900 and 5850 MHz (802.11a).
The AR5005UG and AR5005UX chipsets both have an integrated 32-bit MIPS
R4000-class processor that runs a firmware and manages, among other things,
the automatic control of the transmit rate and the calibration of the radio.
These are the modes the uath
driver can operate in:
- BSS mode
- Also known as infrastructure
mode, this is used when associating with an access point, through which
all traffic passes. This mode is the default.
- monitor mode
- In this mode the driver is able to receive packets without
associating with an access point. This disables the internal receive
filter and enables the card to capture packets from networks which it
wouldn't normally have access to, or to scan for access points.
supports hardware WEP. It can be typically
configured in one of three modes: no encryption; 40-bit encryption; or 104-bit
encryption. It is strongly recommended that WEP not be used as the sole
mechanism to secure wireless communication, due to serious weaknesses in it.
driver can be configured at runtime with
or on boot with
The following firmware file is loaded when a device is plugged:
This firmware file is not freely redistributable.
A prepackaged version of the firmware can be installed using
The following adapters should work:
The following example scans for available networks:
# ifconfig uath0 scan
The following hostname.if(5)
example configures uath0 to join network “mynwid”, using WEP key
“mywepkey”, obtaining an IP address using DHCP:
- uath0: error N, could not read firmware
- For some reason, the driver was unable to read the
firmware image from the filesystem. The file might be missing or
- uath0: could not load firmware
- An error occurred while attempting to upload the firmware
to the onboard MIPS R4000 processor.
- uath0: could not initialize
- The firmware was uploaded successfully but did not
initialize properly or in time.
- uath0: could not send command 0xXX
- An attempt to send a command to the firmware failed.
- uath0: timeout waiting for command
- A read command was sent to the firmware but the firmware
failed to reply in time.
- uath0: device timeout
- A frame dispatched to the hardware for transmission did
not complete in time. The driver will reset the hardware. This should not
driver first appeared in
driver was written by
Atheros Communications refuses to release any documentation for their products.
Atheros proprietary 108 Mbps mode (aka Super AG mode) is not supported.
driver does not attempt to do any
regulation of radio frequencies.