r8169: Link is down

bancsorin10 · 2023-11-17 07:51:24

Just moved to another place and I can't get my internet to work, and it has been a couple of days of me trying to debug this but to no avail. Wifi has not been working either and at the moment I am trying with a cabled connection but I cannot connect. `dmesg` shows the folloing:

[1101242.981240] RTL8208 Fast Ethernet r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
[1101243.108707] pcieport 0000:00:1c.4: AER: Multiple Corrected error received: 0000:02:00.0
[1101243.108747] r8169 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[1101243.108757] r8169 0000:02:00.0:   device [10ec:8136] error status/mask=00000001/00006000
[1101243.108766] r8169 0000:02:00.0:    [ 0] RxErr                  (First)
[1101243.265040] r8169 0000:02:00.0 enp2s0: Link is Down

some of the times it just shows:

[1105137.989660] RTL8208 Fast Ethernet r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
[1105138.250037] r8169 0000:02:00.0 enp2s0: Link is Down

What I have tried:

`sudo modprobe -r r8169 && sudo modprobe r8169`
`sudo ethtool -s enp2s0 speed 100 duplex full autoneg off`
`ip link set enp2s0 down && ip link set enp2s0 up`
tweaking router networking settings turning on and off stuff, disabling filters, etc.
didn't manage to get anything on `tcpdump` (at first there were some packets sent that I did
not catch but which were registered on the router history but after that the connection was cut,
tried to repeat those packages by moving to another interface on the router, but the same thing happened)

Mentioning that:

I cannot ping the router
laptop wifi and ethernet work just fine at work
another 2 phones and a laptop can connect just fine to the network (had some problems with one of the phones too but it works now)
(sorry but I might be slow to respond to requests since I am not permanently moved to
the place and might take up to a week to give new logs if I am not there )
also had this question on reddit https://www.reddit.com/r/archlinux/comm … k_is_down/ but moving the question in the forum

Last edited by bancsorin10 (2023-11-17 07:56:52)

twelveeighty · 2023-11-17 16:45:33

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

bancsorin10 · 2023-11-23 20:12:24

http://0x0.st/Hw_u.log <- here it is; (there are logs on wireless failing too)

twelveeighty · 2023-11-24 16:13:01

I don't see an obvious root cause in your journal. Here are some observations that could be relevant:

1) Your kernel dates from back in October; when was the last time you ran pacman -Syu?
2) You have installed the relevant linux-firmware, correct?
3) There appears to be a lot of network configuration mentioned in your journal, how exactly have you configured your network(s)? These entries, for example, seem bizarre:

Nov 23 22:06:59 rabbit dnsmasq[652]: bad address at /etc/hosts line 31
Nov 23 22:06:59 rabbit dnsmasq[632]: read /etc/hosts - 97176 names

You really have almost 100,000 entries in your /etc/hosts file?

bancsorin10 · 2023-11-25 13:58:45

I ran the last `pacman -Syu` back in october, I don't do the updates as often as one should unfortunately, I ran it after I've seen the problems on the wireless connection, tried to do the updates to maybe fix them but to no avail. I don't know what other linux-firmware I could be installing; the wireless and cabled connection are working usually, it is just this new router that is behaving.
My /etc/hosts has a lot of entries most of them copied from a github project that enumerated some ad websites that are often used; I have it so I block some extra ads or entries on shady sites etc. (this is also outdated probably )
Can the problem be router related?

seth · 2023-11-27 16:38:20

Try to add "pcie_aspm=off" to the https://wiki.archlinux.org/title/Kernel_parameters

bancsorin10 · 2023-12-07 21:09:10

