LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-20-2009, 08:14 PM   #1
JazzItSelf
Member
 
Registered: Oct 2003
Location: Boston
Distribution: Slackware64-current
Posts: 42

Rep: Reputation: 18
problem using wicd to connect to a hidden wep network


Greets all-

I'm running slackware-current and having difficulty using wicd to connect to a hidden wireless network that uses WEP.

Going through wicd's network menu to "find a hidden network" simply results in finding no networks at all. I've tried connecting to the appropriate "hidden" entry in the list of networks, but this also fails. It sits around for a while trying to validate authentication and then fails by not being able to acquire an IP address. I don't think it's actually connected to the network when it starts trying to acquire one.

I've also tried manually setting up a configuration section for it in the wireless-settings.conf with no success at connecting to the network.

Okay, big deal, I can use iwconfig to connect to this particular network when I need to, right? Well, it seems that wicd doesn't like to give up control of the interface. as root, setting the essid simply has no effect. subsequent invocations of iwconfig show an empty string as the essid. presumably it doesn't pick up the wep key either, but that's not displayed for me to check.

I have discovered that if wicd initiates a connection and the attempt is canceled before it connects, it briefly gives up control of the interface. During these moments I can set the essid and wep key using iwconfig. Then I can invoke dhcpcd to get an IP address. At this point wicd will show the connected status of the network.

Anyone have any ideas?

Thanks,
--Chad
 
Old 08-20-2009, 08:51 PM   #2
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,151

Rep: Reputation: 331Reputation: 331Reputation: 331Reputation: 331
Which version of wicd are you running? (I think 1.6.0 is the latest release, and several improvements over the 1.5 versions were made.)
 
Old 08-20-2009, 09:05 PM   #3
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 227Reputation: 227Reputation: 227
From the August 14 -current changelog

Code:
extra/wicd/wicd-1.6.2-i486-2.txz: Rebuilt.
Fixed a problem with hidden networks. Thanks to Robby Workman.
 
Old 08-21-2009, 09:18 PM   #4
JazzItSelf
Member
 
Registered: Oct 2003
Location: Boston
Distribution: Slackware64-current
Posts: 42

Original Poster
Rep: Reputation: 18
Just now tested with 1.6.2 and it seems to have similar problems. I'll have to delve a little deeper before saying that the problem is either the same or different.

I think I forgot to mention that after I attempt to find a hidden network, wicd seems to get stuck with something, and not only do I not find the network, but I can no longer find *any* networks (save the wired one, which is not connected).

I don't see any useful information in the /var/log/wicd/wicd.log. There are entries that say "Setting hidden essidMYESSID". Presumably, the missing space is simply a typo in the code. I'm not sure what I can do to debug this. Is there a way to get more debugging output out of the daemon?
 
Old 08-22-2009, 03:46 PM   #5
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,151

Rep: Reputation: 331Reputation: 331Reputation: 331Reputation: 331
Quote:
Originally Posted by JazzItSelf View Post
[. . .]Is there a way to get more debugging output out of the daemon?
In the AP selection pop-up, click on the "Settings" button and check the "Debugging" check-box.

Caution: The debugging output will included your encryption keys, AP name, etc., in plain text. Don't post that output here without redacting any confidential information unless you don't care to keep it confidential. (The likelihood of a LQ reader finding your post and also being close enough to your AP to use that information seems, to me, to be quite low. But there's no reason to take chances if you don't need to do so. )
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Wicd on Fedora 10 will not connect to WPA/WPA2 network after install Mikazo Linux - Wireless Networking 2 04-11-2009 12:38 PM
Cannot connect to wireless network with wicd on Zenwalk Kenny_C Linux - Wireless Networking 1 04-07-2009 02:11 PM
Hidden WEP Network with more options. begrady Linux - Wireless Networking 3 12-13-2007 10:22 AM
problem getting wep to connect to network bhert Linux - Wireless Networking 5 11-21-2007 09:41 PM
H:Problem in IPW2200 connect to WEP network Fortuner Slackware 5 09-23-2007 08:53 AM


All times are GMT -5. The time now is 09:47 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration