[SOLVED] Arch crashing my router?

mr0no · 2013-10-17 23:56:13

I've got this problem after switching back to my old router after using some other one.
After 10-15min of using archlinux on my PC, my whole network goes down and router restarts. When I boot windows from the same PC everything is OK, so I am almost certain the router is OK (I even flashed the firmware on it).
I don't even know how to start fixing this...

Last edited by mr0no (2014-01-10 17:58:33)

cfr · 2013-10-18 00:07:06

Please have a read of smart questions. Your post offers almost no information which anybody might use to help you.

jasonwryan · 2013-10-18 00:10:32

Moving to NC...

mr0no · 2013-10-18 00:28:52

Yeah, well that's kinda part of the problem. It's just so weird the way this is happening. To me it appears to be random: everything works fine for 15-20min (sometimes less) and then I loose internet connection just like that. On the router I was using before everything was working fine.

When it's OK ip addr shows this:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 8c:89:a5:c1:bf:34 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.65/24 brd 10.0.0.255 scope global enp3s0
       valid_lft forever preferred_lft forever
    inet6 fe80::8e89:a5ff:fec1:bf34/64 scope link 
       valid_lft forever preferred_lft forever

When it crashes, this:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 8c:89:a5:c1:bf:34 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::8e89:a5ff:fec1:bf34/64 scope link 
       valid_lft forever preferred_lft forever

Then after router restarts everything is fine again.

Checking router log... and apparently I can't access my router's web UI (or telnet) only when my PC with arch booted is connected to the network. I'll have to reboot to windows to take a look at that.

And it happened again while I was writing this post...

WonderWoofy · 2013-10-18 00:41:00

When I used the Realtek card my machine shipped with, it was able to actually f*ck up other machine's connectability to the router. After a while I ended up getting an old router and making an access point just for my machine it was so bad. PITA really. It was the one infamous card that uses the rtl8192ce module.

mr0no · 2013-10-18 00:44:11

