LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices

Reply
 
Search this Thread
Old 06-26-2010, 12:14 AM   #1
Poetics
Senior Member
 
Registered: Jun 2003
Location: California
Distribution: Slackware
Posts: 1,178

Rep: Reputation: 49
Unable to connect to WEP or Unsecured Wireless (WPA is fine)


I've just installed a new harddrive into my EeePC 1005HA netbook, and with it a fresh installation of Slackware 13.1. I am able to connect to my WPA-protected network just fine, and others as well, but I am unable to associate with either WEP or unsecured networks. After a number of searches, I've yet been unable to figure out the rationale behind this behavior.

Kernel: 2.6.33.4-smp
Wireless driver: ath9k

I've used both manual iwconfig attempts and wicd, to no avail. Wicd merely states that it cannot obtain an IP address, and the log is relatively unhelpful (detailing the same, that dhcpcd was unable to find a lease). If I attempt to connect manually, iwconfig never reports a successful association.

I appreciate any help that may be provided - it's been a while since I've had wireless difficulties, and this one has me scratching my head.
 
Old 06-27-2010, 09:10 AM   #2
irmin
Member
 
Registered: Jan 2010
Location: the universe
Distribution: Slackware (modified), Slackware64 (modified), openSuSE (modified)
Posts: 342

Rep: Reputation: 62
Quote:
Originally Posted by Poetics View Post
I've just installed a new harddrive into my EeePC 1005HA netbook, and with it a fresh installation of Slackware 13.1. I am able to connect to my WPA-protected network just fine, and others as well, but I am unable to associate with either WEP or unsecured networks. After a number of searches, I've yet been unable to figure out the rationale behind this behavior.

Kernel: 2.6.33.4-smp
Wireless driver: ath9k

I've used both manual iwconfig attempts and wicd, to no avail. Wicd merely states that it cannot obtain an IP address, and the log is relatively unhelpful (detailing the same, that dhcpcd was unable to find a lease). If I attempt to connect manually, iwconfig never reports a successful association.
Hi, perhaps there is no DHCP available on the network? When you want to try manual connects, you will have to shutdown any network managing software (like network manager or wicd). Because they may reconfigure your network at any time. Then try "iwlist scan" to scan for networks and look if your target network is available (Post the output if you like). Then associate to the network using iwconfig. Check the output of dmesg and iwconfig to assure yourself, that the network is associated. If after some seconds the network is not associated and you are sure to be authorized to access the network (some networks have MAC filters ...) post the outputs of iwconfig and dmesg (if you want and they contain some useful messages). Next try to unload the ath9k driver and load it with "debug=-1" module option. And start again. There should be now more error messages in dmesg-output or /var/log/messages. Post them.

Btw: Sometimes it is needed to initiate network scans or to give the associate command again to speed up connecting ... (Works at least at my laptop ...)

If you see in iwconfig that your wireless interface is associated, issue a "dhclient wlan0" command to obtain an IP address.
 
Old 06-27-2010, 07:23 PM   #3
Poetics
Senior Member
 
Registered: Jun 2003
Location: California
Distribution: Slackware
Posts: 1,178

Original Poster
Rep: Reputation: 49
Thanks for the suggestions, irmin, but sadly even after killing wicd or any other type of autoconfiguration script, iwconfig never shows that I've associated, even after supplying essid, AP, and channel. iwlist does indeed detail that the network is available, and I've verified (via another computer) that DHCP is working on said network(s).
 
Old 06-28-2010, 05:43 AM   #4
irmin
Member
 
Registered: Jan 2010
Location: the universe
Distribution: Slackware (modified), Slackware64 (modified), openSuSE (modified)
Posts: 342

Rep: Reputation: 62
Are there any messages, when you load the driver ath9k with option "debug=-1"? You should be able to manually connect to unencrypted and WEP encrypted networks. I had a similar problem on my Asus Eeepc 900a (ath5k driver). I changed to madwifi driver and the problems are gone. Perhaps you want to try this too? But I cannot say for sure that your device is supported by this driver.

http://madwifi.org/
 
