You are not logged in.

#1 2013-07-24 02:42:48

psva00
Member
Registered: 2013-07-24
Posts: 2

Atheros AR9485 wireless not obtaining IP from WPA AP

Hello all, thanks for taking time to read.

I have a fairly new install of Arch, and I am having issues with my wireless connection that I cannot make sense of. I have tried a lot of different tools and possible fixes that I've found all over the internet to no avail.

I am able to scan and detect local networks.
I am able to associate, and authenticate but fails at the point of DHCP, this is the case with two separate WPA2 APs.
I have tried this with both dhclient and dhcpcd, I am currently using dhcpcd.
I have tried this with both wicd and netctl/wifi-menu, I am currently using wifi-menu.

Trying to start wpa_supplicant as a system service fails with odd results.
'systemctl enable wpa_supplicant@wlp3s0' creates a link using name 'wlan0.service'

journalctl -xn:

Jul 23 18:08:18 arch-laptop dhcpcd[2178]: wlp3s0: acknowledged 192.168.43.197 from 192.168.43.1
Jul 23 18:08:18 arch-laptop dhcpcd[2178]: wlp3s0: checking for 192.168.43.197
Jul 23 18:08:18 arch-laptop dhcpcd[2178]: timed out
Jul 23 18:08:19 arch-laptop network[2113]: DHCP IP lease attempt failed on interface 'wlp3s0'
Jul 23 18:08:19 arch-laptop network[2113]: Failed to bring the network up for profile 'wlp3s0-AndroidAP'
Jul 23 18:08:19 arch-laptop kernel: wlp3s0: deauthenticating from 02:1a:11:fb:aa:45 by local choice (reason=3)
Jul 23 18:08:19 arch-laptop systemd[1]: netctl@wlp3s0\x2dAndroidAP.service: main process exited, code=exited, status=1/FAILURE
Jul 23 18:08:19 arch-laptop systemd[1]: Failed to start Networking for netctl profile wlp3s0-AndroidAP.
-- Subject: Unit netctl@wlp3s0\x2dAndroidAP.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit netctl@wlp3s0\x2dAndroidAP.service has failed.
-- 
-- The result is failed.
Jul 23 18:08:19 arch-laptop systemd[1]: Unit netctl@wlp3s0\x2dAndroidAP.service entered failed state.
Jul 23 18:08:19 arch-laptop kernel: cfg80211: Calling CRDA to update world regulatory domain

Kinda stumped here, any help is appreciated!
Thanks,
Patrick

Offline

#2 2013-07-24 03:52:59

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,354

Re: Atheros AR9485 wireless not obtaining IP from WPA AP

I see you are using your Android as an access point.  You did not state what the other AP was.   

In order to  use an Android as an AP, you have to turn on NAT forwarding in the phone.  You also need to provide a DHCP server in the phone.  Are you using a Tethering App, or are you using the settings native to the Android OS.  Also, if you are in the USA, who is your carrier.  Verizon, for example, makes tethering difficult.  Is your phone rooted, and are you using a crippled version of Android (a la Verizon or ATT), or are you running something more reasonable, like Cyanogen?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2013-07-24 05:28:04

psva00
Member
Registered: 2013-07-24
Posts: 2

Re: Atheros AR9485 wireless not obtaining IP from WPA AP

The other AP is a Netgear WNDR3700.
Both APs work from other machines.
The android has been a functional AP for over a year, worked for this machine under Win8 and Win7, and works with this machine if WPA is turned off.

Just found a different error from the Netgear AP. Right after assoc and auth are successful:

...new config is 2412 MHz width 1 (2410/0 MHz)
AP xx:... changed bandwidth in a way we can't support - disconnect

googling...

Update: https://bugzilla.kernel.org/show_bug.cgi?id=58561

Looks like a kernel issue with 3.9.x still present in 3.10rc7

Exact same issue described here:

https://bbs.archlinux.org/viewtopic.php?pid=1275620

Solution is to revert to 3.8.x

Last edited by psva00 (2013-07-24 05:38:32)

Offline

Board footer

Powered by FluxBB