`pcie_aspm` is not toggle able in the kernel options, it was on bios default (which I don't know what it was) and I specifically made it to be `performance` which as I understand it should be off. But it didn't help, I'll put some logs from the wifi connection, there seems to still be a power limiting (should I try manually hitting `no` for the `pcie_aspm` in the kernel config and build it ?)

dmesg logs:

[  650.575383] wlp3s0: authenticate with 14:18:2a:40:cf:71
[  650.575431] wlp3s0: 80 MHz not supported, disabling VHT
[  650.582412] wlp3s0: send auth to 14:18:2a:40:cf:71 (try 1/3)
[  650.627780] wlp3s0: authenticated
[  650.630967] wlp3s0: associate with 14:18:2a:40:cf:71 (try 1/3)
[  650.639831] wlp3s0: RX AssocResp from 14:18:2a:40:cf:71 (capab=0x1411 status=0 aid=8)
[  650.648205] wlp3s0: associated
[  650.648319] wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 14:18:2a:40:cf:71
[  655.652388] wlp3s0: deauthenticated from 14:18:2a:40:cf:71 (Reason: 2=PREV_AUTH_NOT_VALID)

nmcli command:

nmcli d w c DIGI-t6WN
Error: Connection activation failed: Secrets were required, but not provided.

(secrets were provided it just fails with that message, but it is not relevant, tried using the `ask` option to ask for the password but after entering it a few times it still fails)

seth · 2023-12-07 21:21:15

This has nothing to do with the BIOS, did you click the link on how to add kernel parameters?

Also r8169 isn't a wifi chip and you're getting kicked by the wifi AP, the reason might bethat it doesn't like MAC spoofing, https://wiki.archlinux.org/title/Networ … domization
But that has absolutely nothing to do with the subject of this thread.

bancsorin10 · 2023-12-07 21:27:39

Good news, after running another set of `pacman -Syyu`, restarting, and doing the `echo performance > /sys/module/pcie_aspm/parameters/policy`, the wired connection is working at last; (the wifi is still not working but at least I have internet); Do you think I should try more to remove the `pcie_aspm` from the kernel in order to figure the wifi out?

bancsorin10 · 2023-12-07 21:29:56

Yes, I've clicked on the link, it had different methods of adding parameters to how things are handled; I've found the `pcie_aspm` and tried to remove it by doing `make menuconfig` and create a config that way for the kernel, but I wasn't able to

seth · 2023-12-07 21:45:14

I doubt the wifi issues (which are just introduced into this thread off topic) are related to aspm? Or did/does the connection work w/o aspm control?
Did you try to disable the MAC randomization?

bancsorin10 · 2023-12-07 22:05:03

update again, internet worked for like half an hour, now is no longer connecting on anything again. Starting to feel like its a router problem, once I was connected the internet started to fail on other devices (phones, another laptop)

router: `fiberhome SR1041Y`

edit: wifi was never working, mentioned this in the first post on this thread, mac randomization is off

Last edited by bancsorin10 (2023-12-07 22:08:14)

seth · 2023-12-08 08:43:47

update again, internet worked for like half an hour, now is no longer connecting on anything again.

Are you currently talking about the r8169 connection or the wifi?
Journal for that situation? (paraphrasing "does nots works" is devoid of any meaningful information)

once I was connected the internet started to fail on other devices (phones, another laptop)

You mean once the r8169 connection was established your phone and other laptop got kicked from the router?

Did you try to reboot the router?
Is it running out of leases (because of stale ones)?
Do you implement a MAC filter on the router?

bancsorin10 · 2023-12-12 21:04:16

to answer some of the questions:

+ once the connection was established the other devices were not automatically kicked out, rather there were periods where the router seemed to no longer be processing packets, causing noticeable waits of seconds up to several minutes
+ Yes I rebooted the router multiple times
+ I don't think it is running out of leases (i reserved my interfaces to have static ips)
+ there is no mac filtering

I'll come back with logs for the wireless interface also (once i get to get them)

seth · 2023-12-12 21:39:23

Also check "ip -s l" on whether you've many transmission errors.
And try a different cable.

bancsorin10 · 2023-12-14 20:53:57

Didn't manage to get another connection in to see dropped packages (at least with the current cable -- I don't necessary suspect the cable since it is a new one, I've also tested it with a cable tester, but didn't plug it in other networks to check for sure; I will test with another cable when I get the opportunity).

Also got some logs on the wifi failing (might offer more feedback - it looks more verbose at least compared to the wired connection):

