|
This portal deals with the hardware installation of Wi-Fi cards in general. The installation of a card is essentially two steps that are installing the driver (also called the driver or module), and setting up your WiFi network.
Be aware that a WiFi base are operating on an electronic chip called Chipset. We can find the same chip in several different cards. Consequently, the pilot manages this chipset will be the same for all these cards Wifi.
A WiFi interface is an Ethernet interface that also gives access to the configuration parameters peculiar to the Wi-Fi. These parameters are controlled using the iwconfig program.
|
www.debian.org/doc/manuals/reference/ch-gateway.html - Debian Reference Networking Chapter |
Tools prerequisites
wireless-tools, tools for manipulating Linux Wireless Extensions (installed by default on Desktop & Laptop installation)
For system with GUI: NetworkManager (installed by default on Gnome-Desktop & Laptop installation)
module-assistant (tool to make optional module package creation easier).
wpasupplicant, client support for WPA and WPA2 networks (provides 'wpa-' options to /etc/network/interfaces)
Install Driver
Before you buy, you would check the list of hardware with Linux driver (or check for the Linux logo in the box of the WiFi card).
This section presents a list of WiFi cards sorted by manufacturer. It will show you the documentation page of the chip and thus its pilot. We recommend that you retrieve information identifying material.
This list consists of two elements: the device name and the hardware ID. The list is categorized alphabetically by the manufacturer's name and the name of your card.
See the Linux Kernel Driver DataBase for hardware and protocols know by the Linux Kernel
PCI Cards
This information is derived from command:
lspci -nn
See HowToIdentifyADevice/PCI for more information
module name |
Device name(s) |
ID |
help page |
free 1 |
airo |
|
|
? |
|
arlan |
|
|
? |
|
ath_pci |
Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01) |
168c:0013 |
|
|
ath_pci |
Netgear WG311T |
|
|
|
atmel |
|
|
? |
|
atmel_pci |
|
|
? |
|
b43 |
Broadcom Wireless (kernels >= 2.6.24) |
|
? |
|
bcm43xx |
Broadcom Wireless (4311,4312,4318,1390) |
|
? |
|
hermes |
|
|
? |
|
hostap |
|
|
? |
|
hostap_pci |
|
|
? |
|
hostap_plx |
|
|
? |
|
ipw2100 |
Intel Pro wireless 2100 |
|
? |
|
ipw2200 |
Intel Pro wireless 2200 |
|
|
|
ipw3945 |
Intel Pro wireless |
|
|
|
iwl3945 |
Intel Pro wireless 3945 |
|
|
|
orinoco |
|
|
|
|
orinoco_nortel |
|
|
? |
|
orinoco_pci |
|
|
? |
|
orinoco_plx |
|
|
? |
|
orinoco_tmd |
|
|
? |
|
rt2500 |
RaLink RT2500 chipsets |
|
? |
|
strip |
|
|
? |
|
wavelan |
|
|
? |
Legend :
= OK ;
Unsupported(No Driver) ;
= Error (Couldn't get it working); [?] Unknown, Not Test ; [-] Not-applicable
= Configuration Required;
= Only works with a proprietary driver
An extended list of PCI-IDs to kernel-module mapping is available at DeviceDatabase/PCI.
USB Cards
This information is derived from command:
lsusb
See HowToIdentifyADevice/USB for more information
module name |
Device name(s) |
help page |
non-free 1 |
?? |
Netgear MA111 |
? |
? |
usb8xxx |
? |
? |
|
rtl8187 |
? |
? |
|
zd1201 |
? |
? |
|
Linksys WUSBF54G |
|
||
rt73 |
Ralink chipset |
? |
|
Ralink RT chipset in Linksys WUSB54GC |
When you plug it, you get the rausb0 device |
? |
An extended list of USB-IDs to kernel-module mapping is available at DeviceDatabase/USB.
PCMCIA Cards
See HowToIdentifyADevice/PCMCIA for more information
module name |
Device name(s) |
help page |
non-free 1 |
airo_cs |
|
? |
|
atmel_cs |
|
? |
|
hostap_cs |
|
? |
|
netwave_cs |
|
? |
|
orinoco_cs |
Compac WL110 |
? |
|
ray_cs |
|
? |
|
spectrum_cs |
|
? |
|
wavelan_cs |
|
? |
|
wl3501_cs |
|
? |
|
prism54 |
Prism GT |
? |
Routers
module name |
Device name(s) |
help page |
non-free 1 |
Wikipedia; it isn't similar to the WRT54G; The WRT54GC is based on the Sercomm IP806SM reference design the same chipset as the current Linksys WTY54G the Airlink101 AR315W, Alloy WRT2454AP, and Hawking HWR54G. You also can use NdisWrapper |
|
Setting your WiFi device
Identify your network
- Network Name
- Parameter security
- Mode: Access Point / ad-hoc
Configure Interface: AP mode
NetworkManager is a user-friendly program to control network interfaces. It's especially useful for WiFi. (it's available for Gnome and KDE).
Otherwise, you can use /etc/network/interfaces. here's a sample fragment of :
# WiFi card section auto eth0 iface eth0 inet dhcp wpa-essid WANADOO-1418 wpa-psk "xxxxxxxxxxxxxxxxxxxxx"
See also /usr/share/doc/wireless-tools/README.Debian and README.Modes (WPA) for other examples.
Configure Interface: Ad-hoc mode
You haven't Acces Point, and you want connect 2 PC directly. Image 2 PC: calling hostA et hostB.
Wifi: Configure Wifi on your 2 PC:
iwconfig ath0 mode Ad-hoc iwconfig ath0 essid MYNETWORK
Control on your 2 PC:
iwlist ath0 scanning ath0 Scan completed : Cell 01 - Address: 02:0F:B5:4F:74:ED ESSID:"MYNETWORK" Mode:Ad-Hoc Frequency:2.412 GHz (Channel 1) Quality=42/70 Signal level=-53 dBm Noise level=-95 dBm Encryption key:off Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:bcn_int=100
IP: Configure IP on your hostA
ifconfig ath0 192.168.1.1 netmask 255.255.255.0
Configure IP on your hostB
ifconfig ath0 192.168.1.2 netmask 255.255.255.0
Control on your hostB:
ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.073 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.061 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.062 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.063 ms --- 192.168.1.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3001ms rtt min/avg/max/mdev = 0.061/0.064/0.073/0.010 ms
Check the proper functioning
Resources
DebFrWifiTopo (in french)
NdisWrapper - use Windows drivers under Debian/Linux.
External Links
Wi-fi definition
http://www.linuxwireless.org , including devives and drivers.
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/#howto The Linux Wireless Compatibility and HowTo.
Linux installation of Wi-Fi card Proxim Orinoco Silver and Belkin !F5D6020 ver.2 on kernel 2.4
Linux on the Fujitsu P2110 has an example of using pcmcia-compat.sh and /etc/network/interfaces to achieve the same end
Appaji shows how to use guessnet to switch between locations.
Configuring multiple setups and switching between them can be done with ifscheme. alwayssunny.com You can see a worked example of this. Some people think ifscheme is obsolete, and recommend network-manager instead. Others think the future is netconf
WiFiLinux LiveCD.
Welcome on 