I’ve spent many hour trying to get different wireless cards up and running on Linux. I’m no Linux guru, but can hackaway with the best of them to get something to work. I’m posting this for my friend Matt who is working to get his wireless card up and running. In a previous post we worked on getting the MADWIFI drivers installed to work with an Atheros chipset. Since we were unsuccessful with getting this running on his laptop (an old Dell Insipiron 4000) I decided to get my old D-Link DWL-650 Rev. P configured. Below outlines the steps I had to take to get the D-Link running on Fedora Core 4. This howto assumes the kernel source and gcc compiler are installed.
1. The first thing I had to do was download the linux-wlan drivers, which can be found here. I grabbed the latest version (0.2.3) and saved it to my home directory.
2. I then unzipped the file using tar -xf linux-wlan-ng-0.2.3.tar.gz
3. I then changed to root su - and entered the password. There are some modules that need root access to be installed.
4. Next I changed into the linux-wlan directory cd linux-wlan-ng-0.2.3 and configured the driver ./Configure
5. I was then prompted with a whole bunch of yes/no questions and pretty much accepted all the defaults. Since this is a PCMCIA card the first question asked if I’d like to build the PCMCIA driver. I accepted the default, which was yes.
6. As the configure scripts says….”type make and pray”
7. After successful compilation I typed make install
The drivers were successfully compiled and installed so it was time to configure the card to work with my router. In this example I’m going to assume a router name of “linksys” with WEP enabled.
8. Next I edited /etc/modprobe.conf, which loads wireless the driver on boot. I added the line alias wlan0 prism2_cs to the bottom of the file.
9. I know the steps are dragging out, but hang in there because it’s worth it! I then had to modify the wireless configuration file found at /etc/wlan/wlan.conf. I changed the SSID_wlan0=”" to SSID_wlan0=”linksys”. This means we need to create a configuration file named wlancfg-linksys.
10. Since there’s a wlancfg-DEFAULT file in current directory I did cp wlancfg-DEFAULT wlancfg-linksys. If you’re not using encryption you should be done with this step. Since I was using encryption I made the following modifications to the wlancfg-linksys file (modifications in bold):
#=======WEP===========================================
# [Dis/En]able WEP. Settings only matter if PrivacyInvoked is true
lnxreq_hostWEPEncrypt=false # true|false
lnxreq_hostWEPDecrypt=false # true|false
dot11PrivacyInvoked=true # true|false
dot11WEPDefaultKeyID=0 # 0|1|2|3
dot11ExcludeUnencrypted=true # true|false, in AP this means WEP is required.
# If PRIV_GENSTR is not empty, use PRIV_GENTSTR to generate
# keys (just a convenience)
# add-ons/ in the tarball contains other key generators.
PRIV_GENERATOR=/sbin/nwepgen # nwepgen, Neesus compatible
PRIV_KEY128=false # keylength to generate
PRIV_GENSTR=”"# or set them explicitly. Set genstr or keys, not both.
dot11WEPDefaultKey0=12:34:56:78:90 # format: xx:xx:xx:xx:xx or
dot11WEPDefaultKey1= # xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
dot11WEPDefaultKey2= # e.g. 01:20:03:40:05 or
dot11WEPDefaultKey3= # 01:02:03:04:05:06:07:08:09:0a:0b:0c:0d
#=======SELECT STATION MODE===================
IS_ADHOC=n # y|n, y – adhoc, n – infrastructure
#======= INFRASTRUCTURE STATION ===================
# What kind of authentication?
AuthType=”sharedkey” # opensystem | sharedkey (requires WEP)
11. I then added an interface config file in /etc/sysconfig/network-scripts called ifcfg-wlan0, which contained the following:
DEVICE=wlan0
USERCTL=yes
ONBOOT=yes
BOOTPROTO=dhcp
12. And last but not least. I had to disabled selinux to get this to work. This was done by editing /etc/selinux/config and changing the line that says SELINUX=enforcing to SELINUX=permissive.
If I remember correctly that was everything I did to configure my D-Link DWL-650 card. When the moment of truth comes I highly recommend rebooting your machine. You could restart network and pcmcia services, but there’s always something magical that happens when you do a full reboot.I just wanted to give a special thanks to
Ken Kowalski for his help with the selinux trick as well as showing me that iwconfig does not work with the linux-wlan drivers. No that’s not really Ken’s photo and I can’t believe there’s actually another Ken Kowalski, but he should get a kick out of this if he reads it.One last note once your wireless is up and running. You can scan for wireless networks with the following command
iwlist wlan0 scan. If you find this post at all helpful then show some love and by the Linux Cookbook:

Read More