[SOLVED] Wired connection drops after a few seconds

deltux · 2015-08-23 20:33:07

When I connect to my wired network using netctl, the connection drops automatically after a few seconds. It happens both with DHCP and static configuration, but the wifi connection on the same network works perfectly.

What really bothers me is that there is absolutely nothing in the logs, the output of journalctl is absolutely normal during network start-up, and nothing happens when the network disconnects.

Aug 22 18:34:37 dimension polkitd[5127]: Registered Authentication Agent for unix-process:7050:2995548 (system bus name :1.66 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Aug 22 18:34:37 dimension systemd[1]: Starting Networking for netctl profile static...
Aug 22 18:34:37 dimension network[7055]: Starting network profile 'static'...
Aug 22 18:34:37 dimension kernel: IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
Aug 22 18:34:37 dimension kernel: alx 0000:04:00.0 enp4s0: NIC Up: 1 Gbps Full
Aug 22 18:34:37 dimension kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
Aug 22 18:34:37 dimension avahi-daemon[558]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.43.
Aug 22 18:34:37 dimension avahi-daemon[558]: New relevant interface enp4s0.IPv4 for mDNS.
Aug 22 18:34:37 dimension avahi-daemon[558]: Registering new address record for 192.168.0.43 on enp4s0.IPv4.
Aug 22 18:34:37 dimension avahi-daemon[558]: Registering new address record for 192.168.0.175 on enp4s0.IPv4.
Aug 22 18:34:37 dimension network[7055]: Started network profile 'static'
Aug 22 18:34:37 dimension systemd[1]: Started Networking for netctl profile static.
Aug 22 18:34:37 dimension polkitd[5127]: Unregistered Authentication Agent for unix-process:7050:2995548 (system bus name :1.66, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

I have tried connecting directly to the router, I have changed the IP addresses, and I have tried with wicd instead of netctl, with always the same issue.

Last edited by deltux (2015-09-11 15:48:46)

Techmeology · 2015-08-23 20:54:31

Is there anything interesting in dmesg?

Trilby · 2015-08-23 20:58:47

What networking services are you running? Having competing services is the number one cause of this sort of issue.

Head_on_a_Stick · 2015-08-23 21:08:57

What is your hardware?

lspci -knn|grep -iA2 net

deltux · 2015-08-24 07:16:07

There is nothing interesting in dmesg, as in journalctl. I have been careful of running only one instance of netctl, and none of wicd. I use nothing else.

Here is my hardware:

03:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 2230 [8086:0887] (rev c4)
	Subsystem: Intel Corporation Centrino Wireless-N 2230 BGN [8086:4062]
	Kernel driver in use: iwlwifi
--
04:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8161 Gigabit Ethernet [1969:1091] (rev 08)
	Subsystem: ASUSTeK Computer Inc. N56VZ [1043:1477]
	Kernel driver in use: alx

Thanks for the help!

Head_on_a_Stick · 2015-08-24 10:51:02

Some tricks you can try with the iwlwifi driver here:
https://wiki.archlinux.org/index.php/Wi … on#iwlwifi
http://forums.debian.net/viewtopic.php?f=16&t=121696

deltux · 2015-08-24 13:41:52

I tried, without success. But I don't understand why iwlwifi is concerned, the WiFi works perfectly. It is the wired network that is concerned, but I didn't find the same kind of "tricks" for the alx driver....

Head_on_a_Stick · 2015-08-24 17:41:25

deltux wrote:

It is the wired network that is concerned

Oh dear, sorry about that.

Note to self: *read* the OP...

deltux · 2015-08-28 18:49:57

I just tried with another distro (Kali live) and it works perfectly! So it is definitely a software issue, I was beginning to doubt of my network card...

Is this an issue with a recent update? Should I report a bug, and if so, where?

mathfreak · 2015-08-30 15:35:51

For what it's worth, I'm having a very similar problem. I can't even connect, actually. Nothing strange appears in dmesg or in journalctl. I can connect just fine with a USB wifi device. My HTPC that also runs arch hasn't been upgraded for a couple of weeks and it can connect with a wired connection just fine. If I boot off of the USB disk into Ubuntu, I can connect via the wired connection just fine.

My hardware is different than yours, though:

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)
        Subsystem: Lenovo Device [17aa:3821]
        Kernel driver in use: r8169

Head_on_a_Stick · 2015-08-30 15:40:34

A few suggestions here:
https://wiki.archlinux.org/index.php/Ne … leshooting

deltux · 2015-09-06 08:06:04

I still have my issue, nothing seems to work, even the latest updates of systemd, dhcpcd, etc. I can't understand anything around this issue, I've used Arch for more than 3 years and I hadn't met anything like this until now... Should I completely reinstall my system? Although I'm sure it is clean, and the Archlinux team promised one would never have to reinstall completely...

ewaller · 2015-09-06 14:59:43

deltux wrote:

Should I completely reinstall my system?...the Archlinux team promised one would never have to reinstall completely...

Don't reinstall.

Post the output of lspci -nn and of find /etc/systemd

Last edited by ewaller (2015-09-06 15:00:01)

deltux · 2015-09-06 15:55:20

Thanks for the answer! Here it is:

lspci -nn

00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09)
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
00:1c.3 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 [8086:1e16] (rev c4)
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation HM76 Express Chipset LPC Controller [8086:1e59] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev ff)
03:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 2230 [8086:0887] (rev c4)
04:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8161 Gigabit Ethernet [1969:1091] (rev 08)

