View previous topic :: View next topic |
Author |
Message |
numberlessusername n00b
Joined: 29 Dec 2011 Posts: 20
|
Posted: Mon Aug 12, 2013 9:22 pm Post subject: two gentoo boxes can no longer connect to wireless |
|
|
neither went through any updates; they just suddenly broke.
card info from lspci -k:
Network controller: Atheros Communications Inc. AR9462 Wireless Network Adapter (rev 01)
Subsystem: Bigfoot Networks, Inc. Device 2003
Kernel Driver in use: ath9k
the other computer has a different atheros card but also uses ath9k
using wicd-curses to try to connect to both my home network and my cell phone's mobile hotspot. both are WPA2
wpa_supplicant-0.7.3-r5 and wicd-1.7.2.4-r2 are installed.
If I can provide any additional information, let me know.
Thanks in advance! |
|
Back to top |
|
|
numberlessusername n00b
Joined: 29 Dec 2011 Posts: 20
|
Posted: Mon Aug 12, 2013 10:17 pm Post subject: |
|
|
connecting to the unsecured network at my high school works as well as it used to, leading me to believe it's an issue with wpa_supplicant. Any tips? |
|
Back to top |
|
|
TomWij Retired Dev
Joined: 04 Jul 2012 Posts: 1553
|
Posted: Mon Aug 12, 2013 10:24 pm Post subject: |
|
|
Please post debugging output from dmesg, ifconfig, iwconfig, iw, wpa_supplicant such we have more troubleshooting information; thank you in advance. |
|
Back to top |
|
|
numberlessusername n00b
Joined: 29 Dec 2011 Posts: 20
|
Posted: Tue Aug 13, 2013 3:07 am Post subject: |
|
|
dmesg snippet, lines 1004 - 1025 or so of this paste: http://bpaste.net/show/122413/
Code: | [ 482.238886] wlp3s0: authenticate with 00:1d:d6:2b:b7:00
[ 482.249457] wlp3s0: send auth to 00:1d:d6:2b:b7:00 (try 1/3)
[ 482.402504] wlp3s0: authenticated
[ 482.403446] wlp3s0: associate with 00:1d:d6:2b:b7:00 (try 1/3)
[ 482.426584] wlp3s0: RX AssocResp from 00:1d:d6:2b:b7:00 (capab=0xc11 status=0 aid=9)
[ 482.426626] wlp3s0: associated
[ 482.426633] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 502.923279] wlp3s0: deauthenticating from 00:1d:d6:2b:b7:00 by local choice (reason=3)
[ 502.945670] cfg80211: Calling CRDA for country: US
[ 502.997158] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 503.050399] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 504.061384] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 505.162767] wlp3s0: authenticate with 00:1d:d6:2b:b7:00
[ 505.173323] wlp3s0: send auth to 00:1d:d6:2b:b7:00 (try 1/3)
[ 505.175263] wlp3s0: authenticated
[ 505.175544] wlp3s0: associate with 00:1d:d6:2b:b7:00 (try 1/3)
[ 505.184691] wlp3s0: RX AssocResp from 00:1d:d6:2b:b7:00 (capab=0xc11 status=0 aid=9)
[ 505.184737] wlp3s0: associated
[ 505.184746] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 509.361059] wlp3s0: deauthenticating from 00:1d:d6:2b:b7:00 by local choice (reason=3)
[ 509.378798] cfg80211: Calling CRDA to update world regulatory domain
[ 509.428331] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready |
some googling led to this topic: https://forums.gentoo.org/viewtopic-t-935388-start-0.html
from this, I took away that I should make sure all network-related daemons are halted (dhcpcd, wicd, wpa_supplicant, etc) and start networkmanager. nmcli connected fine, so it looks I'll be switching. wext is deprecated anyway.
nmcli dev wifi connect <essid> password <password (in plaintext D> worked fine for me on both machines
https://bbs.archlinux.org/viewtopic.php?id=146052 This topic also suggests multiple things could be fighting for the wireless interface.
I'm sorry, my brain is fried and I can't put more words to describing my fix for googlers. |
|
Back to top |
|
|
666threesixes666 Veteran
Joined: 31 May 2011 Posts: 1248 Location: 42.68n 85.41w
|
Posted: Tue Aug 13, 2013 3:17 am Post subject: |
|
|
i ran wicd for like 3 weeks, and then it started acting buggy and updating it fixed the problem i was having. & did that like 2-3 times... i eventually switch to networkmanager. |
|
Back to top |
|
|
TomWij Retired Dev
Joined: 04 Jul 2012 Posts: 1553
|
Posted: Tue Aug 13, 2013 9:55 am Post subject: |
|
|
It appears you have multiple daemons trying to manage the network running (probably network scripts and wicd), that's what local reason 3 usually indicates. |
|
Back to top |
|
|
|