[Resolved] networking problem after kernel 3.0 upgrade

greyhat.goon · 2011-08-21 23:17:34

my desktop has a wireless card using the ath9k driver.....normally I use wicd to connect. everything
has been working fine for the past year or so. everything got messed up
when i upgraded to kernel 3.0. i do have testing repo enabled.

the output of dmesg and daemons.log are below.
in dmesg, there's a statement about deauthenticating wlan0. i googled this and about the only thing i could find is someone saying
it's a kernel problem.

i have tried connecting manually using iwconfig etc.......still doesn't work.
when trying to connect with wicd, it seems to pull up the access point, authenticate the password, and get an ip address just fine.
wicd even says "connected" for a split second at the end of the process, but then says "not connected".

any help would be greatly appreciated.

tail of daemons.log

Aug 21 08:41:41 localhost dhcpcd[9668]: dhcpcd not running
Aug 21 08:41:41 localhost dhcpcd[9712]: dhcpcd not running
Aug 21 08:42:00 localhost dhcpcd[9907]: version 5.2.12 starting
Aug 21 08:42:00 localhost dhcpcd[9907]: wlan0: waiting for carrier
Aug 21 08:42:30 localhost dhcpcd[9907]: timed out
Aug 21 08:42:52 localhost dhcpcd[10351]: dhcpcd not running
Aug 21 08:42:52 localhost dhcpcd[10393]: dhcpcd not running
Aug 21 08:42:52 localhost dhcpcd[10448]: dhcpcd not running
Aug 21 08:42:55 localhost dhcpcd[10497]: version 5.2.12 starting
Aug 21 08:42:55 localhost dhcpcd[10497]: wlan0: broadcasting for a lease
Aug 21 08:42:55 localhost dhcpcd[10497]: wlan0: offered 10.0.0.133 from 10.0.0.1
Aug 21 08:42:55 localhost dhcpcd[10497]: wlan0: acknowledged 10.0.0.133 from 10.0.0.1
Aug 21 08:42:55 localhost dhcpcd[10497]: wlan0: checking for 10.0.0.133
Aug 21 08:43:00 localhost dhcpcd[10497]: wlan0: leased 10.0.0.133 for 86400 seconds
Aug 21 08:43:00 localhost dhcpcd[10497]: forked to background, child pid 10531
Aug 21 08:43:00 localhost dhcpcd[10559]: sending signal 1 to pid 10531
Aug 21 08:43:00 localhost dhcpcd[10559]: waiting for pid 10531 to exit
Aug 21 08:43:00 localhost dhcpcd[10531]: received SIGHUP, releasing
Aug 21 08:43:00 localhost dhcpcd[10531]: wlan0: releasing lease of 10.0.0.133
Aug 21 08:43:00 localhost dhcpcd[10531]: wlan0: send_packet: Operation not permitted
Aug 21 08:43:00 localhost dhcpcd[10531]: wlan0: removing interface
Aug 21 08:43:01 localhost dhcpcd[10608]: dhcpcd not running
Aug 21 08:44:25 localhost dhcpcd[11294]: dhcpcd not running
Aug 21 08:44:25 localhost dhcpcd[11336]: dhcpcd not running
Aug 21 08:44:25 localhost dhcpcd[11392]: dhcpcd not running
Aug 21 08:44:28 localhost dhcpcd[11441]: version 5.2.12 starting
Aug 21 08:44:28 localhost dhcpcd[11441]: wlan0: broadcasting for a lease
Aug 21 08:44:58 localhost dhcpcd[11441]: timed out
Aug 21 08:45:01 localhost dhcpcd[11547]: dhcpcd not running
Aug 21 08:45:02 localhost dhcpcd[11591]: dhcpcd not running

dmesg output

[16767.587670] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[16769.846383] wlan0: authenticate with 00:24:b2:8a:a4:49 (try 1)
[16769.849844] wlan0: authenticated
[16769.849865] wlan0: associate with 00:24:b2:8a:a4:49 (try 1)
[16769.853926] wlan0: RX AssocResp from 00:24:b2:8a:a4:49 (capab=0x411 status=0 aid=2)
[16769.853928] wlan0: associated
[16769.856346] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[16776.011772] Unknown OutputIN= OUT=wlan0 SRC=10.0.0.133 DST=10.0.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=68 DPT=67 LEN=308 
[16776.175532] wlan0: deauthenticating from 00:24:b2:8a:a4:49 by local choice (reason=3)
[16776.276876] cfg80211: Calling CRDA to update world regulatory domain
[16776.344628] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[16776.450141] r8169 0000:02:00.0: eth0: link down
[16776.450640] ADDRCONF(NETDEV_UP): eth0: link is not ready
[16860.033056] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[16860.947755] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[16861.052689] r8169 0000:02:00.0: eth0: link down
[16861.053317] ADDRCONF(NETDEV_UP): eth0: link is not ready
[16861.136767] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[16863.396373] wlan0: authenticate with 00:24:b2:8a:a4:49 (try 1)
[16863.399705] wlan0: authenticated
[16863.399725] wlan0: associate with 00:24:b2:8a:a4:49 (try 1)
[16863.407726] wlan0: RX AssocResp from 00:24:b2:8a:a4:49 (capab=0x411 status=0 aid=2)
[16863.407728] wlan0: associated
[16863.410171] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[16873.801694] wlan0: no IPv6 routers present
[16897.031964] wlan0: deauthenticating from 00:24:b2:8a:a4:49 by local choice (reason=3)
[16897.193561] cfg80211: Calling CRDA to update world regulatory domain
[16897.261210] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[16897.369506] r8169 0000:02:00.0: eth0: link down
[16897.370156] ADDRCONF(NETDEV_UP): eth0: link is not ready

Last edited by greyhat.goon (2011-08-29 00:58:13)

swanson · 2011-08-22 04:46:38

"dhcpcd not running" doesn't look good. But is it in your rc.conf? I had problems with dhcpd on my ath5k and installed and used dhclient instead, with good results.

greyhat.goon · 2011-08-23 04:30:43

I think WICD starts dhcpcd on demand.......you can see in the log files that dhcpcd eventually gets started. At any rate I have tried dhcpcd wlan0 manually with no luck. If I every find my thumb drive, i'll install dhclient.....otherwise I have to unplug my desktop and move it close enough to the router for a wired connection.

cesura · 2011-08-23 04:36:52

What type of encryption format is your router set to use, WEP or WPA?

EDIT: Sorry, disregard that. I totally forgot that the problem occurred due to a kernel upgrade.

Last edited by cesura (2011-08-23 05:03:34)

greyhat.goon · 2011-08-23 05:03:05

WPA2........but I also tried disabling encryption and connecting....no luck.

Found my thumb drive........downloaded and installed dhclient......didn't work either. seems like an ip address of 10.0.0.133 is being acquired briefly,
but then there's a "send_packet: operation not permitted" and "wlan0: carrier lost" message.