find /etc/systemd

/etc/systemd
/etc/systemd/user.conf
/etc/systemd/timesyncd.conf~
/etc/systemd/logind.conf
/etc/systemd/logind.conf~
/etc/systemd/journald.conf
/etc/systemd/logind.conf.pacnew
/etc/systemd/system.conf
/etc/systemd/bootchart.conf
/etc/systemd/journal-remote.conf
/etc/systemd/system
/etc/systemd/system/mpd.socket
/etc/systemd/system/powertop.service
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/graphical.target.wants
/etc/systemd/system/graphical.target.wants/bumblebeed.service
/etc/systemd/system/dbus-org.freedesktop.Avahi.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/powertop.service
/etc/systemd/system/multi-user.target.wants/netctl-ifplugd@mystatic.service
/etc/systemd/system/multi-user.target.wants/avahi-daemon.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/haveged.service
/etc/systemd/system/multi-user.target.wants/org.cups.cupsd.path
/etc/systemd/system/printer.target.wants
/etc/systemd/system/printer.target.wants/org.cups.cupsd.service
/etc/systemd/system/sysinit.target.wants
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/systemd/system/powertop.service~
/etc/systemd/system/sockets.target.wants
/etc/systemd/system/sockets.target.wants/mpd.socket
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket
/etc/systemd/system/sockets.target.wants/org.cups.cupsd.socket
/etc/systemd/system/network-wireless-adhoc@.service~
/etc/systemd/resolved.conf
/etc/systemd/timesyncd.conf
/etc/systemd/journal-upload.conf
/etc/systemd/user
/etc/systemd/coredump.conf
/etc/systemd/timesyncd.conf.pacnew
/etc/systemd/network

ewaller · 2015-09-06 16:08:59

What tool are you using to control your wireless? I don't see any of the usual suspects being started by systemd. Also, you may want to clean up those .pacnew files.
The good news, Intel wireless are generally well supported.

deltux · 2015-09-06 16:24:34

I use netctl to connect to all my networks (both wired and wireless), although I've tested this issue with wicd. I've always kept my .pacnew files around if I wanted to change anything. Is that bad practice?

ewaller · 2015-09-06 16:41:02

Keeping pacnew files around is fine, just be sure to role the new features of them into your active configuration files.

So, you are using netctl. Are you starting the profiles by hand when you need them? I ask, because all I see is netctl-ifplug

Wait -- What is this?

/etc/systemd/system/network-wireless-adhoc@.service~

Also, now, could you post the output of systemctl status --no-pager

deltux · 2015-09-06 16:46:11

I don't use ifplugd (just uninstalled it btw), I launch netctl manually each time I boot. network-wireless-adhoc is a service that I use to create adhoc wifi network to share my wired connection (not running now, obviously).

systemctl status --no-pager