lspci -v:

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06)
	Subsystem: Micro-Star International Co., Ltd. Device 7752
	Flags: bus master, fast devsel, latency 0, IRQ 45
	I/O ports at d000 [size=256]
	Memory at f2104000 (64-bit, prefetchable) [size=4K]
	Memory at f2100000 (64-bit, prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, MSI 01
	Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
	Kernel driver in use: r8169

It should be OK because, as I said, everything is fine on windows, and everything was fine on the other router.

mr0no · 2013-10-18 00:53:43

Nothing out of the ordinary in router logs or dmesg...

WonderWoofy · 2013-10-18 02:47:32

You might want to try the r8168 module from [community]. I have a rev 7 of this card and it works fine so long as I use r8168. I'm not sure that it will fix your issue, and some people find that r8169 works fine for them. In fact someone I know with that same machine uses r8169 quite successfully. But I guess anything is worth a shot...

mr0no wrote:

It should be OK because, as I said, everything is fine on windows...

You know that this really means nothing apart from the fact that the ethernet card itself isn't broken...

ewaller · 2013-10-18 02:55:30

I have read this entire thread and have no idea as to :

The make and model of the "Good" router.
The make and model of the "Bad" router.
Are the good and bad router the same make/model?
This is a wired interface, but are there other wired devices attached? Are their wireless devices attached?
How are you managing your network?
Static or Dynamic addresses?
Anything interesting in the Arch logs or journal?
What speed are your computer and router negotiating?
Is your cable capable of Gigabit speeds?

nomorewindows · 2013-10-18 22:37:48

You know it's funny. I've a router that I have the dhcp turned off, and uses Arch's dhcpd working with all clients. I turned the router's dhcp on, and it doesn't bode well with any of my Linux clients, not just Arch. So it seems as if one of the implementations are off. And here I thought that my Linux clients were just having problems with commercial routers at schools or libraries. Maybe use Arch's dhcpd on the network instead of the router's dhcp.

Xyne · 2013-10-19 01:20:05

WonderWoofy wrote:

When I used the Realtek card my machine shipped with, it was able to actually f*ck up other machine's connectability to the router. After a while I ended up getting an old router and making an access point just for my machine it was so bad. PITA really. It was the one infamous card that uses the rtl8192ce module.

I have one of those cards and it is indeed a huge, steaming pile of shit. I was, however, not aware that it was so huge it could spill over onto other devices, but I do not doubt it at all.

WonderWoofy · 2013-10-19 02:42:07

Xyne wrote:

I have one of those cards and it is indeed a huge, steaming pile of shit. I was, however, not aware that it was so huge it could spill over onto other devices, but I do not doubt it at all.

Yeah I remember you mentioning having one of these. It pains me to think that others actually have to put up with this card. I was so incredibly disappointed by its performance on Linux, especially consiering it has an in-tree module. I was incredibly shocked that this card was able to cause other machines on my network to perform shittily (making up curse words, that card sucks so much) as well.

After realizing just how bas this card was, I begain actively looking for a replacement, which is no small task with a Lenovo bios whitelist. But once I figured out what to look for, I found one, then another... then another. So I am happily using a dual band broadcom card, which works great. Who would have ever thought that at some point a broadcom card would be preferrable?!

In any case, this thread is apparently about wired ethernet, which I failed to take notice of before issuing that response. But I guess nothing can really be accomplished here unless the OP actually returns bearing much much more info.

mr0no · 2013-12-03 12:56:02

So I finally found the time to get back at the issue.
I reinstalled arch (64 bit version this time to make a full use of my RAM) and the same problem persists. Even during installation I had the problems with connection, so it's probably not a configuration thing. I also tried no DHCP and with different DNS servers with no results.

ewaller wrote:

I have read this entire thread and have no idea as to :
The make and model of the "Good" router.
The make and model of the "Bad" router.
Are the good and bad router the same make/model?
This is a wired interface, but are there other wired devices attached? Are their wireless devices attached?
How are you managing your network?
Static or Dynamic addresses?
Anything interesting in the Arch logs or journal?
What speed are your computer and router negotiating?
Is your cable capable of Gigabit speeds?

Bad router Thomson TG782i
Good router Siemens Gigaset SX 763
But note that bad router worked fine until some point.

It's a wired interface and my PC is connected directly to the router LAN port. There are no other wired connected PCs but I have a debian PC connected over WIFI and 3 smartphones and 2 laptops occasionally connect wirelessly.

There is a DHCP server and a DNS server running are on the router.

Speed is 100 Mbps (router limit), but the card supports gigabit.

Maybe I should try some other distro to see if it's arch specific?

My mobo is MSI Z77A-G45.

Last edited by mr0no (2013-12-03 12:58:19)

nomorewindows · 2013-12-03 13:26:52

I don't see anything that procludes that Arch is the problem.

mr0no · 2013-12-04 18:45:41

I tried the r8168 driver by installing it's package from the official repos and when that didn't work by compiling the driver I got from here myself. I'm sure I did everything properly but both solutions didn't work.
I won't revert to r8169 and keep the r8168 for the time being.

mr0no · 2013-12-04 21:52:02

OK I've got some new info:

I ran Ubuntu 9.10 (Karmic Koala) live CD (it's kernel version 2.6). The networking doesn't work as it normally should, but it behaves differently than on arch nonetheless.

It runs normally for a period of time (around 3 minutes similarly to arch), but then it starts to have hiccups (no websites would load, and pings return host unreachable).
After that it would start working normally again for about 3 minutes.

There are no router crashes like in arch.

I ran pings to google.com and to facebook.com.
Ping times are 40 and 130 ms for google and facebook respectively, and that is what I would usually get on my DSL connection. So packets are not delayed, they either arrive in normal time or don't arrive at all.
When the hiccups are happening I get 3-4 host unreachable returns, which would be around 4-5% in total, but the packet loss reported at the end of the ping command was 40% for google and 60% for facebook.

This is lspci -v from ubuntu:

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
        Subsystem: Micro-Star International Co., Ltd. Device 7752
        Flags: bus master, fast devsel, latency 0, IRQ 32
        I/O ports at d000 [size=256]
        Memory at f2104000 (64-bit, prefetchable) [size=4K]
        Memory at f2100000 (64-bit, prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable- Mask- TabSize=4
        Capabilities: [d0] Vital Product Data <?>
        Capabilities: [100] Advanced Error Reporting <?>
        Capabilities: [140] Virtual Channel <?>
        Capabilities: [160] Device Serial Number 00-e0-4c-68-00-00-00-01
        Kernel driver in use: r8169
        Kernel modules: r8169

What can you make of this?

mr.MikyMaus · 2013-12-04 21:59:20

From what I can tell about the ethernet hardware you have the problem is most likely to be there. As someone mentioned these Realteks are crap. It may very well be a combination of different factors which could include the cable. Did you try using a different cable? Also what does dmesg say during those hiccups and after the "crash"?

mr0no · 2013-12-05 10:25:14

mr.MikyMaus wrote:

From what I can tell about the ethernet hardware you have the problem is most likely to be there. As someone mentioned these Realteks are crap. It may very well be a combination of different factors which could include the cable. Did you try using a different cable? Also what does dmesg say during those hiccups and after the "crash"?

I've switched the cable and router crashes are still happening on arch, but interestingly they are now less frequent - every 20 minutes or so.

This is the dmesg:

[Wed Dec  4 23:13:09 2013] r8168: enp3s0: link up
[Wed Dec  4 23:13:09 2013] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[Wed Dec  4 23:13:11 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Wed Dec  4 23:13:11 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Wed Dec  4 23:13:13 2013] r8168: enp3s0: link up
[Wed Dec  4 23:13:13 2013] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready

//first crash happening
[Wed Dec  4 23:33:43 2013] r8168: enp3s0: link down
[Wed Dec  4 23:33:46 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Wed Dec  4 23:33:47 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Wed Dec  4 23:33:57 2013] r8168: enp3s0: link up
[Wed Dec  4 23:33:57 2013] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready

//second crash
[Wed Dec  4 23:58:53 2013] r8168: enp3s0: link down
[Wed Dec  4 23:58:55 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Wed Dec  4 23:59:07 2013] r8168: enp3s0: link up
[Wed Dec  4 23:59:07 2013] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[Wed Dec  4 23:59:10 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Wed Dec  4 23:59:10 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Wed Dec  4 23:59:12 2013] r8168: enp3s0: link up
[Wed Dec  4 23:59:12 2013] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready

//third crash
[Thu Dec  5 00:12:36 2013] r8168: enp3s0: link down
[Thu Dec  5 00:12:36 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Thu Dec  5 00:12:36 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Thu Dec  5 00:12:40 2013] r8168: enp3s0: link up
[Thu Dec  5 00:12:40 2013] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[Thu Dec  5 00:12:41 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Thu Dec  5 00:12:41 2013] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[Thu Dec  5 00:12:43 2013] r8168: enp3s0: link up
[Thu Dec  5 00:12:43 2013] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[Thu Dec  5 00:12:45 2013] r8168: enp3s0: link down
[Thu Dec  5 00:12:47 2013] r8168: enp3s0: link up

//fourth crash
[Thu Dec  5 00:27:55 2013] sd_festival[5407]: segfault at 2d0 ip 00007fa4458ed191 sp 00007fff30e6b5f0 error 4 in libpthread-2.18.so[7fa4458e0000+18000]
//at this point I had to manually reboot the router because it got stuck.
[Thu Dec  5 00:33:33 2013] r8168: enp3s0: link down
[Thu Dec  5 00:33:38 2013] r8168: enp3s0: link up
[Thu Dec  5 00:35:13 2013] r8168: enp3s0: link down
[Thu Dec  5 00:35:28 2013] r8168: enp3s0: link up

//fifth crash
//it actually crashed at 00:51 and it took 7 minutes for router to boot up
//this is also true for prevous crashes: they happen few minutes before logs actually report "enp3s0 link down".
[Thu Dec  5 00:58:36 2013] r8168: enp3s0: link down
[Thu Dec  5 00:58:39 2013] r8168: enp3s0: link up
[Thu Dec  5 00:58:45 2013] r8168: enp3s0: link down
[Thu Dec  5 00:58:47 2013] r8168: enp3s0: link up

//Crash happening again at 01:18
//after that i stopped testing

Nothing was removed from the dmesg, just the comments were added.

I agree it's probably a combination of different factors including drivers too, because Windows can work it just fine.
And who's the main culprit? Router, network card, or drivers?

mr0no · 2014-01-10 17:55:40

I've finally solved the issue.

I bought a new PCI network card and tried out 3 different cables but the problem was still persisting, so the only thing left to look at was the router.
After trying 3 different firmwares I finally found the one that was working. Funny how some firmwares don't cope well with Linux.

[SOLVED]

WonderWoofy · 2014-01-10 18:32:13

I'm curious if you stuck with some random version of your router's official firmware or you switched to something OpenWRT based.

In any case, it is good you got this solved, as that must have been a real PITA.

mr0no · 2014-01-10 20:34:12

Unfortunately my router isn't supported by OpenWRT.
First two firmwares I tried were the newest version I could find and they are from some Mexican ISPs.
Third firmware is from some Dutch ISP and is older version but it seems to me it's very little modified from stock if modified at all.

Arch Linux

#1 2013-10-17 23:56:13

[SOLVED] Arch crashing my router?

#2 2013-10-18 00:07:06

Re: [SOLVED] Arch crashing my router?

#3 2013-10-18 00:10:32

Re: [SOLVED] Arch crashing my router?

#4 2013-10-18 00:28:52

Re: [SOLVED] Arch crashing my router?

#5 2013-10-18 00:41:00

Re: [SOLVED] Arch crashing my router?

#6 2013-10-18 00:44:11

Re: [SOLVED] Arch crashing my router?

#7 2013-10-18 00:53:43

Re: [SOLVED] Arch crashing my router?

#8 2013-10-18 02:47:32

Re: [SOLVED] Arch crashing my router?

#9 2013-10-18 02:55:30

Re: [SOLVED] Arch crashing my router?

#10 2013-10-18 22:37:48

Re: [SOLVED] Arch crashing my router?

#11 2013-10-19 01:20:05

Re: [SOLVED] Arch crashing my router?

#12 2013-10-19 02:42:07

Re: [SOLVED] Arch crashing my router?

#13 2013-12-03 12:56:02

Re: [SOLVED] Arch crashing my router?

#14 2013-12-03 13:26:52

Re: [SOLVED] Arch crashing my router?

#15 2013-12-04 18:45:41

Re: [SOLVED] Arch crashing my router?

#16 2013-12-04 21:52:02

Re: [SOLVED] Arch crashing my router?

#17 2013-12-04 21:59:20

Re: [SOLVED] Arch crashing my router?

#18 2013-12-05 10:25:14

Re: [SOLVED] Arch crashing my router?

#19 2014-01-10 17:55:40

Re: [SOLVED] Arch crashing my router?

#20 2014-01-10 18:32:13

Re: [SOLVED] Arch crashing my router?

#21 2014-01-10 20:34:12

Re: [SOLVED] Arch crashing my router?

Board footer