You are not logged in.

Pages: 1

#1 2011-04-19 07:09:53

whoops
Member
Registered: 2009-03-19
Posts: 891

wpa keeps dis-/reconnecting

Hello!

My wpa keeps disconnecting and reconnecting. Sometimes it works fine, but once it starts, it's continuing like this until I mess with it (killing processes, restarting, rebooting client & router) - the it seems to start working normally at a random point. Can't figure out what actually fixed it, doesn't often work right away, but it does continue for hours if I don't do anything. wpa_supplicant just says:

CTRL-EVENT-DISCONNECTED bssid=48:5b:39:e8:54:98 reason=0

client says:

Apr 19 08:59:30 localhost dhcpcd[18666]: wlan0: acknowledged 192.168.165.201 from 192.168.11.11
Apr 19 08:59:30 localhost dhcpcd[18666]: wlan0: checking for 192.168.165.201
Apr 19 08:59:34 localhost dhcpcd[18666]: wlan0: leased 192.168.165.201 for 600000 seconds
Apr 19 09:00:21 localhost dhcpcd[18666]: wlan0: carrier lost
Apr 19 09:00:21 localhost kernel: cfg80211: Calling CRDA to update world regulatory domain
Apr 19 09:00:22 localhost dhcpcd[18666]: wlan0: carrier acquired
Apr 19 09:00:22 localhost dhcpcd[18666]: wlan0: rebinding lease of 192.168.165.201
Apr 19 09:00:26 localhost dhcpcd[18666]: wlan0: acknowledged 192.168.165.201 from 192.168.11.11
Apr 19 09:00:26 localhost dhcpcd[18666]: wlan0: checking for 192.168.165.201
Apr 19 09:00:30 localhost dhcpcd[18666]: wlan0: leased 192.168.165.201 for 600000 seconds
Apr 19 09:01:21 localhost dhcpcd[18666]: wlan0: carrier lost
Apr 19 09:01:21 localhost kernel: cfg80211: Calling CRDA to update world regulatory domain
Apr 19 09:01:22 localhost dhcpcd[18666]: wlan0: carrier acquired
Apr 19 09:01:22 localhost dhcpcd[18666]: wlan0: rebinding lease of 192.168.165.201
Apr 19 09:01:26 localhost dhcpcd[18940]: sending signal 1 to pid 18666
Apr 19 09:01:26 localhost dhcpcd[18666]: received SIGHUP, releasing
Apr 19 09:01:26 localhost dhcpcd[18666]: wlan0: removing interface
Apr 19 09:01:26 localhost dhcpcd[18940]: waiting for pid 18666 to exit
Apr 19 09:01:26 localhost kernel: cfg80211: Calling CRDA to update world regulatory domain
Apr 19 09:01:26 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 19 09:01:26 localhost kernel: r8169 0000:02:00.0: eth0: link down
Apr 19 09:01:26 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 19 09:01:31 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 19 09:01:31 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 19 09:01:32 localhost kernel: r8169 0000:02:00.0: eth0: link down
Apr 19 09:01:32 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 19 09:01:32 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 19 09:01:34 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 19 09:01:35 localhost dhcpcd[19004]: version 5.2.12 starting
Apr 19 09:01:35 localhost dhcpcd[19004]: wlan0: broadcasting for a lease
Apr 19 09:01:35 localhost dhcpcd[19004]: wlan0: offered 192.168.165.201 from 192.168.11.11
Apr 19 09:01:35 localhost dhcpcd[19004]: wlan0: acknowledged 192.168.165.201 from 192.168.11.11
Apr 19 09:01:35 localhost dhcpcd[19004]: wlan0: checking for 192.168.165.201
Apr 19 09:01:41 localhost dhcpcd[19004]: wlan0: leased 192.168.165.201 for 600000 seconds
Apr 19 09:01:41 localhost dhcpcd[19004]: forked to background, child pid 19031
Apr 19 09:02:21 localhost dhcpcd[19031]: wlan0: carrier lost
Apr 19 09:02:21 localhost kernel: cfg80211: Calling CRDA to update world regulatory domain
Apr 19 09:02:22 localhost dhcpcd[19031]: wlan0: carrier acquired
Apr 19 09:02:22 localhost dhcpcd[19031]: wlan0: rebinding lease of 192.168.165.201
Apr 19 09:02:23 localhost dhcpcd[19080]: sending signal 1 to pid 19031
Apr 19 09:02:23 localhost dhcpcd[19031]: received SIGHUP, releasing
Apr 19 09:02:23 localhost dhcpcd[19080]: waiting for pid 19031 to exit
Apr 19 09:02:23 localhost dhcpcd[19031]: wlan0: removing interface
Apr 19 09:02:23 localhost kernel: cfg80211: Calling CRDA to update world regulatory domain
Apr 19 09:02:23 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 19 09:02:23 localhost kernel: r8169 0000:02:00.0: eth0: link down
Apr 19 09:02:23 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 19 09:02:28 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 19 09:02:29 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 19 09:02:29 localhost kernel: r8169 0000:02:00.0: eth0: link down
Apr 19 09:02:29 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 19 09:02:29 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 19 09:02:31 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 19 09:02:32 localhost dhcpcd[19148]: version 5.2.12 starting
Apr 19 09:02:32 localhost dhcpcd[19148]: wlan0: broadcasting for a lease
Apr 19 09:02:32 localhost dhcpcd[19148]: wlan0: offered 192.168.165.201 from 192.168.11.11
Apr 19 09:02:32 localhost dhcpcd[19148]: wlan0: acknowledged 192.168.165.201 from 192.168.11.11
Apr 19 09:02:32 localhost dhcpcd[19148]: wlan0: checking for 192.168.165.201
Apr 19 09:02:37 localhost dhcpcd[19148]: wlan0: leased 192.168.165.201 for 600000 seconds
Apr 19 09:02:38 localhost dhcpcd[19148]: forked to background, child pid 19171