Old 07-05-2010, 03:15 PM   #5
Poetics
Senior Member
 
Registered: Jun 2003
Location: California
Distribution: Slackware
Posts: 1,178

Original Poster
Rep: Reputation: 49
It turns out that my system has problems connecting to Ad-Hoc networks, it seems. Over the weekend I took it elsewhere to an unsecured Managed network and it hopped on just fine.

I also didn't see an option in modprobe to run 'debug=1', and so my /var/log/messages was quite empty in regard to loading errors.

It looks like I can now associate just fine (I unfortunately forgot what setting I had changed, or methodology), but I cannot get a DHCP address, or connect to any other device on the network. Any thoughts?

Last edited by Poetics; 07-05-2010 at 03:21 PM.
 
Old 07-05-2010, 04:04 PM   #6
irmin
Member
 
Registered: Jan 2010
Location: the universe
Distribution: Slackware (modified), Slackware64 (modified), openSuSE (modified)
Posts: 342

Rep: Reputation: 62
Quote:
Originally Posted by Poetics View Post
I also didn't see an option in modprobe to run 'debug=1', and so my /var/log/messages was quite empty in regard to loading errors.
You will have to do
Code:
rmmod ath9k
modprobe ath9k debug=-1
to enable verbose debug messages.

Quote:
It looks like I can now associate just fine (I unfortunately forgot what setting I had changed, or methodology), but I cannot get a DHCP address, or connect to any other device on the network. Any thoughts?
If you assign a static IP address to your laptop, does it work then? Maybe the DHCP server is configured not to give you an IP address or there is some MAC filter active.
 
Old 07-06-2010, 03:31 AM   #7
Poetics
Senior Member
 
Registered: Jun 2003
Location: California
Distribution: Slackware
Posts: 1,178

Original Poster
Rep: Reputation: 49
Well it looks like I may just not be able to connect to ad-hoc networks with this driver -- other devices work just fine with the attempted network, and the system seems to be alright with regular (managed) networks.

Really frustrating though, when I was hoping to have this netbook be a "connect anywhere" device. I wonder if there are other drivers/firmwares in the pipe, perhaps in a future kernel.

btw, here's the results of the debug=1; no anomalous entries found
Code:
root@slacktop:~# grep ath9k /var/log/messages
Jul  6 00:39:13 slacktop kernel: ath9k 0000:02:00.0: PCI INT A disabled
Jul  6 00:39:13 slacktop kernel: ath9k: Driver unloaded
Jul  6 00:39:47 slacktop kernel: ath9k 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Jul  6 00:39:47 slacktop kernel: Registered led device: ath9k-phy1::radio
Jul  6 00:39:47 slacktop kernel: Registered led device: ath9k-phy1::assoc
Jul  6 00:39:47 slacktop kernel: Registered led device: ath9k-phy1::tx
Jul  6 00:39:47 slacktop kernel: Registered led device: ath9k-phy1::rx
 
Old 07-06-2010, 04:15 AM   #8
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
How do you find out that "just not be able to connect to ad-hoc networks with this driver"?
Do you have access to AP, can you simply turn off (temporary) encryption?
Check on you comp. that wpa_supplicant is not loaded, any network managers is not loaded, and ONLY then do:
1. up your wireless interface.
2. scan air, check that driver "sees" your AP
3. down wireless interface.
4. Bring it up with additional parameters "essid" (man iwconfig may help)
 
  


Reply

Tags
adhoc, ath9k, wep, wireless


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
Network manager unable to connect to unsecured wireless - WPA networks fine :S phyre-x Ubuntu 8 05-16-2011 10:11 AM
NM & WICD cannot connect to WEP/WPA 2 wireless elusive_night Linux - Newbie 3 09-28-2009 06:04 PM
Why can I see wireless networks but never connect, WPA/WEP or open? Dan.b Linux - Newbie 3 09-03-2009 10:43 PM
WPA-PSK not working, but unsecured wireless OK Bleys Maynard Linux - Wireless Networking 9 06-11-2007 07:33 AM


All times are GMT -5. The time now is 06:19 PM.

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