● dimension
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Sun 2015-09-06 10:00:49 CEST; 8h ago
   CGroup: /
           ├─1 /sbin/init
           ├─system.slice
           │ ├─avahi-daemon.service
           │ │ ├─492 avahi-daemon: running [dimension.local]
           │ │ └─500 avahi-daemon: chroot helper
           │ ├─dbus.service
           │ │ └─485 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
           │ ├─org.cups.cupsd.service
           │ │ └─488 /usr/bin/cupsd -l
           │ ├─system-netctl.slice
           │ │ └─netctl@FreeboxLZV.service
           │ │   ├─ 965 wpa_supplicant -q -B -P /run/wpa_supplicant_wlp3s0.pid -i wlp3s0 -D nl80211,wext -c/run/network/wpa_supplicant_wlp3s0.conf
           │ │   └─1116 dhcpcd -4 -q -t 30 -L wlp3s0
           │ ├─mpd.service
           │ │ └─589 /usr/bin/mpd --no-daemon
           │ ├─bumblebeed.service
           │ │ └─490 /usr/bin/bumblebeed
           │ ├─colord.service
           │ │ └─501 /usr/lib/colord/colord
           │ ├─systemd-journald.service
           │ │ └─208 /usr/lib/systemd/systemd-journald
           │ ├─systemd-timesyncd.service
           │ │ └─478 /usr/lib/systemd/systemd-timesyncd
           │ ├─systemd-logind.service
           │ │ └─489 /usr/lib/systemd/systemd-logind
           │ ├─systemd-udevd.service
           │ │ └─234 /usr/lib/systemd/systemd-udevd
           │ ├─haveged.service
           │ │ └─483 /usr/bin/haveged -F -w 1024 -v 1
           │ └─polkit.service
           │   └─653 /usr/lib/polkit-1/polkitd --no-debug
           └─user.slice
             └─user-1000.slice
               ├─user@1000.service
               │ ├─518 /usr/lib/systemd/systemd --user
               │ ├─520 (sd-pam)
               │ └─emacs.service
               │   └─525 /usr/bin/emacs --daemon
               └─session-c1.scope
                 ├─  493 login -- dimitri
                 ├─  529 -zsh
                 ├─  532 /bin/sh /usr/bin/startx
                 ├─  554 xinit /home/dimitri/.xinitrc -- /etc/X11/xinit/xserverrc :0 vt1 -auth /tmp/serverauth.JXH3xya4v1
                 ├─  555 /usr/lib/xorg-server/Xorg -nolisten tcp :0 vt1 -auth /tmp/serverauth.JXH3xya4v1
                 ├─  559 xf86-video-intel-backlight-helper intel_backlight
                 ├─  562 awesome
                 ├─  567 sh /home/dimitri/.xinitrc
                 ├─  575 conky
                 ├─  576 urxvt
                 ├─  586 /usr/bin/dbus-launch --autolaunch ede0b03b1efe470797b665f816c53f25 --binary-syntax --close-stderr
                 ├─  590 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
                 ├─  593 zsh
                 ├─  598 /home/dimitri/.dropbox-dist/dropbox-lnx.x86_64-3.8.8/dropbox /newerversion
                 ├─  718 firefox
                 ├─ 4008 /bin/zsh
                 ├─ 4017 thunderbird
                 ├─11971 /usr/lib/at-spi2-core/at-spi-bus-launcher
                 ├─11977 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
                 ├─11980 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
                 ├─12004 /usr/lib/dconf/dconf-service
                 ├─20730 /usr/lib/firefox/plugin-container /usr/lib/mozilla/plugins/libflashplayer.so -greomni /usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omn...
                 ├─24009 su
                 ├─24013 zsh
                 └─24782 systemctl status --no-pager

Last edited by deltux (2015-09-06 16:49:07)

ewaller · 2015-09-06 17:23:45

It is strange for a wired connection to drop.
And the wifi is not at issue

And other OSes don't have issues with the same router and cable.
What is the indication that the connection 'drops'?
What are the link lights doing on the computer and (if available) the router?
This is a gigabit device. Is the router a gigabit device? Is the cable up to gigabit speeds? Do you know what speed the other OSes are connecting at?
under kali, did you happen to note which driver was being used?

Head_on_a_Stick · 2015-09-06 17:25:18

Can we see the output of:

dmesg|egrep 'enp|firmw|dhc'

deltux · 2015-09-06 17:52:43

There is no clear indication that the connection drops. For example, I ping repeatedly Google until it says "unknown host", and it is the same with a browser: I can load pages normally, until it says "cannot access the internet". And there is absolutely nothing in the logs when the connection drops.
The lights blink normally all the time. Everything is gigabit, I have the issue even when I connect directly to the router, which is one of those latest models. The other OSes connect at normal speed (very good, for I am on fiber).
I can't check which driver kali uses right now, I'll tell you more as soon as I can boot it up again.

dmesg|egrep 'enp|firmw|dhc'