router says:

Apr 19 08:51:33 router daemon.info dnsmasq-dhcp[1384]: DHCPDISCOVER(br0) 74:ea:3a:b5:28:91 
Apr 19 08:51:33 router daemon.info dnsmasq-dhcp[1384]: DHCPOFFER(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 08:51:33 router daemon.info dnsmasq-dhcp[1384]: DHCPREQUEST(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 08:51:33 router daemon.info dnsmasq-dhcp[1384]: DHCPACK(br0) 192.168.165.201 74:ea:3a:b5:28:91 xarch
Apr 19 08:52:35 router daemon.info dnsmasq-dhcp[1384]: DHCPDISCOVER(br0) 74:ea:3a:b5:28:91 
Apr 19 08:52:35 router daemon.info dnsmasq-dhcp[1384]: DHCPOFFER(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 08:52:35 router daemon.info dnsmasq-dhcp[1384]: DHCPREQUEST(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 08:52:35 router daemon.info dnsmasq-dhcp[1384]: DHCPACK(br0) 192.168.165.201 74:ea:3a:b5:28:91 xarch
Apr 19 08:54:46 router daemon.info dnsmasq-dhcp[1384]: DHCPREQUEST(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 08:54:46 router daemon.info dnsmasq-dhcp[1384]: DHCPACK(br0) 192.168.165.201 74:ea:3a:b5:28:91 xarch
Apr 19 08:56:49 router daemon.info dnsmasq-dhcp[1384]: DHCPREQUEST(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 08:56:49 router daemon.info dnsmasq-dhcp[1384]: DHCPACK(br0) 192.168.165.201 74:ea:3a:b5:28:91 xarch
Apr 19 08:57:32 router daemon.info dnsmasq-dhcp[1384]: DHCPREQUEST(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 08:57:32 router daemon.info dnsmasq-dhcp[1384]: DHCPACK(br0) 192.168.165.201 74:ea:3a:b5:28:91 xarch
Apr 19 08:59:30 router daemon.info dnsmasq-dhcp[1384]: DHCPREQUEST(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 08:59:30 router daemon.info dnsmasq-dhcp[1384]: DHCPACK(br0) 192.168.165.201 74:ea:3a:b5:28:91 xarch
Apr 19 09:00:26 router daemon.info dnsmasq-dhcp[1384]: DHCPREQUEST(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 09:00:26 router daemon.info dnsmasq-dhcp[1384]: DHCPACK(br0) 192.168.165.201 74:ea:3a:b5:28:91 xarch
Apr 19 09:01:35 router daemon.info dnsmasq-dhcp[1384]: DHCPDISCOVER(br0) 74:ea:3a:b5:28:91 
Apr 19 09:01:35 router daemon.info dnsmasq-dhcp[1384]: DHCPOFFER(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 09:01:35 router daemon.info dnsmasq-dhcp[1384]: DHCPREQUEST(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 09:01:35 router daemon.info dnsmasq-dhcp[1384]: DHCPACK(br0) 192.168.165.201 74:ea:3a:b5:28:91 xarch
Apr 19 09:02:32 router daemon.info dnsmasq-dhcp[1384]: DHCPDISCOVER(br0) 74:ea:3a:b5:28:91 
Apr 19 09:02:32 router daemon.info dnsmasq-dhcp[1384]: DHCPOFFER(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 09:02:32 router daemon.info dnsmasq-dhcp[1384]: DHCPREQUEST(br0) 192.168.165.201 74:ea:3a:b5:28:91 
Apr 19 09:02:32 router daemon.info dnsmasq-dhcp[1384]: DHCPACK(br0) 192.168.165.201 74:ea:3a:b5:28:91 xarch

So... This happens every 1-2 minutes. First I thought, 2 instances of wpa_supplicant were running concurrently, because after killing wpa_supplicant / dhcpcd it sometimes worked. Or after switching from wicd to connectiong manually. But that seems to be random... there is a second dhcpcd in ps aux at the moment, but it says "[dhcpcd] <defunct>" / can't kill it and the PID of that one never appears in the logs, so I guess its not really doing anything? If that's why this happens, I don't know how to stop it - it comes back after rebooting... that might just be me trying to fix / kill things though, not a part of the actual problem...?

Last edited by whoops (2011-04-19 07:17:50)

Offline

#2 2011-04-19 11:28:55

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: wpa keeps dis-/reconnecting

"Carrier lost" usually means there's no physical connection. Is your signal decent?

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#3 2011-04-19 13:24:22

whoops
Member
Registered: 2009-03-19
Posts: 891

Re: wpa keeps dis-/reconnecting

Looks fine to me... not great, but:
Signal level client is getting: -59 dBm
Signal level router is getting: -49 dBm
2 machines in the Network are worse and experience no problems. Anything else I should be looking at?

Offline

Pages: 1

Board footer

Powered by FluxBB