Wireless and wired internet stop working after a few hours

asportking · 2014-05-30 20:04:09

I don't have this issue on any other of my computers, or even on the same computer running Windows, so I think I can rule out the internet itself being the source of the problem. What happens is that, after connecting to the internet via networkmanager, it slows to an almost nonexistent crawl after an hour or so. Networkmanager still says that the computer is connected, but it seems like it's just hanging on by a thread (I'm no networking expert, that's just my general understanding of it), because if I try to ping google, it will attempt it for a while but eventually timeout and give me the usual error. This happens sporadically - I say an hour, but sometimes it can last for six hours, sometimes it can last for fifteen minutes. Sometimes there is sort of an "intermediate step" in its degradation where speedtest.net gives me around 1 Mb/s up and down, whereas my usual speed is 20 Mb/s down and 5 Mb/s up. I suspect it might be tied to the amount of usage of the internet, but I don't have any hard evidence of this.

Fixing this problem can also be a bit of a hit and miss. Sometimes just disconnecting and reconnecting works. If that doesn't work, I try erasing and re-creating the profile in Networkmanager, and sometimes that works. If all else fails, I can reboot, and the internet continues to work again, at least for a while longer. I have a Qualcomm Atheros AR8161 Gigabit Ethernet controller using the ath9k driver and a Qualcomm Atheros AR9485 Wireless Network Adapter controller using the alx driver. Is there any way to fix this?

bluestreak0 · 2014-05-30 21:22:25

Try restarting dhcpcd with

# systemctl restart dhcpcd

Might be DNS related: try a

$ ping -c 3 8.8.8.8

Upload to pastebin/gist etc the output of:

$ lspci -v

$ lsmod

# dmesg

$ systemctl status NetworkManager

$ systemctl status dhcpcd

preferably before and after said problem

jasonwryan · 2014-05-30 21:27:08

Wiki wrote:

Note: You must ensure that no other service that wants to configure the network is running, in fact multiple networking services will conflict. You can find a list of the currently running services with systemctl --type=service and then stop them.

asportking · 2014-05-31 02:37:28

bluestreak0 wrote:

Try restarting dhcpcd with
# systemctl restart dhcpcd
Might be DNS related: try a
$ ping -c 3 8.8.8.8
Upload to pastebin/gist etc the output of:
$ lspci -v
$ lsmod
# dmesg
$ systemctl status NetworkManager
$ systemctl status dhcpcd
preferably before and after said problem

Here's a pastebin of all the outputs before. Now I've just got to wait until the problem comes back, which, considering I actually want it to happen now, is probably going to take a while.

EDIT: Here's the outputs during the problem. One strange thing I noticed is that running systemctl status NetworkManger and systemctl status dhcpcd gives the error-like messages you see, but running them with sudo gives me the same outputs that I got before the problem arose.

jasonwryan wrote:

Wiki wrote:
Note: You must ensure that no other service that wants to configure the network is running, in fact multiple networking services will conflict. You can find a list of the currently running services with systemctl --type=service and then stop them.

Nope, no other services running.

Last edited by asportking (2014-05-31 03:56:48)

bluestreak0 · 2014-05-31 09:39:18

You're right, that is strange. By the way, it is your wifi device that is using ath9k. Your ethernet uses alx. They are both listed in the lsmod, so that's not the problem.

dmesg doesn't *seem* to be reporting any issues.

Have you tried connecting using wifi?

And how did you connect to the internet in the install? Did that have problems too?

Sorry I couldn't reply earlier, timezones are annoying.

Last edited by bluestreak0 (2014-05-31 09:48:32)

youngdm · 2014-05-31 09:42:24

I have the same problem on a MacBook Pro (7,1) with arch 3.14.4-1. I've only recently switched to NM from netctl where this issue didn't occur. No other device on our network has connection problems. Have you seen this link? https://bugzilla.gnome.org/show_bug.cgi?id=678363 I haven't got access to my PC at the moment so can't test it, but will do so when I am able. It might be worth a try. Just thought I'd let you know.

bluestreak0 · 2014-05-31 09:55:24

Asportking: Try doing:

# rmmod -v alx
# modprobe -v alx

or

# rmmod -v ath9k
# modprobe -v ath9k

if on wifi

jasonwryan · 2014-05-31 10:10:02

asportking wrote:

jasonwryan wrote:
Wiki wrote:
Note: You must ensure that no other service that wants to configure the network is running, in fact multiple networking services will conflict. You can find a list of the currently running services with systemctl --type=service and then stop them.
Nope, no other services running.

asportking wrote:

Here's the outputs during the problem:
● NetworkManger.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
● dhcpcd.service - dhcpcd on all interfaces
Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled)
Active: inactive (dead)

That's two services, by my count...

asportking · 2014-05-31 11:06:06

jasonwryan wrote:

asportking wrote:

Nope, no other services running.
asportking wrote:
Here's the outputs during the problem:
● NetworkManger.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
● dhcpcd.service - dhcpcd on all interfaces
Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled)
Active: inactive (dead)

