You are not logged in.
Hi, Every time i try to game in arch after a while my wired connection turns off, i can just connect to it again but in game i need to close and open it again. This happens with the NM + iwd setup, NM only and iwd + systemd_networkd. This is the "find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f "output:
bluetooth.service | bluetooth.target.wants
dbus-org.bluez.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service | system
getty@tty1.service | getty.target.wants
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
nvidia-hibernate.service | systemd-hibernate.service.wants
nvidia-resume.service | systemd-hibernate.service.wants
nvidia-resume.service | systemd-suspend.service.wants
nvidia-resume.service | systemd-suspend-then-hibernate.service.wants
nvidia-suspend.service | systemd-suspend.service.wants
p11-kit-server.socket | sockets.target.wants
pipewire-pulse.socket | sockets.target.wants
pipewire-session-manager.service | user
pipewire.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
systemd-resolved.service | sysinit.target.wants
systemd-userdbd.socket | sockets.target.wants
tlp.service | multi-user.target.wants
wireplumber.service | pipewire.service.wants
xdg-user-dirs-update.service | default.target.wants
Last edited by tesima (2025-06-17 00:37:02)
Offline
Please use "code" tags for the find output.
Why using iwd (a wireless daemon) with a wired/Ethernet connection?
Offline
Sorry for the missing tag, and I was using iwd only for wireless connection with nm or networkd for the wired connection. And the wired connection disconnects and connects again outside games too.
Offline
What does NetworkManager say when the connection is dropped?
journalctl -b | grep NetworkManager
Offline
Jun 16 20:10:45 Falcone NetworkManager[1121]: <info> [1750115445.5675] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 16 20:10:47 Falcone NetworkManager[1121]: <info> [1750115447.3656] dhcp4 (enp2s0): state changed new lease, address=192.168.1.106, acd pending
Jun 16 20:10:47 Falcone NetworkManager[1121]: <info> [1750115447.5204] dhcp4 (enp2s0): state changed new lease, address=192.168.1.106
Jun 16 20:10:47 Falcone NetworkManager[1121]: <info> [1750115447.5314] device (enp2s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jun 16 20:10:47 Falcone NetworkManager[1121]: <info> [1750115447.5322] device (enp2s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jun 16 20:10:47 Falcone NetworkManager[1121]: <info> [1750115447.5323] device (enp2s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jun 16 20:10:47 Falcone NetworkManager[1121]: <info> [1750115447.5324] device (enp2s0): Activation: successful, device activated.
Jun 16 20:10:47 Falcone NetworkManager[1121]: <info> [1750115447.5326] manager: startup complete
Jun 16 20:10:48 Falcone NetworkManager[1121]: <info> [1750115448.0097] policy: set 'Wired connection 1' (enp2s0) as default for IPv4 routing and DNS
Jun 16 20:10:49 Falcone NetworkManager[1121]: <info> [1750115449.6075] device (enp2s0): conflict detected for IP address 192.168.1.106 with host D0:39:57:28:64:F3
Jun 16 20:21:08 Falcone NetworkManager[1121]: <info> [1750116068.0422] manager: NetworkManager state is now CONNECTED_SITE
Jun 16 20:21:08 Falcone NetworkManager[1121]: <info> [1750116068.0424] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 16 20:21:08 Falcone NetworkManager[1121]: <info> [1750116068.0425] manager: NetworkManager state is now CONNECTED_SITE
Jun 16 20:21:08 Falcone NetworkManager[1121]: <info> [1750116068.0425] policy: set 'My_Wifi_name' (wlan0) as default for IPv4 routing and DNS
Offline
There is another device in your network claiming the address "192.168.1.106" - with a MAC address belonging to "LiteOn Technology".
Resolve this IP conflict.
Offline
Thank you. I disabled my dhcp and made a static ip configuration and it solved the issues with my wired connection.
Offline
Doing that on other system is what caused this in the first place. You need to figure out how you want your overall network set up. Don't run a DHCP server that's handing out the same IPs as you have static for a start.
Last edited by Scimmia (2025-06-18 13:22:50)
Offline