[SOLVED] Connection lost shortly after boot

corp28 · 2013-08-23 04:43:00

After booting and logging in, I am connected to the network but soon lose connection (if I ping google as soon as I log in, the network becomes unreachable after a few counts). However, running,

dhcpcd -k

dhcpcd[710]: sending signal 1 to pid 197
dhcpcd[710]: waiting for pid 197 to exit

followed by,

dhcpcd

dhcpcd[743]: version 6.0.5 starting
dhcpcd[743]: enp9s0: waiting for carrier
dhcpcd[743]: wlp12s0: waiting for carrier
dhcpcd[743]: wlp12s0: carrier acquired
dhcpcd[743]: wlp12s0: soliciting an IPv6 router
dhcpcd[743]: wlp12s0: soliciting a DHCP lease
dhcpcd[743]: control command: dhcpcd -4qL -t 10 -K wlp12s0
dhcpcd[743]: wlp12s0: offered 192.168.1.13 from 192.168.1.1
dhcpcd[743]: wlp12s0: leased 192.168.1.13 for 86400 seconds
dhcpcd[743]: wlp12s0: adding host route to 192.168.1.13 via 127.0.0.1
dhcpcd[743]: wlp12s0: adding route to 192.168.1.0/24
dhcpcd[743]: wlp12s0: adding default route via 192.168.1.1
dhcpcd[743]: forked to background, child pid 903

fixes the connection.

Some extra info (these commands were run after killing and restarting dhcpcd, so the connection is currently working).

iw dev
phy#0
	Interface wlp12s0
		ifindex 3
		wdev 0x1
		addr 70:1a:04:95:73:d4
		ssid BICSNET
		type managed

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 00:25:64:7d:71:42 brd ff:ff:ff:ff:ff:ff
3: wlp12s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 70:1a:04:95:73:d4 brd ff:ff:ff:ff:ff:ff

lspci -vnn | grep 14e4:
0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)

lsmod | grep wl
wl                   2558644  0 
lib80211                3821  2 wl,lib80211_crypt_tkip
cfg80211              406112  1 wl

lsmod | grep b43
lsmod | grep ssb

pacman -Q broadcom-wl
broadcom-wl 5.100.82.112-13

pacman -Q linux
linux 3.10.7-1

cat /etc/netctl/wlp12s0-BICSNET

Description='WPA encryption settings for BICSNET'
Interface=wlp12s0
Connection=wireless
Security=wpa

IP=dhcp

ESSID='BICSNET'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='password'
# Uncomment this if your ssid is hidden
#Hidden=yes

Some background.
I was previously using broadcom-wl-dkms from the aur without problems but a recent update started causing problems. I got to the point I'm at by removing it and installing broadcom-wl from the aur. I've never had much luck with b43 and I've used broadcom-wl on a previous installation for quite some time with no problems.

Let me know if you need any more info.
Thanks

EDIT: grammar

Last edited by corp28 (2013-08-24 17:01:22)

corp28 · 2013-08-23 04:58:05

Thinking about it, I figured I'd post some of those commands before I kill dhcpcd (so the connection is currently down).

journalctl -xn

-- Logs begin at Sat 2013-07-06 18:39:40 EDT, end at Thu 2013-08-22 20:57:15 EDT. --
Aug 22 20:56:57 lappy dhcpcd[195]: wlp12s0: carrier acquired
Aug 22 20:56:57 lappy dhcpcd[195]: wlp12s0: carrier lost
Aug 22 20:56:57 lappy dhcpcd[195]: wlp12s0: waiting for carrier
Aug 22 20:56:59 lappy kernel: cfg80211: Calling CRDA to update world regulatory domain
Aug 22 20:57:01 lappy kernel: cfg80211: Calling CRDA to update world regulatory domain
Aug 22 20:57:04 lappy kernel: cfg80211: Calling CRDA to update world regulatory domain
Aug 22 20:57:11 lappy dhcpcd[195]: wlp12s0: carrier acquired
Aug 22 20:57:11 lappy dhcpcd[195]: wlp12s0: soliciting an IPv6 router
Aug 22 20:57:11 lappy dhcpcd[195]: wlp12s0: rebinding lease of 192.168.1.13