That's two services, by my count...

I was under the impression that dhcpcd was a part of NetworkManger. Is that not true?

bluestreak0 wrote:

Asportking: Try doing:
# rmmod -v alx
# modprobe -v alx
or
# rmmod -v ath9k
# modprobe -v ath9k
if on wifi

Doing the last command on each gives me

insmod /lib/modules/3.14.4.-1-ARCH/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko.gz nohwcrypt=1 asus_nb_wmi wapf=1

and

insmod /lib/modules/3.14.4-1-ARCH/kernel/drivers/net/ethernet/atheros/alx/alx.ko.gz

Additionally, it seems as though doing this fixes the problem, at least temporarily.

youngdm wrote:

I have the same problem on a MacBook Pro (7,1) with arch 3.14.4-1. I've only recently switched to NM from netctl where this issue didn't occur. No other device on our network has connection problems. Have you seen this link? https://bugzilla.gnome.org/show_bug.cgi?id=678363 I haven't got access to my PC at the moment so can't test it, but will do so when I am able. It might be worth a try. Just thought I'd let you know.

Problem persists when using netctl, wifi-menu, and NetworkManager. I tried the fix you sent me, and am currently waiting to see if the problem comes back.

bluestreak0 wrote:

You're right, that is strange. By the way, it is your wifi device that is using ath9k. Your ethernet uses alx. They are both listed in the lsmod, so that's not the problem.
dmesg doesn't *seem* to be reporting any issues.
Have you tried connecting using wifi?
And how did you connect to the internet in the install? Did that have problems too?
Sorry I couldn't reply earlier, timezones are annoying.

Yes, connecting via wifi gives the same problems. Maybe even faster, although that might just be my imagination. I connected to the internet wirelessly via wifi-menu, and although nothing happened that I can remember, I wasn't connected very long.

Also, forgot to mention: tried pinging 8.8.8.8 and got the same problem.

bluestreak0 · 2014-05-31 12:11:35

Maybe you could try, at least temporarily, just to ditch NetworkManager and use dhcpcd exclusively instead? After what jasonwryan said, they might well be conflicting.

BTW, what the rmmod and modprobe are doing is unloading and reloading the drivers for your network cards. Its just an alternative to rebooting (and faster, and you don't loose any open applications. Needs root though).

loqs · 2014-05-31 12:32:16

jasonwryan wrote:

asportking wrote:

Nope, no other services running.
asportking wrote:
Here's the outputs during the problem:
● NetworkManger.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
● dhcpcd.service - dhcpcd on all interfaces
Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled)
Active: inactive (dead)

That's two services, by my count...

NetworkManger.service misspelt should be NetworkManager.service
dhcpcd.service is disabled so that is probably still only one active service attempting to control the network interfaces

HiImTye · 2014-05-31 23:18:36

are you using any special traffic shaping rules? any DHT type services (such as YaCy)?

Last edited by HiImTye (2014-05-31 23:19:01)

asportking · 2014-06-01 04:09:43

HiImTye wrote:

are you using any special traffic shaping rules? any DHT type services (such as YaCy)?

No. Should I be?

Also, the previous fix mentioned stopped working after a while. Seemed like it lasted longer than most other tries, although I might have just gotten lucky.

bluestreak0 · 2014-06-01 09:20:43

Try *just* using dhcpcd, see if that works.

# systemctl disable NetworkManager
# systemctl stop NetworkManager
# systemctl enable dhcpcd
# systemctl start dhcpcd

And then reboot for good measure.

Make sure you are connected to ethernet with this; I don't know if dhcpcd handles WiFi connections.

Arch Linux

#1 2014-05-30 20:04:09

Wireless and wired internet stop working after a few hours

#2 2014-05-30 21:22:25

Re: Wireless and wired internet stop working after a few hours

#3 2014-05-30 21:27:08

Re: Wireless and wired internet stop working after a few hours

#4 2014-05-31 02:37:28

Re: Wireless and wired internet stop working after a few hours

#5 2014-05-31 09:39:18

Re: Wireless and wired internet stop working after a few hours

#6 2014-05-31 09:42:24

Re: Wireless and wired internet stop working after a few hours

#7 2014-05-31 09:55:24

Re: Wireless and wired internet stop working after a few hours

#8 2014-05-31 10:10:02

Re: Wireless and wired internet stop working after a few hours

#9 2014-05-31 11:06:06

Re: Wireless and wired internet stop working after a few hours

#10 2014-05-31 12:11:35

Re: Wireless and wired internet stop working after a few hours

#11 2014-05-31 12:32:16

Re: Wireless and wired internet stop working after a few hours

#12 2014-05-31 23:18:36

Re: Wireless and wired internet stop working after a few hours

#13 2014-06-01 04:09:43

Re: Wireless and wired internet stop working after a few hours

#14 2014-06-01 09:20:43

Re: Wireless and wired internet stop working after a few hours

Board footer