I have Dlink DWA-125 USB adapter (Driver rt2870usb) ...Wicd is able to detect all networks but is not able to connect.. I tried giving "dhcpcd wlan0" to associate with access point , but still no luck..
Initially I got - "connection failed: bad password"
I removed wicd and reinstalled wicd from install disc , now there is no error message but nothing happens! , It seems to goes thru judging from the messages in the window ,Connecting..., Obtaining IP Address, Connecting.., writing WPA configuration file and then it comes out ..
I also tried downloading Networkmanager and nm-applet, but I am not sure as to how to get the frontend working..After starting NM , I do not know what to do ...I searched the widgets also , but nm-applet is not there
How do I get over this problem?
Wicd - problem 13.37 64 bit
Re: Wicd - problem 13.37 64 bit
In that case it's always a good idea to try with an un-encrypted network first. Also non-ASCII characters in the password may be a source of problems.vikrang wrote:Initially I got - "connection failed: bad password"
Hey, we are not on W*nd*wsvikrang wrote:I removed wicd and reinstalled wicd from install disc
This won't help unless you have a faulty install.
Re: Wicd - problem 13.37 64 bit
A quick web search on 'wicd bad password' reveals there seems to be a bit of this about in various distros. I didn't see The One True Answer - does the output of dmesg after a failed attempt reveal anything useful?
If all else fails real men (and no doubt also real women) roll up their sleeves and read all about wpa_supplicant, and wpa_supplicant.conf. It's not that hard to get going, basically you have to edit wpa_supplicant.conf and supply the details of your network, then run wpa_supplicant at the cli. That should get you associated and authenticated, then you need to get an ip address. Looks like wpa_supplicant is supplied with Salix. If you can get the network going at this basic level as proof things are working, then maybe you can wrassle the gui apps till they say uncle thereafter.
As to nm-applet, how exactly that becomes available to the user is one of the great unanswered questions of the universe - grin. That's to say it seems to work with some desktop environments but be problematic in others. I think the applet has to be told to appear in a desktop panel for example so it is accessible to the end user, but you'd need to read the fine manual to work this out for your particular setup.
If all else fails real men (and no doubt also real women) roll up their sleeves and read all about wpa_supplicant, and wpa_supplicant.conf. It's not that hard to get going, basically you have to edit wpa_supplicant.conf and supply the details of your network, then run wpa_supplicant at the cli. That should get you associated and authenticated, then you need to get an ip address. Looks like wpa_supplicant is supplied with Salix. If you can get the network going at this basic level as proof things are working, then maybe you can wrassle the gui apps till they say uncle thereafter.
As to nm-applet, how exactly that becomes available to the user is one of the great unanswered questions of the universe - grin. That's to say it seems to work with some desktop environments but be problematic in others. I think the applet has to be told to appear in a desktop panel for example so it is accessible to the end user, but you'd need to read the fine manual to work this out for your particular setup.
Re: Wicd - problem 13.37 64 bit
wicd uses wpa_supplicant by default. The wpa_supplicant.conf is generated from templates in /etc/wicd/encryption/templates/ and the ready to use conf is stored in /var/lib/wicd/configurations/ with some hash filename.gnomic wrote:If all else fails real men (and no doubt also real women) roll up their sleeves and read all about wpa_supplicant, and wpa_supplicant.conf. It's not that hard to get going, basically you have to edit wpa_supplicant.conf and supply the details of your network, then run wpa_supplicant at the cli. That should get you associated and authenticated, then you need to get an ip address. Looks like wpa_supplicant is supplied with Salix. If you can get the network going at this basic level as proof things are working, then maybe you can wrassle the gui apps till they say uncle thereafter.
