(Solved-sort of)Manual wifi config works, but wicd bites it

Riser Glen · 2007-08-14 02:54:50

I just don't get it. When I use the following commands:
iwconfig wlan0 essid mynet
iwconfig wlan0 key s:mykey
ifconfig wlan0 up
dhclient wlan0

I can connect to the router and everything works fine, but when I use wicd, it doesn't work at all. If I enter my key using iwconfig then click connect in wicd, it connects and everything works. I want to use wicd (I tried networkmanager, but it just never worked for me either, probably the same problem as wicd). I don't understand why the password isn't handled correctly in wicd (or networkmanager). Does anyone have any idea at all why it is like this?

Last edited by Riser Glen (2007-08-16 17:56:05)

low · 2007-08-15 01:51:51

from this http://xx.joeuser.com/index.asp?AID=156640 it says you may need to add quotes around you key in wicd

Riser Glen · 2007-08-15 02:38:13

low wrote:

from this http://xx.joeuser.com/index.asp?AID=156640 it says you may need to add quotes around you key in wicd

Already tried that. It didn't help.

Riser Glen · 2007-08-16 17:52:15

Gave up on networkmanager & wicd. I've never had so much trouble with networkmanager before. While I do prefer something along the lines of knetworkmanager or wicd, I ended up using autowifi & wpa_supplicant. Seems to be fine now.

Last edited by Riser Glen (2007-08-16 18:15:07)

schivmeister · 2007-08-17 07:05:51

ndiswrapper? ive noticed something. a while ago i was using the stock kernel driver for my bcm card (bcm43xx), both wicd and knetworkmanager worked fine, though the new app wicd connects more efficiently on a regular basis (networkmanager is very fluctuating) , no difference in link quality or whatsoever.

i wanted to try ndiswrapper im now on it. knet detects the networks but won't connect, gets stuck. wicd won't even detect. however, like u, manual setup works.

back to kernel driver i guess

Riser Glen · 2007-08-17 13:54:37

I tried both ndiswrapper and prism54 driver, had the same problem in knet & wicd with both. The last time networkmanager connected every time I wanted it to was last year when I was using FC5.

The thing I don't understand is this: the networkmanager project has been going on since sometime in 2004, why do so many people still have trouble with it? Surely by now it should work for everyone.

thayer · 2007-08-17 16:51:25

Or, as in my case, it's even more surprising that Networkmanager used to work fine with the Intel 3945 cards, but has since regressed during the past 3 months to the point that it can't even connect to WPA-TKIP networks.

Last edited by thayer.w (2007-08-17 16:52:05)

schivmeister · 2007-08-18 06:53:53

networkmanager has been around for quite a while, yes. but wireless only got very high priority recently. it looks like you have to find the packages that work for you, as it seems no one application works for every card - everyone. In this case, autowifi & wpa_s*

on another thought, isn't it much less of code and hassle to start a script for the manual setup? maybe iwlist scan at the top of the list then a _if then else_, or _choice_. Or just issue them immediately without any further intervention. i guess it is, but something gui is definitely intuitive.

iphitus · 2007-08-18 07:17:15

*cough* netcfg2 http://bbs.archlinux.org/viewtopic.php?id=36384

I'll add that also, many people write off various wireless methods, but sometimes it's their own error in configuration that prevents it from working. So it isn't really right to say that it's "pot luck", though some do have their known issues.

As for networkmanager, i've had issues with it too. I've filed bugs, but their developers have practically ignored the bug tracker. So... no wonder it doesnt work.

James

Last edited by iphitus (2007-08-18 07:18:20)

Riser Glen · 2007-08-18 13:20:00

The thing is, networkmanager used to work fine with my card, but NM seems to be in "one step forward, two steps back" development mode. My bug reports have also been ignored.

iphitus, you should take something for that cough netcfg2 looks good, I'll check it out.

schivmeister · 2007-08-19 10:06:07

true that iphitus, it is almost always a user-related fault if it's not hardware issue. good work on the scripts!

Riser Glen · 2007-08-19 14:58:53

All I know is that it wasn't an error in my configuration.

Last edited by Riser Glen (2007-08-19 15:36:40)

Arch Linux

#1 2007-08-14 02:54:50

(Solved-sort of)Manual wifi config works, but wicd bites it

#2 2007-08-15 01:51:51

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#3 2007-08-15 02:38:13

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#4 2007-08-16 17:52:15

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#5 2007-08-17 07:05:51

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#6 2007-08-17 13:54:37

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#7 2007-08-17 16:51:25

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#8 2007-08-18 06:53:53

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#9 2007-08-18 07:17:15

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#10 2007-08-18 13:20:00

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#11 2007-08-19 10:06:07

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

#12 2007-08-19 14:58:53

Re: (Solved-sort of)Manual wifi config works, but wicd bites it

Board footer