journalctl:

Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9594] audit: op="connection-update" uuid="9048a06b-ab4d-4cbd-a6e5-05c2aa6e4efa" name="DIGI-t6WN" pid=177187>
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9762] device (wlp3s0): Activation: starting connection 'DIGI-t6WN' (9048a06b-ab4d-4cbd-a6e5-05c2aa6e4efa)
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9763] audit: op="connection-activate" uuid="9048a06b-ab4d-4cbd-a6e5-05c2aa6e4efa" name="DIGI-t6WN" pid=1771>
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9764] device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9767] manager: NetworkManager state is now CONNECTING
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9770] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9773] device (wlp3s0): Activation: (wifi) access point 'DIGI-t6WN' has security, but secrets are required.
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9773] device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9775] sup-iface[07ba5cd8833d9e36,16,wlp3s0]: wps: type pbc start...
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9785] device (wlp3s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9788] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9791] device (wlp3s0): Activation: (wifi) connection 'DIGI-t6WN' has security, and secrets exist.  No new s>
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9791] Config: added 'ssid' value 'DIGI-t6WN'
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9791] Config: added 'scan_ssid' value '1'
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9791] Config: added 'bgscan' value 'simple:30:-70:86400'
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9791] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9792] Config: added 'auth_alg' value 'OPEN'
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9792] Config: added 'psk' value '<hidden>'
Dec 14 22:42:07 rabbit wpa_supplicant[551]: wlp3s0: WPS-CANCEL
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9947] device (wlp3s0): supplicant interface state: inactive -> scanning
Dec 14 22:42:07 rabbit NetworkManager[32350]: <info>  [1702586527.9947] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> scanning
Dec 14 22:42:08 rabbit wpa_supplicant[551]: wlp3s0: SME: Trying to authenticate with 14:18:2a:40:cf:71 (SSID='DIGI-t6WN' freq=2462 MHz)
Dec 14 22:42:08 rabbit kernel: wlp3s0: authenticate with 14:18:2a:40:cf:71
Dec 14 22:42:08 rabbit kernel: wlp3s0: 80 MHz not supported, disabling VHT
Dec 14 22:42:08 rabbit kernel: wlp3s0: send auth to 14:18:2a:40:cf:71 (try 1/3)
Dec 14 22:42:08 rabbit NetworkManager[32350]: <info>  [1702586528.8066] device (wlp3s0): supplicant interface state: scanning -> authenticating
Dec 14 22:42:08 rabbit NetworkManager[32350]: <info>  [1702586528.8066] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> authenticating
Dec 14 22:42:08 rabbit wpa_supplicant[551]: wlp3s0: Trying to associate with 14:18:2a:40:cf:71 (SSID='DIGI-t6WN' freq=2462 MHz)
Dec 14 22:42:08 rabbit kernel: wlp3s0: authenticated
Dec 14 22:42:08 rabbit NetworkManager[32350]: <info>  [1702586528.8508] device (wlp3s0): supplicant interface state: authenticating -> associating
Dec 14 22:42:08 rabbit NetworkManager[32350]: <info>  [1702586528.8509] device (p2p-dev-wlp3s0): supplicant management interface state: authenticating -> associating
Dec 14 22:42:08 rabbit kernel: wlp3s0: associate with 14:18:2a:40:cf:71 (try 1/3)
Dec 14 22:42:08 rabbit kernel: wlp3s0: RX AssocResp from 14:18:2a:40:cf:71 (capab=0x1411 status=0 aid=9)
Dec 14 22:42:08 rabbit wpa_supplicant[551]: wlp3s0: Associated with 14:18:2a:40:cf:71
Dec 14 22:42:08 rabbit wpa_supplicant[551]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dec 14 22:42:08 rabbit kernel: wlp3s0: associated
Dec 14 22:42:08 rabbit NetworkManager[32350]: <info>  [1702586528.8740] device (wlp3s0): supplicant interface state: associating -> 4way_handshake
Dec 14 22:42:08 rabbit NetworkManager[32350]: <info>  [1702586528.8741] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> 4way_handshake
Dec 14 22:42:08 rabbit kernel: wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 14:18:2a:40:cf:71
Dec 14 22:42:13 rabbit kernel: wlp3s0: deauthenticated from 14:18:2a:40:cf:71 (Reason: 2=PREV_AUTH_NOT_VALID)
Dec 14 22:42:13 rabbit kernel: wlp3s0: deauthenticated from 14:18:2a:40:cf:71 (Reason: 2=PREV_AUTH_NOT_VALID)
Dec 14 22:42:13 rabbit wpa_supplicant[551]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=14:18:2a:40:cf:71 reason=2
Dec 14 22:42:13 rabbit wpa_supplicant[551]: wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Dec 14 22:42:13 rabbit wpa_supplicant[551]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="DIGI-t6WN" auth_failures=1 duration=10 reason=WRONG_KEY
Dec 14 22:42:13 rabbit NetworkManager[32350]: <info>  [1702586533.8956] device (wlp3s0): supplicant interface state: 4way_handshake -> disconnected
Dec 14 22:42:13 rabbit NetworkManager[32350]: <info>  [1702586533.8957] device (wlp3s0): Activation: (wifi) disconnected during association, asking for new key
Dec 14 22:42:13 rabbit NetworkManager[32350]: <info>  [1702586533.8957] device (wlp3s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: >
Dec 14 22:42:13 rabbit NetworkManager[32350]: <info>  [1702586533.8960] device (p2p-dev-wlp3s0): supplicant management interface state: 4way_handshake -> disconnected
Dec 14 22:42:13 rabbit NetworkManager[32350]: <warn>  [1702586533.8964] device (wlp3s0): no secrets: No agents were available for this request.
Dec 14 22:42:13 rabbit NetworkManager[32350]: <info>  [1702586533.8964] device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Dec 14 22:42:13 rabbit NetworkManager[32350]: <info>  [1702586533.8968] manager: NetworkManager state is now CONNECTED_LOCAL
Dec 14 22:42:13 rabbit NetworkManager[32350]: <warn>  [1702586533.8970] device (wlp3s0): Activation: failed for connection 'DIGI-t6WN'
Dec 14 22:42:13 rabbit NetworkManager[32350]: <info>  [1702586533.8973] device (wlp3s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Dec 14 22:42:13 rabbit rtkit-daemon[1118]: Supervising 11 threads of 8 processes of 1 users.
Dec 14 22:42:13 rabbit rtkit-daemon[1118]: Supervising 11 threads of 8 processes of 1 users.
Dec 14 22:42:15 rabbit NetworkManager[32350]: <info>  [1702586535.9970] device (wlp3s0): supplicant interface state: disconnected -> inactive
Dec 14 22:42:15 rabbit NetworkManager[32350]: <info>  [1702586535.9971] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> inactive

dmesg:

[328926.585823] wlp3s0: authenticate with 14:18:2a:40:cf:71
[328926.585852] wlp3s0: 80 MHz not supported, disabling VHT
[328926.588815] wlp3s0: send auth to 14:18:2a:40:cf:71 (try 1/3)
[328926.632114] wlp3s0: authenticated
[328926.636440] wlp3s0: associate with 14:18:2a:40:cf:71 (try 1/3)
[328926.643930] wlp3s0: RX AssocResp from 14:18:2a:40:cf:71 (capab=0x1411 status=0 aid=9)
[328926.650194] wlp3s0: associated
[328926.670815] wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 14:18:2a:40:cf:71
[328931.653487] wlp3s0: deauthenticated from 14:18:2a:40:cf:71 (Reason: 2=PREV_AUTH_NOT_VALID)

seth · 2023-12-14 21:44:32

Please don't copypaste out of the pager it trunc>

Dec 14 22:42:13 rabbit kernel: wlp3s0: deauthenticated from 14:18:2a:40:cf:71 (Reason: 2=PREV_AUTH_NOT_VALID)
Dec 14 22:42:13 rabbit kernel: wlp3s0: deauthenticated from 14:18:2a:40:cf:71 (Reason: 2=PREV_AUTH_NOT_VALID)
Dec 14 22:42:13 rabbit wpa_supplicant[551]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=14:18:2a:40:cf:71 reason=2
Dec 14 22:42:13 rabbit wpa_supplicant[551]: wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Dec 14 22:42:13 rabbit wpa_supplicant[551]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="DIGI-t6WN" auth_failures=1 duration=10 reason=WRONG_KEY

The wifi AP simply doesn't like your password?

bancsorin10 · 2023-12-14 22:44:58

I've tried resetting the connection and remaking it several times, in the end it worked connecting. What I usually see is I run nmcli connect with the `-a` flag to ask for the password, I enter the password, it asks for it again, and this repeats like 5 times then it fails or times out (usually if the password is incorrect the connection will fail on the first try, so it seemed like the handshake failed / was reset multiple times before failing).

At the moment I'm trying to replicate the failing again, because I don't know what changed; not ruling out the fact that the connection will work only temporarily again

Last edited by bancsorin10 (2023-12-14 22:47:25)

seth · 2023-12-15 08:23:58

Ftr. the wired connection on over r8169 doesn't work at all?
And "it is just this new router that is behaving"?
Firmware update? Does the router keep logs?

bancsorin10 · 2023-12-15 12:09:05

for the wired connection I've seen 3 states it can be in; the router either straight up blocks the connection, or makes the connection then it seems there are some packages that are dropped coming from me by the router itself kicking me out afterwards, or I get connected for a short while then if other devices enter the network I might get kicked out (?); and yes it is only this router that seems to be behaving like this;

I'll try looking for some firmware updates;
I don't think the router keeps any logs, at first sight the only thing I saw was a log of the number of packets received then dropped (that's how I know in some cases I get connected for a very short while);
When I get disconnected after the first few packets, I can no longer reconnect even if I switch the interface where I connect to. (I've looked through the settings, there weren't any macs getting blocked, no firewall present, I somehow get shadow blocked? getting the wire in and out of the laptop doesn't do anything, I don't know what is happening there for the router to no longer receive any packets, instead of receiving then dropping; I don't remember if resetting the interface worked or I had to wait a certain amount of time - I'll be checking this aswell)

seth · 2023-12-15 15:00:28

What's the specifc routers brand/vendol/model/version?

bancsorin10 · 2023-12-15 15:34:47

router: FiberHome model SR1041Y -- installed by the ISP

seth · 2023-12-15 21:36:19

for the wired connection I've seen 3 states it can be in; the router either straight up blocks the connection, or makes the connection then it seems there are some packages that are dropped coming from me by the router itself kicking me out afterwards, or I get connected for a short while then if other devices enter the network I might get kicked out (?)

I don't think we've seen any journal for that condition? (Only for the wifi-failures) have we?

Unfortunately that router model doesn't seem very well (publically) documented, the only manual I could find was "plug the cables into the slots" - thanks for the absolute pro-tip

Arch Linux

#1 2023-11-17 07:51:24

r8169: Link is down

#2 2023-11-17 16:45:33

Re: r8169: Link is down

#3 2023-11-23 20:12:24

Re: r8169: Link is down

#4 2023-11-24 16:13:01

Re: r8169: Link is down

#5 2023-11-25 13:58:45

Re: r8169: Link is down

#6 2023-11-27 16:38:20

Re: r8169: Link is down

#7 2023-12-07 21:09:10

Re: r8169: Link is down

#8 2023-12-07 21:21:15

Re: r8169: Link is down

#9 2023-12-07 21:27:39

Re: r8169: Link is down

#10 2023-12-07 21:29:56

Re: r8169: Link is down

#11 2023-12-07 21:45:14

Re: r8169: Link is down

#12 2023-12-07 22:05:03

Re: r8169: Link is down

#13 2023-12-08 08:43:47

Re: r8169: Link is down

#14 2023-12-12 21:04:16

Re: r8169: Link is down

#15 2023-12-12 21:39:23

Re: r8169: Link is down

#16 2023-12-14 20:53:57

Re: r8169: Link is down

#17 2023-12-14 21:44:32

Re: r8169: Link is down

#18 2023-12-14 22:44:58

Re: r8169: Link is down

#19 2023-12-15 08:23:58

Re: r8169: Link is down

#20 2023-12-15 12:09:05

Re: r8169: Link is down

#21 2023-12-15 15:00:28

Re: r8169: Link is down

#22 2023-12-15 15:34:47

Re: r8169: Link is down

#23 2023-12-15 21:36:19

Re: r8169: Link is down

Board footer