Re: NetworkManager and rt2x00
- From: Sam Morris <sam robots org uk>
- To: networkmanager-list gnome org
- Subject: Re: NetworkManager and rt2x00
- Date: Tue, 5 Dec 2006 20:10:55 +0000 (UTC)
On Tue, 05 Dec 2006 14:46:50 -0500, Dan Williams wrote:
> On Tue, 2006-12-05 at 14:19 +0000, Sam Morris wrote:
>> On Mon, 2006-12-04 at 20:29 -0500, Darren Albers wrote:
>> > While I am not an expert I do see a lot of strange messages and it
>> > doesn't look like the card is even able to associate:
>> > Dec 4 19:04:20 xerces NetworkManager:
>> > <information>^Iwpa_supplicant(2730): wpa_driver_wext_associate
>> > Dec 4 19:04:20 xerces NetworkManager:
>> > <information>^Iwpa_supplicant(2730): Association request to the driver
>> > failed
>> >
>> > Two questions:
>> > 1) Can you associate by stopping NetworkManager and bringing up
>> > WPA_Supplicant manually?
>>
>> Yes. I therefore assume that the rt2x00 driver has some idiosyncrasies
>> that prevent the commands that are issued by NM from working.
>
> Can you post the command that you use to execute wpa_supplicant?
Sorry, I misread what you asked above. I meant that I am able to associate
if I avoid NM and wpa_supplicant alltogether and do this:
# ip link set up dev wlan0
# iwlist wlan0 scan
# iwconfig wlan0 ssid morris1
# iwconfig wlan0 key $wep_key
# iwconfig wlan0 ap 00:30:BD:FD:B7:87
I am also able to associate if I tell NM to connect to the network and
then quickly issue just the 'iwconfig ap' command above.
>> > If you need instructions on doing this I can provide them
I can try this for you if you let me know what commands to issue.
--
Sam Morris
http://robots.org.uk/
PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]