systemctl status dhcpcd@wlp12s0
dhcpcd@wlp12s0.service - dhcpcd on wlp12s0
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; disabled)
   Active: inactive (dead)

Aug 22 20:15:06 lappy systemd[1]: Starting dhcpcd on wlp12s0...
Aug 22 20:15:06 lappy systemd[1]: PID file /run/dhcpcd-wlp12s0.pid not readable (yet?) after start.
Aug 22 20:15:06 lappy systemd[1]: Failed to start dhcpcd on wlp12s0.
Aug 22 20:15:06 lappy systemd[1]: Unit dhcpcd@wlp12s0.service entered failed state.
Aug 22 20:17:05 lappy systemd[1]: Starting dhcpcd on wlp12s0...
Aug 22 20:17:05 lappy systemd[1]: PID file /run/dhcpcd-wlp12s0.pid not readable (yet?) after start.
Aug 22 20:17:05 lappy systemd[1]: Failed to start dhcpcd on wlp12s0.
Aug 22 20:17:05 lappy systemd[1]: Unit dhcpcd@wlp12s0.service entered failed state.

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 00:25:64:7d:71:42 brd ff:ff:ff:ff:ff:ff
3: wlp12s0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT mode DORMANT qlen 1000
    link/ether 70:1a:04:95:73:d4 brd ff:ff:ff:ff:ff:ff

iw dev
phy#0
	Interface wlp12s0
		ifindex 3
		wdev 0x1
		addr 70:1a:04:95:73:d4
		type managed

strugee · 2013-08-23 06:00:42

Try systemctl enable dhcpd?

corp28 · 2013-08-23 12:21:01

strugee wrote:

Try systemctl enable dhcpd?

I already have it enabled. dhcpcd is running and I have a wireless connection for a short window after booting. The network only then becomes unreachable; usually within a few seconds. Although there was at least one instance where the wireless connection was maintained beyond this window.

cfr · 2013-08-24 02:16:29

I would guess multiple things are fighting over the connection. Does netctl not manage dhcpd? If so, make sure you have *not* enabled it separately.

WonderWoofy · 2013-08-24 02:24:19

In fact, maybe you should give some output of what is actually running. Do systemctl --type=service --no-pager and post the output.

corp28 · 2013-08-24 16:59:54

cfr wrote:

I would guess multiple things are fighting over the connection. Does netctl not manage dhcpd? If so, make sure you have *not* enabled it separately.

Good call.

WonderWoofy wrote:

In fact, maybe you should give some output of what is actually running. Do systemctl --type=service --no-pager and post the output.

systemctl --type=service --no-pager
...
dhcpcd.service               loaded active running dhcpcd on all interfaces
netctl-auto@wlp12s0.service  loaded active running Automatic wireless network co
...

So i ran,

systemctl disable dhcpcd

and now the connection is maintained.

Thanks for the help.

EDIT: fixed quote attribution

Last edited by corp28 (2013-08-25 05:04:43)

cfr · 2013-08-24 21:07:58

Glad you sorted it but I did not make the second suggestion - only the first.

Arch Linux

#1 2013-08-23 04:43:00

[SOLVED] Connection lost shortly after boot

#2 2013-08-23 04:58:05

Re: [SOLVED] Connection lost shortly after boot

#3 2013-08-23 06:00:42

Re: [SOLVED] Connection lost shortly after boot

#4 2013-08-23 12:21:01

Re: [SOLVED] Connection lost shortly after boot

#5 2013-08-24 02:16:29

Re: [SOLVED] Connection lost shortly after boot

#6 2013-08-24 02:24:19

Re: [SOLVED] Connection lost shortly after boot

#7 2013-08-24 16:59:54

Re: [SOLVED] Connection lost shortly after boot

#8 2013-08-24 21:07:58

Re: [SOLVED] Connection lost shortly after boot

Board footer