Huh. I'm using madwifi-0.9.0 with FC5 (NM 0.6.3) and it all works just fine... Except for the fact that NM gets confused with my d-link where it uses the same MAC address on 802.11(a) and 802.11(b/g) but NM doesn't think these are distinct networks...
-derek Quoting Adam Lindberg <[EMAIL PROTECTED]>: > I believe it is a problem with the madwifi driver, seems as though > they do not support the WEXT protocols, which is odd. I thought they > did. > > How do I set it up manually with wpa_supplicant? > > On 6/28/06, Tom Diehl <[EMAIL PROTECTED]> wrote: >> On Wed, 28 Jun 2006, Adam Lindberg wrote: >> >> > Hi, >> > >> > I'm using the latest CVS of NetworkManager, the latest development >> > snapshot of madwifi-ng (r1654) and the latest development snapshot of >> > wpa_supplicant (0.5.4). When trying to connect to my WPA encrypted >> > access point this happens: >> > >> > Is there any way to fix this? >> > >> >> If you figure it out I too would like to know. For me NM never sees my >> madwifi card. If I start wpa_supplicant by hand, the card comes up and will >> play for days with wpa encryption enabled. If I do not start wpa_supplicant >> by hand the card never completes the connection. Unless I plug in a network >> cable, the NM icon always shows a circle with a slash through it. >> >> I asked about this problem a few weeks ago, was asked to supply some info >> but I never heard anything after I sent the info. >> >> I am running the following versions of nm and wpa_supplicant: >> (bullwinkle pts3) $ rpm -qa | grep -i networkmanager >> NetworkManager-gnome-0.6.3-1.fc5 >> NetworkManager-glib-0.6.3-1.fc5 >> NetworkManager-0.6.3-1.fc5 >> >> (bullwinkle pts3) $ rpm -qa | grep -i wpa >> wpa_supplicant-0.4.8-10.fc5 >> >> (bullwinkle pts3) $ rpm -qa | grep net-tool >> net-tools-1.60-62.1 >> >> (bullwinkle pts3) $ rpm -qa | grep mad >> madwifi-0.1645.20060615-6 >> madwifi-module-0.1645.20060615-6_2.6.17_1.2139_FC5 >> >> This is a fully updated FC5 dell 2650 laptop. >> >> I also see the following in the logs continously: >> >> Jun 28 13:53:27 bullwinkle netplugd[1701]: ath0: ignoring event >> Jun 28 13:53:27 bullwinkle netplugd[1701]: No interface name >> Jun 28 13:53:27 bullwinkle netplugd[1701]: Callback failed >> Jun 28 13:53:30 bullwinkle netplugd[1701]: No interface name >> Jun 28 13:53:30 bullwinkle netplugd[1701]: Callback failed >> >> Does the card work for you if you start wpa_supplicant by hand?? >> >> Regards, >> >> Tom >> > > > -- > Adam Lindberg > (+46) 734 228920 > [EMAIL PROTECTED] > http://www.namsisi.com/ > _______________________________________________ > NetworkManager-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list > -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [EMAIL PROTECTED] PGP key available _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
