You are not logged in.
Hello everyone.
Apologies if I miss anything important out as it's my first time needing to make a post about a problem I'm having with my system.
To preface this, I use a wired connection to my router and I have my network configured using systemd-networkd. I've never had a problem with this setup before, but I'm now on a new machine and I've noticed that I've been losing connection to the internet at seemingly random intervals. I've inspected the output of systemctl status systemd-networkd and noticed the following:
Feb 18 14:55:36 hostname systemd-networkd[422]: eno1: Lost carrier
Feb 18 14:55:37 hostname systemd-networkd[422]: eno1: DHCPv6 lease lost
Feb 18 14:55:39 hostname systemd-networkd[422]: eno1: Gained carrier
Feb 18 14:55:40 hostname systemd-networkd[422]: eno1: Lost carrier
Feb 18 14:55:40 hostname systemd-networkd[422]: eno1: DHCPv6 lease lost
Feb 18 14:55:50 hostname systemd-networkd[422]: eno1: Gained carrier
Feb 18 14:55:51 hostname systemd-networkd[422]: eno1: Lost carrier
Feb 18 14:55:51 hostname systemd-networkd[422]: eno1: DHCPv6 lease lost
Feb 18 14:55:54 hostname systemd-networkd[422]: eno1: Gained carrier
Feb 18 14:55:58 hostname systemd-networkd[422]: eno1: DHCPv4 address 192.168.1.249/24, gateway 192.168.1.1 acquired from 192.168.1.1
This most recent episode occurred after boot, shortly before I logged in. However, I've noticed that this seems to happen more regularly during certain activities, such as playing Overwatch 2 under Steam/Proton - although, this might just be because I'm using an internet-based application and therefore noticing the problem more.
I'm fairly clueless when it comes to anything networking-related, but I've searched around and found a similar problem described in this GitHub issue. From my understanding, the eventual solution to the problem appeared to be related to using the IgnoreCarrierLoss option, but I believe this only helps in a wireless context.
I really have no idea how to even start solving this problem, so I'm hoping somebody here will be able to shed some light on the situation for me. Here's the output of journalctl --boot=0 (with the problem described occurring at the end of the output), the output of lspci, and my network configuration file.
Thanks :-)
Offline
Your 2.5 Gigabit adapter negotiates a 1 Gigabit connection with the Ethernet port on your router and loses the connection as soon as there is some kind of data transfer.
You may try:
- Changing the cable
- Changing the port on the router
- Limiting the I225-V to 1 Gigabit (or - just for testing - to 100 MBit half-duplex)
- Insert a small Gigabit switch between PC and router
Offline
I've been using a spare TP-Link Gigabit switch between my router and PC for a few hours now, and it appears to have fixed the problem, so thank you! Not noticing any delay in getting a connection to the internet anymore, either.
As for achieving this same result without the need for a switch, I don't think I'd benefit from changing the cable as it should already support 2.5Gb, and changing the router is out of the question. How would I go about limiting the I225-V to 1 Gigabit? Thanks again for your help! :-)
Offline
https://man.archlinux.org/man/extra/eth … htool.8.en
"autoneg off speed 1000" or "advertise 0x020"
Offline
This seems to be exactly what I'm looking for, thanks! Is there a recommended way of making this a persistent change? Most suggestions are to add the command to rc.local, but that advice seems a little outdated.
Offline
You can use a systemd.link unit with the Advertise-Key: https://man.archlinux.org/man/core/syst … ON_OPTIONS
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
I've configured my systemd.link unit with the following:
[Link]
Advertise=1000baset-full
I've verified that this configuration is being applied using ethtool. However, the problem is still continuing. Have I missed something, or is there anything else I can try?
Offline
Limiting the I225-V … just for testing - to 100 MBit half-duplex
Does ethtool suggest that you're not advertising more?
Offline
I've only tried limiting the speed to 1 gigabit so far, and ethtool reports the following:
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
MDI-X: off (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
I'll try the earlier 100MBit half-duplex suggestion for some time now and see if notice the issue persisting. In the meantime, the gigabit switch suggestion has been working flawlessly.
Offline