Wireless network configuration
Template:I18n links start Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n links end
- 1 Introduction
- 2 Part I: Identify your card and appropriate Driver
- 2.1 First steps
- 2.2 How it Works
- 2.3 Installation
- 2.3.1 If you have wired internet available
- 2.3.2 If you have only wireless internet available
- 2.3.3 Wireless Quickstart
- 2.3.4 Drivers and Firmware
- 126.96.36.199 wlan-ng
- 188.8.131.52 rt2870
- 184.108.40.206 rtl8180
- 220.127.116.11 rt2x00
- 18.104.22.168 RT2500
- 22.214.171.124 RT61
- 126.96.36.199 RT73 (ie Ralink RT2571)
- 188.8.131.52 madwifi
- 184.108.40.206 ath9k
- 220.127.116.11 ipw2100 and ipw2200
- 18.104.22.168 iwl3945, iwl4965 and iwl5000-series
- 22.214.171.124 ipw3945 (Deprecated Method)
- 126.96.36.199 orinoco
- 188.8.131.52 ndiswrapper
- 184.108.40.206 prism54
- 220.127.116.11 ACX100/111
- 18.104.22.168 BCM43XX
- 22.214.171.124 b43
- 126.96.36.199 broadcom-wl
- 188.8.131.52 rtl8187
- 184.108.40.206 zd1211rw
- 2.4 Test Installation
- 3 Part II: Wireless Management
- 4 See Also
- 5 Additional Resources
Configuring wireless under Arch Linux (or any distro for that matter) is a two-part process. The first part is to identify and ensure the correct driver for your wireless device is installed, (they are available on the installation media, so make sure you install them) and configure the interface. The second is choosing a method of managing wireless connections. This article covers both parts, and provides additional links to wireless management tools.
Part I: Identify your card and appropriate Driver
- Check to see whether the Linux kernel supports your hardware. You can find your card with 'lspci | grep -i net'. The Ubuntu Wiki has an extensive list of wireless cards and whether or not they are supported by available linux kernel drivers.
- zd1201-based card like ZyXEL B-220
- wlan-ng supports quite a lot of chipsets; check here first.
- madwifi for Atheros chipsets (AR5210, AR5211, AR5212 and AR5213)
- ath5k is a completely FOSS driver (without a binary blob, unlike Madwifi) for Atheros chipsets.
- ath9k is Atheros' official driver for the newer 11n chipsets (AR5416, AR5418, AR9160, AR9280, AR9281, AR9285).
- rt2x00 project for a unified driver for Ralink's rt2400, rt2500, and rt2570 chipsets (beta).
- Ralink Linux Support for drivers for Ralink chipsets direct from the manufacturer.
- rt2x00 project for better-maintained versions of Ralink's own drivers ("legacy drivers" on the site).
- ipw2100 for Intel Pro/Wireless 2100 Mini PCI
- ipw2200 for Intel Pro/Wireless 2200 Mini PCI
- iwlwifi-3945-ucode for Intel Pro/Wireless 3945 AB/G Mini PCI-E
- iwlwifi-4965-ucode for Intel Pro/Wireless 4965 AB/G Mini PCI-E
- orinoco for some Prism 2-based cards
- prism54 for Prism 54-based cards
- bcm43xx for Broadcom 43xx-based cards (old)
- b43 for Broadcom 43xx-based cards
- broadcom-wl for recent 43xx Broadcom cards not supported by bcm43xx or b43.
- Check the Linux Wireless Support page for your hardware or in The Linux Questions hardware compatibility list (HCL), which also has a good list of Linux-friendly hardware
- Also, this page has a matrix of supported hardware.
- If the hardware is supported only under Windows
- If your hardware is not listed anywhere
- Try a web search for the exact model name of your hardware with the word "linux" - and feel free to ask for help on the forums
- There is a chance that your hardware will not function under GNU/Linux (however, this is rarely the case)
How it Works
The Arch kernel is modular, meaning many of the drivers for machine hardware reside on the hard drive and are available as modules. At boot, udev takes an inventory of your hardware. Udev will load appropriate modules (drivers) for your corresponding hardware, and the driver, in turn, will allow creation of a kernel interface.
The interface name for different drivers and chipsets will vary. Some examples are wlan0, eth1, and ath0.
- Note: Udev is not perfect. If the proper module is not loaded by udev on boot, simply modprobe it and add the module name to etc/rc.conf on the MODULES= line.
If you have wired internet available
If you have wired ethernet available, and are simply adding wireless functionality to an existing system, and did not include wireless_tools during initial installation, use pacman to install:
# pacman -S wireless_tools
The drivers' corresponding package names are all highlighted in bold on this page. The packages can be installed during initial package selection on the Arch installation media and can also be installed later with pacman, e.g.:
# pacman -S madwifi
If you have only wireless internet available
The wireless_tools package is now available as part of the base system and is also on the live installation media (CD/USB stick image) under the base-devel category.
You cannot initialize wireless hardware without these userspace tools, so ensure they are installed from the installer media, (during package selection), especially if you have no other means of networking other than wirelessly. Otherwise, you will be stuck in a recursion when you reboot your newly installed Arch system; you will need wireless_tools and drivers, but in order to get them, you will need wireless_tools and drivers.
The general procedure will be:
- Identify your interface and appropriate module:
# hwdetect --show-net
# lspci | grep -i net
- Ensure the module is loaded with
lsmod | grep <name_or_part_of_name_of_module>e.g.:
# lsmod | grep ath
- Ensure the driver has created a usable interface:
- Bring the interface up with
ifconfig <interface> up. e.g.:
# ifconfig ath0 up
- (Optional) Scan for available access points:
# iwlist ath0 scan | less
- Specify the id of the wireless network with
iwconfig <interface> essid "<youressid>". Or, if using WEP;
iwconfig <interface> essid "<youressid>" key <yourwepkey>(give the essid (the 'network name') of the network in quotes), e.g.:
# iwconfig ath0 essid "linksys" key 0241baf34c
If your WEP key is ASCII, prefix with
# iwconfig ath0 essid linksys key s:mywepkey
- Request an IP address with
dhcpcd <interface>. e.g.:
# dhcpcd ath0
- Ensure you can route:
$ ping -c 3 www.google.com
Refer to Part II to ensure a permanent configuration solution for your system.
If you are using WPA, refer to WPA/WPA2 below.
Drivers and Firmware
Methods and procedures for installing drivers for various chipsets are covered below. In addition, certain chipsets require the installation of corresponding firmware. (Also covered below).
This driver support PRISM based cards, which are hard to find now. The PRISM card is an IEEE 802.11 compliant 2.4 GHz DSSS WLAN network interface card that uses the Intersil PRISM chipset for its radio functions and the AMD PCNet-Mobile chip (AM79C930) for its Media Access Controller (MAC) function. The supported adapters can be found from here: http://www.linux-wlan.org/docs/wlan_adapters.html.gz
For wlan-ng you do not need the wireless_tools package as mentioned above. Instead you will need to learn the tools in the wlan-ng26-utils package: wlancfg and wlanctl-ng.
Realtek rtl8180 PCI/Cardbus 802.11b now fully supported in the kernel
Unified driver for Ralink chipsets (replaces rt2500,rt61,rt73 etc). Compatible with stable wpa_supplicant using the wext driver interface. This driver is now (as of 2.6.24) part of the mainline kernel, and can be manually loaded as follows...
modprobe rt2500pci(replace rt2500pci with your hardware e.g. rt2400pci, rt2500usb, rt61pci, rt73usb)
Some chips require a firmware file, which can be installed like this:
pacman -S rt2x00-rt71w-fw
pacman -S rt2x00-rt61-fw
..depending on the chipset. See the rt2x00 wiki page.
For Ralink's PCI/PCMCIA based rt2500 series chipsets (the first generation of Ralink chips to support 802.11g).
Supports standard iwconfig tools for unencrypted and WEP connections, although it can be quite sensitive to the order of commands. wpa_supplicant is not supported using the standard wext interface. The driver does support WPA (using hardware encryption), but in a non-standard way. The trunk version of wpa_supplicant (0.6.x) appears to include special support for this driver, and it is also possible to negotiate a WPA connection manually using iwpriv commands. See these instructions for details. The same applies for RT61 and RT73 below.
As of August 24, 2008, the rt2x00 driver (rt2500pci module) is preferred and will work with wpa_supplicant using the wext driver, if you are using the old rt2500 module, you may need to disable it in your rc.conf fileand make sure you are loading the rt2500pci and rt2x00lib and rt2x00pci modules.
For PCI/PCMCIA cards based on Ralink's later generation of 802.11g chipsets (including those supporting proprietary MIMO modes). "RT61" has now been made largely obsolete by the in-kernel rt2x00 driver (see above), although there may be cases where the legacy driver performs better.
See the RT61 wiki page.
For USB devices based on Ralink's later generation of 802.11g chipsets (including those supporting proprietary MIMO modes).
Several USB WiFi dongles use this chipset, including the Linksys WUSB54GC and the Belkin Wireless G USB key (F5D7050 v3000) .
"RT73" has now been made largely obsolete by the in-kernel rt2x00 driver (see above), although there may be cases where the legacy driver performs better. See the RT73 wiki page.
The module is called ath_pci. The newer module, ath5k, will eventually phase out ath_pci.
for the older driver, or:
for the development version. Note that not all cards work with ath5k yet.
If using ath_pci, you may need to blacklist ath5k by adding it to the MODULES= array in /etc/rc.conf, and subsequently prefixing it with a bang (!):
MODULES=(!ath5k forcedeth snd_intel8x0 ... ...)
Some users may need to use the countrycode option when loading the MadWifi driver in order to use channels and transmit power settings that are legal in their country/region. In the Netherlands, for example, you would load the module like this:
modprobe ath_pci countrycode=528
You can verify the settings with the iwlist command. See man iwlist and the CountryCode page on the MadWifi wiki. To have this setting automatically applied during boot, add the following to /etc/modprobe.conf:
options ath_pci countrycode=528
ATTENTION: I had to remove the countrycode option completely or the ath0 device wasn't created (andyrtr, kernel 2.6.21)!
ath9k is Atheros' officially supported driver for the newer 11n chipsets. All of the chips with 11n capabilities are supported, with a maximum throughput around 180 Mbps. To see a complete list of supported hardware, check this page.
Working modes: Station, AP and Adhoc.
ath9k has been part of the kernel as of 2.6.27. But it has undergone some heavy development, and the changes haven't propagated to the mainline kernel tree yet. The best solution would be to use the compat-wireless package for now. A mailing list exists for support and development related discussions.
ipw2100 and ipw2200
Depending on which of the chips you have, use either:
pacman -S ipw2100-fw
pacman -S ipw2200-fw
If installing after initial Arch installation, you may need to reboot for the firmware to be loaded.
If at boot up you see that your firmware is not being loaded, then you probably need to add the 'firmware' hook to your /etc/mkinitcpio.conf file and regenerate your kernel image with:
mkinitcpio -g /boot/kernel26.img
To enable radiotap interface:
# rmmod ipw2200 # modprobe ipw2200 rtap_iface=1
iwl3945, iwl4965 and iwl5000-series
Intel's open source WiFi drivers for Linux (See iwlwifi) will work for both the 3945 and 4965 chipsets since kernel v2.6.24. And iwl5000-series chipsets (including 5100BG, 5100ABG, 5100AGN, 5300AGN and 5350AGN) module has been supported since kernel 2.6.27, by the intree driver iwlagn.
# pacman -S iwlwifi-3945-ucode
# pacman -S iwlwifi-4965-ucode
# pacman -S iwlwifi-5000-ucode
If MOD_AUTOLOAD is set to yes in /etc/rc.conf (it is by default) that should be all that's required. Simply check for the presence of the drivers by running ifconfig -a from a terminal. There should be a listing for wlan0.
To manually load the driver at startup, edit /etc/rc.conf as root and add iwl3945 or iwl4965 respectively to the MODULES array. For example:
MODULES=( ... b44 mii iwl3945 snd-mixer-oss ...)
The drivers should now load after a reboot, and running ifconfig -a from a terminal should report wlan0 as a new network interface.
- The windows NETw4x32 driver can be used with ndiswrapper as an alternative to the iwl3945 and ipw3945 drivers
- In some cases (specifically a Dell Latitude D620 with Arch 2008.06, though it could happen elsewhere) after installation you may have both iwl3945 and ipw3945 in your MODULES=() section of rc.conf. The card will not work with both modules loaded, so you will have to ! out the ipw3945 module and then reboot or remove the module manually before you can use your wireless card.
- By default iwl3945 is configured to only work with networks on channels 1-11. Higher ranges are not allowed in some parts of the world (US). In the EU however channels 12 and 13 are used quite common. To make iwl3945 scan for all channels, add "options cfg80211 ieee80211_regdom=EU" to /etc/modprobe.d/options. With "iwlist f" you can check which channels are allowed.
- If you want to enable more channels on Intel Wifi 5100 (and quite possible other cards too) you can do that with the crda package. After install, edit /etc/conf.d/wireless-regdom and uncomment the line where your country code is found. Add wireless-regdom to your DAEMONS in rc.conf and restart (which is the easiest thing to do). You should now, when writing sudo iwlist wlan0 channel, have access to more channels (depending on your location).
ipw3945 (Deprecated Method)
# pacman -S ipw3945 ipw3945-ucode ipw3945d
To initialize the driver on startup, edit /etc/rc.conf as root and add ipw3945 to the MODULES array and ipw3945d to the DAEMONS array. For example:
MODULES=(... mii ipw3945 snd-mixer-oss ...)
DAEMONS=(syslog-ng ipw3945d network ...)
Note: The ipw3945d daemon must be inserted BEFORE network and dhcdbd/networkmanager in the array.
This should be part of the kernel package and be installed already.
Note: Some orinoco chipsets are Hermes I/II. You can use http://aur.archlinux.org/packages.php?ID=9637 to replace the orinoco driver and gain WPA support. See http://ubuntuforums.org/showthread.php?p=2154534#post2154534 for more information.
To use the driver I blacklisted orinoco_cs in rc.conf (!orinoco_cs in the modules array) and added wlags49_h1_cs to the modules array. Example:
MODULES=(!snd_pcsp !eepro100 !orinoco_cs wlags49_h1_cs)
Ndiswrapper is not a real driver, but you can use it when there are no native Linux drivers for your wireless chips. So it is very useful in some situations. To use it you need the *.inf file from your Windows driver (the *.sys file must also be present in the same directory). If you need to extract these files from an *.exe file, you can use either cabextract or wine. ndiswrapper is included on the installation CD.
Follow these steps to configure ndiswrapper.
ndiswrapper -i filename.inf ndiswrapper -l ndiswrapper -m depmod -a
Now the ndiswrapper install is almost finished; you just have to update /etc/rc.conf to load the module at boot (below is a sample of my config; yours might look slightly different):
MODULES=(ndiswrapper snd-intel8x0 !usbserial)
The important part is making sure that ndiswrapper exists on this line, so just add it alongside the other modules. It would be best to test that ndiswrapper will load now, so:
modprobe ndiswrapper iwconfig
and wlan0 should exist. Check this page if you're having problems: Ndiswrapper installation wiki.
Download the firmware driver for your appropriate card from this site. Rename the firmware file to 'isl3890'. If nonexistent, create the directory /lib/firmware and place the file 'isl3890' in it. This should do the trick. (forum source)
If that didn't work, try this:
- Reload the prism module (modprobe p54usb or modprobe p54pci, depending on your hardware)
alternatively remove your wifi card and then reconnect it
- Use the "dmesg" command, and look at the end of the output it prints out.
Look for a section looking like this:
firmware: requesting isl3887usb_bare p54: LM86 firmware p54: FW rev 220.127.116.11 - Softmac protocol 3.0
and try renaming the firmware file to the name corresponding to the part bolded here.
packages: tiacx tiacx-firmware
The driver should tell you which firmware it needs; check /var/log/messages.log or use the dmesg command.
Move the appropriate firmware to '/lib/firmware'. I did this:
ln -s /usr/share/tiacx/acx111_18.104.22.168/tiacx111c16 /lib/firmware
For another way to determine which firmware revision number to use, see the "Which firmware" section of the acx100.sourceforge wiki page page. For ACX100, you can follow the links provided there, to a table of card model number vs. "firmware files known to work"; you can figure out the rev. number you need, by looking at the suffix there. E.g. a dlink_dwl650+ uses "1.9.8.b", in which case you'd do this:
ln -s /usr/share/tiacx/acx100_1.9.8.b/* /lib/firmware
Hint: If you find that the driver is spamming your kernel log, for example because you're running Kismet with channel-hopping, you could put this in /etc/modprobe.conf:
options acx debug=0
NOTE: The open-source acx driver does not support WPA/RSN encryption. NDISWRAPPER will have to be used with the windows driver to enable the enhanced encryption. See ndiswrapper, this page, for more details.
Broadcom users that have 43xx series chipsets have a new alternative to ndiswrapper. In kernel version 2.6.17, the bcm43xx driver was introduced.
hwd -sto determine that you have an appropriate card. My output of hwd -s looked like this:
Network : Broadcom Corp.|BCM94306 802.11g NIC module: unknown
For a list of supported devices, see here.
pacman -Sy b43-fwcutterto install the firmware cutter application.
- Download the Windows driver file for your card from which to extract the firmware.
- If you download the driver from Dell's website, you must run in on a Windows machine or under WINE (it is a .exe file that extracts itself to C:\Dell\[driver numbers]). Or you may try ,  or . I just saved this file to my desktop; you won't need it after the next step.
bcm43xx-fwcutter -w /lib/firmware /home/<user>/Desktop/wl_apsta.oYou may have to create /lib/firmware first.
- Restart, and configure your device as normal. You may want to add bcm43xx into the modules section of your rc.conf file. Good luck!
This driver is the successor to the bcm43xx driver, and is included in kernel 2.6.24.
lspcito determine that you have an appropriate card. My output of looked like this:
0c:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
For a list of supported devices, see here.
Either install the "b43-firmware" package from AUR, or perform the following steps manually.
- Install the firmware cutter application from core. It is named "b43-fwcutter".
- Because now in core we have kernel >=2.6.25 we download version 22.214.171.124 of Broadcom's proprietary driver. The older version(126.96.36.199) will be drop in july.
- Unpack the compressed file.
tar xjf broadcom-wl-188.8.131.52.tar.bz2
- Change the current directory to the newly created directory, and then further to the driver folder:
- Create /lib/firmware if you don't have and then Run
b43-fwcutter -w "/lib/firmware/" wl_apsta_mimo.o
- Restart, and configure your device as normal.
MODULES=(...b43 !bcm43xx !ndiswrapper...)
For recent Broadcom 43xx cards not supported by bcm43xx or b43. Not just for 4312 cards. See the Broadcom 4312 wiki page. It is available in AUR. These chipsets are used in most Dell laptops, among others.
See the rtl8187 wiki page.
zd1211rwzd1211rw is a driver for the ZyDAS ZD1211 802.11b/g USB WLAN chipset and it is included in recent versions of the Linux kernel. See  for a list of supported devices. You only need to install the firmware for the device:
pacman -Sy zd1211-firmware
--Willey 22:32, 20 September 2008 (EDT)
After loading your driver run
and see if a wireless interface (wlanx, ethx, athx) is recognized
iwlist scan displays
Interface doesn't support scanning then you probably forgot to install the firmware.
Part II: Wireless Management
Assuming that your drivers are installed and working properly, you will need to choose a method for managing your wireless connections. The following subsections will help you decide the best way to do just that.
Procedure and tools you’ll need will depend on several factors:
- The easiness of configuration management, from a completely manual setup procedure that you’ll need to repeat at each boot to a software-managed, automatic, autostarting solution
- The encryption type (or not) that protects the wireless network
- If you need network profiles, i.e. if your computer will frequently change networks (such as a laptop)
This table shows the different methods that can be used to activate and manage a wireless network connection, depending on the encryption and management types, and the various tools that are required. Although there may be other possibilities, these are the most frequently used:
|Management||No encryption/WEP||WPA/WPA2 PSK|
|Manual, need to repeat at each computer reboot||
|Automatically managed, centralized without network profile support|| define interface in
|Automatically managed, with network profiles support|| |
Whatever your choice, you should try to connect using the manual method first. This will help you understand the different steps that are required and debug them in case a problem arose. Another tip: if possible (e.g. if you admin your wifi access point), try connecting with no encryption, to check everything works. Then try using encryption, either WEP (simpler to configure) or WPA.
The programs provided by the package wireless_tools are the basic set of tools to set up a wireless network. Moreover, if you use WPA/WPA2 encryption, you will need the package wpa_supplicant. These powerful userspace console tools work extremely well and allow complete, manual control from the shell.
These examples assume your wireless device is
wlan0 with the appropriate device name.
1. (Optional, may be required) Some cards require that the kernel interface be activated before you can use the wireless_tools:
# ifconfig wlan0 up
2. (Optional, may be required) See what access points are available:
# iwlist wlan0 scan
We assume you want to use the essid named
3. Depending on the encryption, you need to associate your wireless device with the access point to use and pass the encryption key.
- No encryption
# iwconfig wlan0 essid "MyEssid"
using an hexadecimal key:
# iwconfig wlan0 essid "MyEssid" key 1234567890
using an ascii key:
# iwconfig wlan0 essid "MyEssid" key s:asciikey
You need to edit the
/etc/wpa_supplicant.conf file as described in WPA_Supplicant. Then, issue this command:
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
This is assuming your device uses the
wext driver. If this does not work, you may need to adjust these options. Check WPA_Supplicant for more information and troubleshooting.
4. Finally, provide an IP address to the network interface. Simple examples are:
# dhcpcd wlan0
for DHCP, or
# ifconfig wlan0 192.168.0.2 # route add default gw 192.168.0.1
for static IP.
Automatic connection - Network daemon
- The /etc/rc.conf file is sourced by the network script. Therefore, you may define and configure a simple wireless setup within /etc/rc.conf for a centralized approach with wlan_<interface>="<interface> essid <essid>" and INTERFACES=(<interface1> <interface2>). The name of the network goes in place of MyEssid.
# /etc/rc.conf eth0="dhcp" wlan0="dhcp" wlan_wlan0="wlan0 essid MyEssid" # Unencrypted #wlan_wlan0="wlan0 essid MyEssid key 1234567890" # hex WEP key #wlan_wlan0="wlan0 essid MyEssid key s:asciikey" # ascii WEP key INTERFACES=(eth0 wlan0)
Not all wireless cards are
wlan0. Determine your wireless interface with ifconfig -a.
Atheros-based cards, for example, are typically
ath0, so change
wlan_ath0="ath0 essid MyEssid key 12345678"
Also define ath0 in the INTERFACES= line.)
- Alternatively, you may define wlan_<interface> within /etc/conf.d/wireless, (which is also sourced by the network script), for a de-centralized approach:
# /etc/conf.d/wireless wlan_wlan0="wlan0 essid MyEssid"
Automatic connection - netcfg
netcfg provides a versatile, robust and fast solution to networking on Arch.
It uses a profile based setup and is capable of detection and connection to a wide range of network types. This is no harder than using graphical tools. Following the directions above, you can get a list of wireless networks. Then, as with graphical tools, you will need a password.
Detailed documentation Network Profiles
Notes for developmental version Network Profiles development
Other network managers
There are a number of wireless management solutions available to Arch Linux users as an alternative to the above.
Autowifi is a daemon that configures your wireless network automatically depending on the ESSID. Once configured, no user interaction is necessary and no GUI tools are required.
For more information, see the Autowifi wiki.
Wicd is a network manager that can handle both wireless and wired connections. It is written in Python and Gtk with fewer dependencies than NetworkManager, making it an ideal solution for lightweight desktop users. Wicd is now available in the extra repository for both i686 and x86_64.
For more information, see the Wicd wiki.
NetworkManager is an advanced network management tool that is enabled by default in most popular Linux distributions. In addition to managing wired connections, NetworkManager provides worry-free wireless roaming with an easy-to-use GUI program for selecting your desired network.
For more information, see the NetworkManager wiki.
WiFi Radar is Python/PyGTK2 utility for managing wireless profiles (and only wireless). It enables you to scan for available networks and create profiles for your preferred networks.
For more information, see the Wifi Radar wiki.
Wlassistant is a very intuitive and straightforward GUI app for managing your wireless connections.
# pacman -S wlassistant
Wlassistant must be run with root privileges:
# sudo wlassistant
One method of using wlassistant is to configure your wireless card within /etc/rc.conf, specifying the access point you use most often. On startup, your card will automatically be configured for this essid, but if other wireless networks are needed/available, wlassistant can then be invoked to access them. Background the network daemon in /etc/rc.conf, by prefixing it with a @, to avoid boot delays.
- NetworkManager - The official website for NetworkManager
- WICD - The official website for WICD
- Wifi Radar - Wifi Radar information page
- An overly wordy howto that rarely helps
- The madwifi project's method of installing, good if you're having trouble doing it the Arch way