I got mine to work by going to System Settings -->Network, then changing the DNS so it doesn't get DNS info automatically from the router. Then go into the DNS tab and manually type in the ip address of an external DNS server.
For example, I have DSL at home and the router hands out DHCP and DNS server settings. The router was handing out the correct ip address and it was handing out 192.168.0.1 for DNS as a primary and a 205.*.*.* for a secondary DNS. I had to remove 192.168.0.1 address and just use the 205.*.*.* as the primary.
Then I had to shutdown completely, reboot, then go back to the Network settings and Activate the connection.
I am using Red Hat Enterprise Linux 3 (kernel 2.4.21-27).
I am trying to install the madwifi drivers. I am having lots of trouble with it... can you please tell me how you installed the drivers? (step by step would be preferred since I'm new to Linux).
I have 2 options to install it: RPM package from
http://atrpms.net/dist/el3/madwifi/
or the .TGZ package I got from a link in the Aicrack Readme.
I tried to install the RPM but I'm getting dependency errors. I'm using a Dell laptop (Pentium M on an Intel motherboard)
For the 2nd option, I've tried to follow the Install and Readme files but it seems confusing.
Requirements
============
o sharutils (especially uudecode tool)
o kernel sources of running kernel
o Wireless Extensions support (14 or later, 17 preferred)
o Sysctl support
o Crypto API support (AES support is used if present, otherwise the
AES-CCMP cipher module falls back to a private implementation)
o gcc in same version as the compiled kernel, or you get problems
during module load (Invalid module format)
1. How can I check to make sure I have all the requirements met? (I am running Red Hat Enterprise Linux 3 kernel 2.4.21-27)
The driver is built using the Linux kernel build mechanism. This means you must have some part of the kernel source distribution installed on the machine where you want to build the driver. In particular, the kernel include files and configuration must be available as well as the build scripts. If you built your kernel
from source then this will be present. Otherwise you may need to install some materials from your distribution.
Most people can just type:
trouble% make
at the top level to build all the modules for the system where you are building.
2. I've tried to run that but it says "command not found".