[    8.554877] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x361f03)
[    9.154752] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm
[   10.574846] alx 0000:04:00.0 enp4s0: renamed from eth0
[   64.041601] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
[   64.042762] alx 0000:04:00.0 enp4s0: NIC Up: 1 Gbps Full
[   64.042999] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
[31542.308637] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
[31542.309413] alx 0000:04:00.0 enp4s0: NIC Up: 1 Gbps Full
[31542.309649] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready

ewaller · 2015-09-06 17:58:44

What kernel are you using? What is the output of uname -a ?
Are you using IPv6? Did kali use IPv6?

deltux · 2015-09-06 18:04:23

uname -a

Linux dimension 4.1.6-1-ARCH #1 SMP PREEMPT Mon Aug 17 08:52:28 CEST 2015 x86_64 GNU/Linux

(It is the standard Arch kernel.)
I use IPv4. I assume kali used the same.

Last edited by deltux (2015-09-06 18:05:05)

deltux · 2015-09-07 15:59:37

I've just checked under kali: the same driver (alx) is used, allthough through NetworkManager this time. I will try with NetworkManager on Arch, although I believe NM creates more issues than it solves... And I confirmed it is IPv4.
[EDIT] Just tried with NetworkManager... I got the exact same issue. Connection drops, and nothing in the (although verbose) logs of NM.

Last edited by deltux (2015-09-07 16:28:44)

wildcat71 · 2015-09-10 12:20:03

Hi deltux,
I saw you have the same ethernet card I have on my laptop, Atheros AR8161, that, unfortunately for us, is affected by an ALX driver bug with latest kernels.

If your problem is related to this bug you can try a workaround:

#ifconfig eth0 mtu 9000

where, instead of "eth0", you put your ethernet interface name. (Source)

You can also try:

#ip link set <your_eth_name> mtu 9000

The value 9000 worked for me, I didn't test others values

If it works, you can make this change permanent following the Jumbo Frames Section of the wiki.

Hope this solves your issue too.

Riccardo

Last edited by wildcat71 (2015-09-10 12:21:22)

Arch Linux

#1 2015-08-23 20:33:07

[SOLVED] Wired connection drops after a few seconds

#2 2015-08-23 20:54:31

Re: [SOLVED] Wired connection drops after a few seconds

#3 2015-08-23 20:58:47

Re: [SOLVED] Wired connection drops after a few seconds

#4 2015-08-23 21:08:57

Re: [SOLVED] Wired connection drops after a few seconds

#5 2015-08-24 07:16:07

Re: [SOLVED] Wired connection drops after a few seconds

#6 2015-08-24 10:51:02

Re: [SOLVED] Wired connection drops after a few seconds

#7 2015-08-24 13:41:52

Re: [SOLVED] Wired connection drops after a few seconds

#8 2015-08-24 17:41:25

Re: [SOLVED] Wired connection drops after a few seconds

#9 2015-08-28 18:49:57

Re: [SOLVED] Wired connection drops after a few seconds

#10 2015-08-30 15:35:51

Re: [SOLVED] Wired connection drops after a few seconds

#11 2015-08-30 15:40:34

Re: [SOLVED] Wired connection drops after a few seconds

#12 2015-09-06 08:06:04

Re: [SOLVED] Wired connection drops after a few seconds

#13 2015-09-06 14:59:43

Re: [SOLVED] Wired connection drops after a few seconds

#14 2015-09-06 15:55:20

Re: [SOLVED] Wired connection drops after a few seconds

#15 2015-09-06 16:08:59

Re: [SOLVED] Wired connection drops after a few seconds

#16 2015-09-06 16:24:34

Re: [SOLVED] Wired connection drops after a few seconds

#17 2015-09-06 16:41:02

Re: [SOLVED] Wired connection drops after a few seconds

#18 2015-09-06 16:46:11

Re: [SOLVED] Wired connection drops after a few seconds

#19 2015-09-06 17:23:45

Re: [SOLVED] Wired connection drops after a few seconds

#20 2015-09-06 17:25:18

Re: [SOLVED] Wired connection drops after a few seconds

#21 2015-09-06 17:52:43

Re: [SOLVED] Wired connection drops after a few seconds

#22 2015-09-06 17:58:44

Re: [SOLVED] Wired connection drops after a few seconds

#23 2015-09-06 18:04:23

Re: [SOLVED] Wired connection drops after a few seconds

#24 2015-09-07 15:59:37

Re: [SOLVED] Wired connection drops after a few seconds

#25 2015-09-10 12:20:03

Re: [SOLVED] Wired connection drops after a few seconds

Board footer