On Sun, 2006-11-26 at 15:38 -0500, Carlos Moffat wrote: > Hi Again, > > On Sun, 2006-11-19 at 23:11 -0500, Dan Williams wrote: > > On Sun, 2006-11-19 at 22:10 -0500, Carlos Moffat wrote: > > > On Sun, 2006-11-19 at 19:06 -0500, Dan Williams wrote: > > > > On Sun, 2006-11-19 at 18:22 -0500, Carlos Moffat wrote: > > > > > Hi, > > > > > > > > > > I've been trying to track down this issue for a while. Although > the NM + > > > > > Madwifi drivers worked for a while for me (I'm using > Debian/Sid), I've > > > > > been stuck using the r1500 version of the madwifi drivers, as > any newer > > > > > version does not work. If I use a newer version, NM does not get > an IP > > > > > address from the router (no WEP, no WPA). > > > > > > > > > > The issue is discussed here: > > > > > > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385599 > > > > > > > > > > If I shut down NM, I can get an IP address from the router using > > > > > dhclient. But NM works fine with the older driver, so I'm not > sure who's > > > > > to blame here. > > > > > > > > Probably an interaction with wpa_supplicant and madwifi; can you > connect > > > > with plain wpa_supplicant? > > > > > > > > Dan > > > > > > > > > > Mmhh. Can one connect to a dhcp (no WPA, no WEP) using > wpasupplicant? > > > How does that work? > > > > Sure; wpa_supplicant just sets up the connection. So first stop > > NetworkManager, then: > > > > Put the following in /etc/wpa_supplicant.conf: > > > > ctrl_interface_group=0 > > ctrl_interface=/var/run/wpa_supplicant > > eapol_version=1 > > ap_scan=1 > > fast_reauth=1 > > network={ > > ssid="my network" > > key_mgmt=NONE > > auth_alg=OPEN > > } > > > > then execute with (as root): > > > > wpa_supplicant -ddd -iwifi0 -c/etc/wpa_supplicant.conf -Dwext > > > > and then, when it says "CONNECTED", > > > > dhclient -1 wifi0 > > > > Sorry for the late reply (Thanksgiving got in the way). So it seems > wpa_supplicant is giving me trouble. The first command doesn't ever get > to 'connected'. I've attached the output I get. > > Funny thing is, straight dhclient ath0 works, but if I do > wpa_supplicant, then cancel, and try dhclient ath0, it does not work. In > that case, I need to modprobe-out ath_pci, insert the module again, and > the dhclient ath0 works. > Ok, I think I was wrong about the second part. dhclient ath0 (no wpa_supplicant before) always works.
Carlos > Also, is -iwifi0 the correct interface, or is it -iath0? I have both... > > I appreciate any help. > > Carlos > > > > > And see what happens. > > > > > Thanks, > > > Carlos > > > > > > > > > > > Any ideas, or any users of Debian/Sid using the madwifi drivers > and NM > > > > > successfully? > > > > > > > > > > > > > > > Thanks, > > > > > Carlos > > > > > > > > > > Other Info: > > > > > > > > > > * kernel 2.6.17 (tried .16 and .18, no luck) > > > > > * 02:02.0 Ethernet controller: Atheros Communications, Inc. > AR5212 > > > > > 802.11abg NIC (rev 01) > > > > > * NM 0.6.4 > > > > > * wpasupplicant 0.5.5 > > > > > * Thinkpad T42p. > > > > > > > > > > _______________________________________________ > > > > > NetworkManager-list mailing list > > > > > [email protected] > > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > > > > > _______________________________________________ > NetworkManager-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
