Hi Dan et al
  Thanks for the response.  I have two out of three answers requested, 
inline

Dan O'Reilly wrote:
> On Tue, Jun 16, 2009 at 7:58 AM, Steve Nahn<n...@mit.edu> wrote:
>   
>> 1) Although the Associate method in wnettools.py has changed, I still
>> have the same problem - trying to set the Access point doesn't work -
>> commenting out the Misc.Run() command for this action and I can connect
>> to any open wifi network
>>     
>
> Does iwconfig give you an error if you try to do this by hand?
>
>   
No - I can execute the same commands by hand using iwconfig and 
everything works fine.
>> 2) However, I cannot connect to a WEP encrypted network.  The odd thing
>> here is the iwconfig parameters are set correctly, including the WEP key
>> (using the external tools and wext driver) so after wicd fails with "bad
>> password" I can start dhclient by hand and connect immediately.
>>
>> [n...@sammy ~]$ sudo iwconfig ra0
>> ra0       Ralink STA  ESSID:"TG374"  Nickname:"RT2860STA"
>>          Mode:Managed  Frequency=2.437 GHz  Access Point: 00:1F:90:D4:A7:90
>>          Bit Rate=54 Mb/s
>>          RTS thr:off   Fragment thr:off
>>          Encryption key:DEAD-BEEF-AD
>>          Link Quality=100/100  Signal level:-52 dBm  Noise level:-81 dBm
>>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>>          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>>
>> So, something in the wpa_supplicant is failing, but I am not exactly
>> sure how to test this.  Any ideas?  I tried using the RALINK legacy
>> driver but it didn't really work, and I've browsed a fair amount of
>> forums but haven't come up with any hints for debugging.  Could it be
>> that wicd just doesn't work for my hardware?
>>     
>
> It sounds like your driver is behaving strangely.  You can try running
> the commands you see in the log by hand to debug, with some minor
> adjustments:
> /sbin/dhclient -v -r eth0
> ifconfig eth0 0.0.0.0
> /sbin/ip route flush dev eth0
> ifconfig eth0 down
> ifconfig eth0 up
> ifconfig ra0 down
> /sbin/dhclient -v -r ra0
> ifconfig ra0 0.0.0.0
> wpa_cli -i ra0 terminate
> /sbin/ip route flush dev ra0
> iwconfig ra0 mode Managed
> ifconfig ra0 up
> wpa_supplicant -i ra0 -c /var/lib/wicd/configurations/001f90d4a790 -D
> wext (run this in its own window, also note the -B option has been
> removed, which causes wpa_supplicant to fork into the background)
> iwconfig ra0 essid TG374
> iwconfig ra0 channel 6
> iwconfig ra0 ap 00:1F:90:D4:A7:90
>
> Then watch the wpa_supplicant window for stuff that looks like an error.
>
>   
Will try this this evening.

> Also, does the encryption key in iwconfig actually show up as DEAD-BEEF-AD?
>   
No - DEAD-BEEF-AD was just a over-paranoid security measure on my part.  
The actual WEP Key is reported correctly by iwconfig

Thanks

Steve


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
wicd-devel mailing list
wicd-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicd-devel

Reply via email to