I downloaded the latest madwifi drivers on cvs and I can activate the WAG511 card with:
ifconfig ath0 up
However when I do this iwconfig gives:
lo no wireless extensions.
sit0 no wireless extensions.
ath0 IEEE 802.11g ESSID:"xxxx"
Mode:Managed Frequency:2.462GHz Access Point: 00:09:5B:CD:28:A4
Bit Rate=1Mb/s Tx-Power:off Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:73/94 Signal level:-22 dBm Noise level:-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Which looks ok, but I still have no connection to the internet and when I ping my access point I receive the message:
connect: Network is unreachable
ifconfig -a gives:
ath0 Link encap:Ethernet HWaddr 00:09:5B:D2:F3:FE
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::209:5bff:fed2:f3fe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1430 Metric:1
RX packets:9597 errors:64871 dropped:0 overruns:0 frame:64871
TX packets:6993 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:688775 (672.6 Kb) TX bytes:309324 (302.0 Kb)
Interrupt:11 Memory:c89e4000-c89f4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:153 errors:0 dropped:0 overruns:0 frame:0
TX packets:153 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13192 (12.8 Kb) TX bytes:13192 (12.8 Kb)
sit0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
When I enter dmesg, the relevant part I get is:
ath0: association failed (reason 1) for 00:09:5b:cd:28:a4
When I googled I found this (
http://article.gmane.org/gmane.linux...wifi.user/3326):
"Two common reasons for association failure:
...
2. the Madwifi driver includes the WME information element in its
association request. The AP does not ignore it (as it should) and fails the
association. The only fix in this case is to disable sending the WME info element. In cvs HEAD this is done by compiling with NO_WME. In the next stable release that merges WME and WPA, this can be done with a sysctl."
Now do you think this is the answer and how do I compile the cvs HEAD with NO_WME? Any other suggestions would be welcome.
Cheers
donk:)