$ sudo tail -50 /var/log/daemon.log
Aug 22 14:45:25 localhost dhclient: Sending on   LPF/eth0/00:24:1d:15:50:9b
Aug 22 14:45:25 localhost dhclient: Sending on   Socket/fallback
Aug 22 14:45:25 localhost dhclient: Internet Systems Consortium DHCP Client 4.2.1-P1
Aug 22 14:45:25 localhost dhclient: Copyright 2004-2011 Internet Systems Consortium.
Aug 22 14:45:25 localhost dhclient: All rights reserved.
Aug 22 14:45:25 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Aug 22 14:45:25 localhost dhclient: 
Aug 22 14:45:25 localhost dhclient: Listening on LPF/wlan0/1c:af:f7:f3:45:db
Aug 22 14:45:25 localhost dhclient: Sending on   LPF/wlan0/1c:af:f7:f3:45:db
Aug 22 14:45:25 localhost dhclient: Sending on   Socket/fallback
Aug 22 14:45:25 localhost dhclient: DHCPRELEASE on wlan0 to 10.0.0.1 port 67
Aug 22 14:45:25 localhost dhclient: send_packet: Network is unreachable
Aug 22 14:45:25 localhost dhclient: send_packet: please consult README file regarding broadcast address.
Aug 22 14:45:28 localhost dhcpcd[2663]: wlan0: carrier acquired
Aug 22 14:45:28 localhost dhcpcd[2663]: wlan0: rebinding lease of 10.0.0.133
Aug 22 14:45:28 localhost dhcpcd[2663]: wlan0: acknowledged 10.0.0.133 from 10.0.0.1
Aug 22 14:45:28 localhost dhcpcd[2663]: wlan0: checking for 10.0.0.133
Aug 22 14:45:28 localhost dhclient: Internet Systems Consortium DHCP Client 4.2.1-P1
Aug 22 14:45:28 localhost dhclient: Copyright 2004-2011 Internet Systems Consortium.
Aug 22 14:45:28 localhost dhclient: All rights reserved.
Aug 22 14:45:28 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Aug 22 14:45:28 localhost dhclient: 
Aug 22 14:45:29 localhost dhclient: Listening on LPF/wlan0/1c:af:f7:f3:45:db
Aug 22 14:45:29 localhost dhclient: Sending on   LPF/wlan0/1c:af:f7:f3:45:db
Aug 22 14:45:29 localhost dhclient: Sending on   Socket/fallback
Aug 22 14:45:33 localhost dhcpcd[2663]: wlan0: leased 10.0.0.133 for 86400 seconds
Aug 22 14:45:33 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Aug 22 14:45:33 localhost dhclient: DHCPOFFER from 10.0.0.1
Aug 22 14:45:33 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Aug 22 14:45:33 localhost dhclient: DHCPACK from 10.0.0.1
Aug 22 14:45:33 localhost dhclient: bound to 10.0.0.133 -- renewal in 36498 seconds.
Aug 22 14:45:34 localhost dhclient: Internet Systems Consortium DHCP Client 4.2.1-P1
Aug 22 14:45:34 localhost dhclient: Copyright 2004-2011 Internet Systems Consortium.
Aug 22 14:45:34 localhost dhclient: All rights reserved.
Aug 22 14:45:34 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Aug 22 14:45:34 localhost dhclient: 
Aug 22 14:45:34 localhost dhclient: Listening on LPF/wlan0/1c:af:f7:f3:45:db
Aug 22 14:45:34 localhost dhclient: Sending on   LPF/wlan0/1c:af:f7:f3:45:db
Aug 22 14:45:34 localhost dhclient: Sending on   Socket/fallback
Aug 22 14:45:34 localhost dhclient: DHCPRELEASE on wlan0 to 10.0.0.1 port 67
Aug 22 14:45:34 localhost dhclient: send_packet: Operation not permitted
Aug 22 14:45:34 localhost dhcpcd[2663]: wlan0: carrier lost
Aug 22 14:45:34 localhost dhclient: Internet Systems Consortium DHCP Client 4.2.1-P1
Aug 22 14:45:34 localhost dhclient: Copyright 2004-2011 Internet Systems Consortium.
Aug 22 14:45:34 localhost dhclient: All rights reserved.
Aug 22 14:45:34 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Aug 22 14:45:34 localhost dhclient: 
Aug 22 14:45:34 localhost dhclient: Listening on LPF/eth0/00:24:1d:15:50:9b
Aug 22 14:45:34 localhost dhclient: Sending on   LPF/eth0/00:24:1d:15:50:9b
Aug 22 14:45:34 localhost dhclient: Sending on   Socket/fallback

cesura · 2011-08-23 05:09:14

Hmm, that is quite strange. I'll search around for you and report anything interesting.

In the meantime, have you tried using the madwifi driver?

greyhat.goon · 2011-08-29 00:57:41

Well, seems to to work after rebooting with wicd using dhclient instead of dhcpcd. Without rebooting, got the same error messages with dhclient. However, worked after rebooting.

Arch Linux

#1 2011-08-21 23:17:34

[Resolved] networking problem after kernel 3.0 upgrade

#2 2011-08-22 04:46:38

Re: [Resolved] networking problem after kernel 3.0 upgrade

#3 2011-08-23 04:30:43

Re: [Resolved] networking problem after kernel 3.0 upgrade

#4 2011-08-23 04:36:52

Re: [Resolved] networking problem after kernel 3.0 upgrade

#5 2011-08-23 05:03:05

Re: [Resolved] networking problem after kernel 3.0 upgrade

#6 2011-08-23 05:09:14

Re: [Resolved] networking problem after kernel 3.0 upgrade

#7 2011-08-29 00:57:41

Re: [Resolved] networking problem after kernel 3.0 upgrade

Board footer