Skip to main content
Topic: Wired connection keeps deactiviting after waking up from sleep (Read 1107 times) previous topic - next topic
0 Members and 5 Guests are viewing this topic.

Wired connection keeps deactiviting after waking up from sleep

I have another Windows laptop which can connect to wired Ethernet normally. On my Artix laptop, wirless connection works normally. A recurring issue with wired connection is that after the system starts or wakes up from sleep, wired connection often, but not always, keeps deactivting. This issue can always be immediately solved by restarting the router. But that's a big hassle, as opposed to the appropriate solution at one go.

This problem occurred before plasma set Wayland as the default DE. Since I found Wayland to be buggy, I switched back to X11. So it should have nothing to do with Wayland.

My ini is runit and I used NetworkManager. And below is the output of the command ip a:

Code: [Select]
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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 proto kernel_lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 54:e1:ad:97:61:1d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
       valid_lft 604471sec preferred_lft 604471sec
    inet6 2409:8a3c:4c7:e680:3183:2543:8b5:5789/64 scope global dynamic noprefixroute
       valid_lft 259189sec preferred_lft 172789sec
    inet6 fe80::4bcf:cbef:e9f4:1aec/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether f2:ac:cb:c8:3b:68 brd ff:ff:ff:ff:ff:ff permaddr f8:28:19:c2:f0:83

Any thoughts or suggestion of diagnosing command will be gratefully aknowledged.

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #1
seeing the state your wlan0 interface is in, it is not powered.

try
 
$ sudo ip link set wlan0 up

it should re power your interface.

If you want to diagnose the issue, I advise you to check Networkmanager logs, maybe it can help you.


Re: Wired connection keeps deactiviting after waking up from sleep

Reply #2
sudo ip link set wlan0 up doesn't work because RTNETLINK answers: Operation not possible due to RF-kill

Where can I check  out  NetworkManager logs?

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #3
Oh, so it's rfkill... In that case, you can use the command `rfkill` to list and unblock your network devices

This is how the command should be used. It can be different in your installation tough:

Code: [Select]
 $ rfkill
ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan        blocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0                blocked unblocked
 3 bluetooth hci0              unblocked unblocked

 $ sudo ip link set wlan0 up
RTNETLINK answers: Operation not possible due to RF-kill

 $ rfkill unblock 0 2
 $ rfkill
 ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan      unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0              unblocked unblocked
 3 bluetooth hci0              unblocked unblocked


In most service with runit, log aren't configured, and that the case with Networkmanager.
So first, you have to configure the log service.

Code: [Select]
$ sudo touch /etc/runit/sv/Networkmanager/log/run
$ sudo chmod +x /etc/runit/sv/Networkmanager/log/run

After that add this code to the file

Code: [Select]
#!/bin/sh
exec 2>&1; set -e

[ -d /var/log/networkmanager ] || install -dm 755 /var/log/networkmanager

exec svlogd -tt /var/log/networkmanager

And restart the log service

Code: [Select]
$ sudo sv restart Networkmanager/log

After that, you should be able to find Networkmanager's log in the new /var/log/networkmanager folder.


Re: Wired connection keeps deactiviting after waking up from sleep

Reply #4
Wow, what a coincidence! You're also using a Legion/Ideapad

Before unblocking:
Code: [Select]
ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan        blocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0                blocked unblocked
 4 bluetooth hci0              unblocked unblocked

After unblocking:
Code: [Select]
ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan      unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0              unblocked unblocked
 4 bluetooth hci0              unblocked unblocked

Why devices 0 and 2 got blocked in the first palce?

sudo sv restart Networkmanager/log doesn't work because warning: NetworkManager/log: unable to open supervise/ok: file does not exist

The contents of NetworkManager are: log  run  supervise




 

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #5
Quote
sudo sv restart Networkmanager/log doesn't work because warning: NetworkManager/log: unable to open supervise/ok: file does not exist

Indeed, it seams I overestimated runit.

Do instead

Code: [Select]
sudo sv exit Networkmanager

That will generate Networkmanager/log/supervise, and start the log service. After that, if you do

Code: [Select]
$ sudo sv status Networkmanager

you should see the service and the log service up.

I've just check, and there is another thing to change in order to have the logs.

in /etc/runit/sv/Networkmanager/run, change the line
Code: [Select]
exec NetworkManager -n > /dev/null 2>&1

to

Code: [Select]
exec NetworkManager -n -d 2>&1

Now, try
Code: [Select]
cat /var/log/networkmanager/current

you should be able to see the logs.


Re: Wired connection keeps deactiviting after waking up from sleep

Reply #7
It can be.

Personnaly I don't use Networkmanager. iwd plus dhcpcd is from far enough for my needs.

you should indeed try to downgrade elogind to see if it solve the bug.

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #8
Wow, what a coincidence! You're also using a Legion/Ideapad

Before unblocking:
Code: [Select]
ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan        blocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0                blocked unblocked
 4 bluetooth hci0              unblocked unblocked

After unblocking:
Code: [Select]
ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan      unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0              unblocked unblocked
 4 bluetooth hci0              unblocked unblocked

Why devices 0 and 2 got blocked in the first palce?

sudo sv restart Networkmanager/log doesn't work because warning: NetworkManager/log: unable to open supervise/ok: file does not exist

The contents of NetworkManager are: log  run  supervise





Now after waking up from sleep, wireless connection cannot be enabled either. I've to reboot Artix and restart the router to activate wired connection

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #9
Quote
sudo sv restart Networkmanager/log doesn't work because warning: NetworkManager/log: unable to open supervise/ok: file does not exist

Indeed, it seams I overestimated runit.

Do instead

Code: [Select]
sudo sv exit Networkmanager

That will generate Networkmanager/log/supervise, and start the log service. After that, if you do

Code: [Select]
$ sudo sv status Networkmanager

you should see the service and the log service up.

I've just check, and there is another thing to change in order to have the logs.

in /etc/runit/sv/Networkmanager/run, change the line
Code: [Select]
exec NetworkManager -n > /dev/null 2>&1

to

Code: [Select]
exec NetworkManager -n -d 2>&1

Now, try
Code: [Select]
cat /var/log/networkmanager/current

you should be able to see the logs.


Below is the lastest log:
Code: [Select]
2024-04-22_12:11:53.59998 <info>  [1713787913.5993] NetworkManager (version 1.46.0-2) is starting... (boot:0629d5f2-8e9b-4871-8e74-82e7087b150e)
2024-04-22_12:11:53.60009 <info>  [1713787913.6000] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
2024-04-22_12:11:53.61113 <info>  [1713787913.6110] manager[0x5e60852feea0]: monitoring kernel firmware directory '/lib/firmware'.
2024-04-22_12:11:53.61331 <info>  [1713787913.6132] hostname: hostname: couldn't get property from hostnamed
2024-04-22_12:11:53.61358 <info>  [1713787913.6134] hostname: static hostname changed from (none) to "raylenovo"
2024-04-22_12:11:53.61423 <info>  [1713787913.6141] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
2024-04-22_12:11:53.61764 <info>  [1713787913.6176] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci)
2024-04-22_12:11:53.61808 <info>  [1713787913.6180] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/rfkill/rfkill0) (platform driver ideapad_acpi)
2024-04-22_12:11:53.62086 <info>  [1713787913.6208] manager[0x5e60852feea0]: rfkill: Wi-Fi hardware radio set disabled
2024-04-22_12:11:53.62092 <info>  [1713787913.6209] manager[0x5e60852feea0]: rfkill: WWAN hardware radio set enabled
2024-04-22_12:11:53.65926 <info>  [1713787913.6591] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-team.so)
2024-04-22_12:11:53.66370 <info>  [1713787913.6636] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-wwan.so)
2024-04-22_12:11:53.66470 <info>  [1713787913.6646] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-ovs.so)
2024-04-22_12:11:53.66536 <info>  [1713787913.6652] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
2024-04-22_12:11:53.66664 <info>  [1713787913.6665] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-wifi.so)
2024-04-22_12:11:53.66725 <info>  [1713787913.6671] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-adsl.so)
2024-04-22_12:11:53.66764 <info>  [1713787913.6675] manager: rfkill: Wi-Fi disabled by radio killswitch; disabled by state file
2024-04-22_12:11:53.66770 <info>  [1713787913.6676] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
2024-04-22_12:11:53.66784 <info>  [1713787913.6677] manager: Networking is enabled by state file
2024-04-22_12:11:53.66831 <info>  [1713787913.6682] settings: Loaded settings plugin: keyfile (internal)
2024-04-22_12:11:53.67234 <info>  [1713787913.6723] dhcp: init: Using DHCP client 'internal'
2024-04-22_12:11:53.67275 <info>  [1713787913.6726] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
2024-04-22_12:11:53.67419 <info>  [1713787913.6741] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
2024-04-22_12:11:53.67509 <info>  [1713787913.6750] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
2024-04-22_12:11:53.67601 <info>  [1713787913.6759] device (lo): Activation: starting connection 'lo' (f24e1271-2856-48b0-9bd9-b2b66a6afa7b)
2024-04-22_12:11:53.67709 <info>  [1713787913.6770] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
2024-04-22_12:11:53.67738 <info>  [1713787913.6773] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
2024-04-22_12:11:53.88598 <warn>  [1713787913.8858] device (eth0): connectivity: "/proc/sys/net/ipv4/conf/eth0/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
2024-04-22_12:11:53.88663 <info>  [1713787913.8865] device (wlan0): driver supports Access Point (AP) mode
2024-04-22_12:11:53.88751 <info>  [1713787913.8874] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
2024-04-22_12:11:53.88817 <info>  [1713787913.8880] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
2024-04-22_12:11:53.88903 <info>  [1713787913.8889] device (wlan0): set-hw-addr: set MAC address to 06:5D:6E:99:5F:73 (scanning)
2024-04-22_12:11:53.88937 <warn>  [1713787913.8892] device (wlan0): connectivity: "/proc/sys/net/ipv4/conf/wlan0/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
2024-04-22_12:11:53.89059 <info>  [1713787913.8905] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
2024-04-22_12:11:53.89258 <info>  [1713787913.8925] ovsdb: disconnected from ovsdb
2024-04-22_12:11:53.89277 <info>  [1713787913.8927] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
2024-04-22_12:11:53.89312 <info>  [1713787913.8930] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
2024-04-22_12:11:53.89343 <info>  [1713787913.8933] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
2024-04-22_12:11:53.89429 <info>  [1713787913.8942] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
2024-04-22_12:11:53.89647 <info>  [1713787913.8963] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
2024-04-22_12:11:53.89677 <info>  [1713787913.8966] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
2024-04-22_12:11:53.89735 <info>  [1713787913.8972] device (lo): Activation: successful, device activated.
2024-04-22_12:11:53.98668 <info>  [1713787913.9865] modem-manager: ModemManager not available
2024-04-22_12:11:54.02267 <info>  [1713787914.0226] modem-manager: ModemManager now available
2024-04-22_12:11:59.89030 <info>  [1713787919.8901] manager: startup complete
2024-04-22_12:12:06.52607 <info>  [1713787926.5259] device (eth0): carrier: link connected
2024-04-22_12:12:06.52655 <info>  [1713787926.5264] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:12:06.52744 <info>  [1713787926.5273] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:12:06.52822 <info>  [1713787926.5281] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:12:06.52841 <info>  [1713787926.5283] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:12:06.52885 <info>  [1713787926.5287] manager: NetworkManager state is now CONNECTING
2024-04-22_12:12:06.52928 <info>  [1713787926.5292] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:12:06.53062 <info>  [1713787926.5305] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:12:06.53119 <info>  [1713787926.5311] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-22_12:12:07.71964 <info>  [1713787927.7194] agent-manager: agent[2ea66d67187292d2,:1.16/org.kde.plasma.networkmanagement/1000]: agent registered
2024-04-22_12:12:12.53144 <info>  [1713787932.5313] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:12:12.54790 <info>  [1713787932.5478] dhcp4 (eth0): canceled DHCP transaction
2024-04-22_12:12:12.54795 <info>  [1713787932.5479] dhcp4 (eth0): state changed no lease
2024-04-22_12:12:12.54917 <info>  [1713787932.5490] manager: NetworkManager state is now DISCONNECTED
2024-04-22_12:12:20.20788 <info>  [1713787940.2077] device (eth0): carrier: link connected
2024-04-22_12:12:20.20828 <info>  [1713787940.2081] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:12:20.20922 <info>  [1713787940.2091] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:12:20.20995 <info>  [1713787940.2098] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:12:20.21120 <info>  [1713787940.2100] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:12:20.21123 <info>  [1713787940.2104] manager: NetworkManager state is now CONNECTING
2024-04-22_12:12:20.21123 <info>  [1713787940.2108] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:12:20.21199 <info>  [1713787940.2118] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:12:20.21288 <info>  [1713787940.2127] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-22_12:12:26.21227 <info>  [1713787946.2121] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:12:26.23173 <info>  [1713787946.2316] dhcp4 (eth0): canceled DHCP transaction
2024-04-22_12:12:26.23175 <info>  [1713787946.2317] dhcp4 (eth0): state changed no lease
2024-04-22_12:12:26.23295 <info>  [1713787946.2328] manager: NetworkManager state is now DISCONNECTED
2024-04-22_12:12:26.53300 <info>  [1713787946.5328] device (eth0): carrier: link connected
2024-04-22_12:12:26.53354 <info>  [1713787946.5332] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:12:26.53410 <info>  [1713787946.5340] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:12:26.53489 <info>  [1713787946.5347] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:12:26.53507 <info>  [1713787946.5349] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:12:26.53565 <info>  [1713787946.5356] manager: NetworkManager state is now CONNECTING
2024-04-22_12:12:26.53603 <info>  [1713787946.5359] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:12:26.53732 <info>  [1713787946.5367] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:12:26.53748 <info>  [1713787946.5374] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-22_12:12:33.53793 <info>  [1713787953.5378] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:12:33.55459 <info>  [1713787953.5544] dhcp4 (eth0): canceled DHCP transaction
2024-04-22_12:12:33.55461 <info>  [1713787953.5545] dhcp4 (eth0): state changed no lease
2024-04-22_12:12:33.55589 <info>  [1713787953.5557] manager: NetworkManager state is now DISCONNECTED
2024-04-22_12:13:19.94536 <info>  [1713787999.9452] device (eth0): carrier: link connected
2024-04-22_12:13:19.94584 <info>  [1713787999.9456] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:13:19.94666 <info>  [1713787999.9465] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:13:19.94745 <info>  [1713787999.9473] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:13:19.94785 <info>  [1713787999.9474] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:13:19.94885 <info>  [1713787999.9479] manager: NetworkManager state is now CONNECTING
2024-04-22_12:13:19.94887 <info>  [1713787999.9483] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:13:19.94985 <info>  [1713787999.9492] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:13:19.94986 <info>  [1713787999.9497] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-22_12:13:25.95021 <info>  [1713788005.9501] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:13:25.96793 <info>  [1713788005.9678] dhcp4 (eth0): canceled DHCP transaction
2024-04-22_12:13:25.96795 <info>  [1713788005.9679] dhcp4 (eth0): state changed no lease
2024-04-22_12:13:25.96927 <info>  [1713788005.9691] manager: NetworkManager state is now DISCONNECTED
2024-04-22_12:13:33.32112 <info>  [1713788013.3209] device (eth0): carrier: link connected
2024-04-22_12:13:33.32169 <info>  [1713788013.3214] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:13:33.32257 <info>  [1713788013.3225] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:13:33.32337 <info>  [1713788013.3232] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:13:33.32362 <info>  [1713788013.3234] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:13:33.32602 <info>  [1713788013.3239] manager: NetworkManager state is now CONNECTING
2024-04-22_12:13:33.32603 <info>  [1713788013.3244] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:13:33.32604 <info>  [1713788013.3254] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:13:33.32648 <info>  [1713788013.3263] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-22_12:13:39.32642 <info>  [1713788019.3263] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:13:39.34167 <info>  [1713788019.3415] dhcp4 (eth0): canceled DHCP transaction
2024-04-22_12:13:39.34171 <info>  [1713788019.3416] dhcp4 (eth0): state changed no lease
2024-04-22_12:13:39.34330 <info>  [1713788019.3431] manager: NetworkManager state is now DISCONNECTED
2024-04-22_12:13:49.35173 <info>  [1713788029.3516] device (eth0): carrier: link connected
2024-04-22_12:13:49.35239 <info>  [1713788029.3520] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:13:49.35318 <info>  [1713788029.3530] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:13:49.35405 <info>  [1713788029.3538] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:13:49.35411 <info>  [1713788029.3540] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:13:49.35464 <info>  [1713788029.3544] manager: NetworkManager state is now CONNECTING
2024-04-22_12:13:49.35673 <info>  [1713788029.3549] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:13:49.35674 <info>  [1713788029.3556] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:13:49.35674 <info>  [1713788029.3563] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-22_12:13:51.73625 <info>  [1713788031.7361] device (eth0): carrier: link connected
2024-04-22_12:13:58.74299 <info>  [1713788038.7428] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:13:58.75835 <info>  [1713788038.7582] dhcp4 (eth0): canceled DHCP transaction
2024-04-22_12:13:58.75838 <info>  [1713788038.7583] dhcp4 (eth0): state changed no lease
2024-04-22_12:13:58.75976 <info>  [1713788038.7596] manager: NetworkManager state is now DISCONNECTED
2024-04-22_12:14:33.98752 <info>  [1713788073.9873] device (eth0): carrier: link connected
2024-04-22_12:14:33.98823 <info>  [1713788073.9878] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-22_12:14:33.98899 <info>  [1713788073.9888] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:14:33.98971 <info>  [1713788073.9896] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-22_12:14:33.99006 <info>  [1713788073.9898] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:14:33.99034 <info>  [1713788073.9903] manager: NetworkManager state is now CONNECTING
2024-04-22_12:14:33.99087 <info>  [1713788073.9907] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:14:33.99189 <info>  [1713788073.9914] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:14:33.99214 <info>  [1713788073.9920] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-22_12:14:44.67174 <info>  [1713788084.6716] dhcp4 (eth0): state changed new lease, address=192.168.1.3, acd pending
2024-04-22_12:14:44.82457 <info>  [1713788084.8244] dhcp4 (eth0): state changed new lease, address=192.168.1.3
2024-04-22_12:14:44.82511 <info>  [1713788084.8250] policy: set 'New 802-3-ethernet connection' (eth0) as default for IPv4 routing and DNS
2024-04-22_12:14:44.84624 <info>  [1713788084.8450] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:14:44.84876 <info>  [1713788084.8485] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:14:44.84909 <info>  [1713788084.8490] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
2024-04-22_12:14:44.84977 <info>  [1713788084.8494] manager: NetworkManager state is now CONNECTED_SITE
2024-04-22_12:14:44.84990 <info>  [1713788084.8497] device (eth0): Activation: successful, device activated.
2024-04-22_12:14:52.16739 <info>  [1713788092.1672] manager: NetworkManager state is now CONNECTED_GLOBAL
2024-04-22_12:14:54.01202 <info>  [1713788094.0119] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-22_12:14:54.01317 <info>  [1713788094.0128] policy: set 'New 802-3-ethernet connection' (eth0) as default for IPv6 routing and DNS
2024-04-22_12:14:55.00371 <info>  [1713788095.0035] dhcp6 (eth0): state changed new lease

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #10
 
It can be.

Personnaly I don't use Networkmanager. iwd plus dhcpcd is from far enough for my needs.

you should indeed try to downgrade elogind to see if it solve the bug.
I cannot find enough tutorials to switch to and use iwd and dhcpcd. What's the viable solution if I'm going to ditch NetworkManager and use some other package instead?

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #11
This thread is a bit confusing to me. I'm left unsure whether you want to use the wifi or the wired connection? Maybe both?
But I'll add this.
If the only way to get the the connections back after they drop is restarting the router then you need to consider the possibility that the issue is with the router.

Maybe learn to bring up both wired and wifi connections manually on the commandline, without any dhcp. I'm not sugessting to do that all the time but it's useful to debug situations like you are encountering. You need to disable, or at least stop, any network managers before you do that though.

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #12
I want to use wired connection.

I don't think the issue lies in the router since I vaguely recall that the same issue occurred in another residence.

Code: [Select]
2024-04-23_00:19:57.23050 <info>  [1713831597.2291] caught SIGTERM, shutting down normally.
2024-04-23_00:19:57.43456 <info>  [1713831597.4344] device (wlan0): state change: unavailable -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed')
2024-04-23_00:19:57.43483 <info>  [1713831597.4347] device (wlan0): set-hw-addr: reset MAC address to F8:28:19:C2:F0:83 (unmanage)
2024-04-23_00:19:57.45126 <info>  [1713831597.4511] exiting (success)
2024-04-23_10:42:06.94262 <info>  [1713868926.9420] NetworkManager (version 1.46.0-2) is starting... (boot:c7c1b80d-22ca-4f6b-a8eb-9dffc9230071)
2024-04-23_10:42:06.94301 <info>  [1713868926.9426] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
2024-04-23_10:42:06.95381 <info>  [1713868926.9537] manager[0x59ad2c2f4fa0]: monitoring kernel firmware directory '/lib/firmware'.
2024-04-23_10:42:06.95588 <info>  [1713868926.9558] hostname: hostname: couldn't get property from hostnamed
2024-04-23_10:42:06.95620 <info>  [1713868926.9561] hostname: static hostname changed from (none) to "raylenovo"
2024-04-23_10:42:06.95683 <info>  [1713868926.9567] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
2024-04-23_10:42:06.96038 <info>  [1713868926.9603] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci)
2024-04-23_10:42:06.96079 <info>  [1713868926.9607] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/rfkill/rfkill0) (platform driver ideapad_acpi)
2024-04-23_10:42:06.96346 <info>  [1713868926.9634] manager[0x59ad2c2f4fa0]: rfkill: Wi-Fi hardware radio set disabled
2024-04-23_10:42:06.96349 <info>  [1713868926.9634] manager[0x59ad2c2f4fa0]: rfkill: WWAN hardware radio set enabled
2024-04-23_10:42:07.00064 <info>  [1713868927.0005] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-team.so)
2024-04-23_10:42:07.00577 <info>  [1713868927.0056] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-wwan.so)
2024-04-23_10:42:07.00672 <info>  [1713868927.0066] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-ovs.so)
2024-04-23_10:42:07.00740 <info>  [1713868927.0073] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
2024-04-23_10:42:07.00867 <info>  [1713868927.0086] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-wifi.so)
2024-04-23_10:42:07.00935 <info>  [1713868927.0092] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-adsl.so)
2024-04-23_10:42:07.00971 <info>  [1713868927.0096] manager: rfkill: Wi-Fi disabled by radio killswitch; disabled by state file
2024-04-23_10:42:07.00990 <info>  [1713868927.0097] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
2024-04-23_10:42:07.00991 <info>  [1713868927.0098] manager: Networking is enabled by state file
2024-04-23_10:42:07.01044 <info>  [1713868927.0103] settings: Loaded settings plugin: keyfile (internal)
2024-04-23_10:42:07.01482 <info>  [1713868927.0147] dhcp: init: Using DHCP client 'internal'
2024-04-23_10:42:07.01522 <info>  [1713868927.0151] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
2024-04-23_10:42:07.01668 <info>  [1713868927.0166] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
2024-04-23_10:42:07.01954 <info>  [1713868927.0174] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
2024-04-23_10:42:07.01956 <info>  [1713868927.0186] device (lo): Activation: starting connection 'lo' (2328d744-7535-4e42-9776-e8854f6fcf6e)
2024-04-23_10:42:07.01990 <info>  [1713868927.0198] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
2024-04-23_10:42:07.02026 <info>  [1713868927.0202] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
2024-04-23_10:42:07.19211 <warn>  [1713868927.1920] device (eth0): connectivity: "/proc/sys/net/ipv4/conf/eth0/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
2024-04-23_10:42:07.19348 <info>  [1713868927.1926] device (wlan0): driver supports Access Point (AP) mode
2024-04-23_10:42:07.19349 <info>  [1713868927.1933] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
2024-04-23_10:42:07.19391 <info>  [1713868927.1937] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
2024-04-23_10:42:07.19470 <info>  [1713868927.1946] device (wlan0): set-hw-addr: set MAC address to 2A:06:48:7B:71:DF (scanning)
2024-04-23_10:42:07.19502 <warn>  [1713868927.1949] device (wlan0): connectivity: "/proc/sys/net/ipv4/conf/wlan0/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
2024-04-23_10:42:07.19646 <info>  [1713868927.1964] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
2024-04-23_10:42:07.19812 <info>  [1713868927.1980] ovsdb: disconnected from ovsdb
2024-04-23_10:42:07.19826 <info>  [1713868927.1982] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
2024-04-23_10:42:07.19863 <info>  [1713868927.1984] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
2024-04-23_10:42:07.19876 <info>  [1713868927.1987] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
2024-04-23_10:42:07.19946 <info>  [1713868927.1993] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
2024-04-23_10:42:07.20170 <info>  [1713868927.2016] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
2024-04-23_10:42:07.20186 <info>  [1713868927.2018] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
2024-04-23_10:42:07.20226 <info>  [1713868927.2022] device (lo): Activation: successful, device activated.
2024-04-23_10:42:07.28278 <info>  [1713868927.2826] modem-manager: ModemManager not available
2024-04-23_10:42:07.33296 <info>  [1713868927.3329] modem-manager: ModemManager now available
2024-04-23_10:42:13.19661 <info>  [1713868933.1964] manager: startup complete
2024-04-23_10:42:22.57735 <info>  [1713868942.5772] agent-manager: agent[0aabad2477dc48d5,:1.30/org.kde.plasma.networkmanagement/1000]: agent registered
2024-04-23_11:16:37.86686 <info>  [1713870997.8665] manager: sleep: sleep requested (sleeping: no  enabled: yes)
2024-04-23_11:16:37.86718 <info>  [1713870997.8670] device (eth0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
2024-04-23_11:16:37.87579 <info>  [1713870997.8757] device (wlan0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
2024-04-23_11:16:37.87730 <info>  [1713870997.8762] device (wlan0): set-hw-addr: reset MAC address to F8:28:19:C2:F0:83 (unmanage)
2024-04-23_11:16:37.87732 <info>  [1713870997.8768] manager: NetworkManager state is now ASLEEP
2024-04-23_11:59:38.73568 <info>  [1713873578.7343] caught SIGTERM, shutting down normally.
2024-04-23_11:59:38.76507 <info>  [1713873578.7646] exiting (success)
2024-04-23_12:00:00.69406 <info>  [1713873600.6934] NetworkManager (version 1.46.0-2) is starting... (boot:ba1c4d0e-dba6-4ea7-9748-2c571a24c8d1)
2024-04-23_12:00:00.69432 <info>  [1713873600.6940] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
2024-04-23_12:00:00.70570 <info>  [1713873600.7055] manager[0x572dafe85f50]: monitoring kernel firmware directory '/lib/firmware'.
2024-04-23_12:00:00.70781 <info>  [1713873600.7077] hostname: hostname: couldn't get property from hostnamed
2024-04-23_12:00:00.70812 <info>  [1713873600.7080] hostname: static hostname changed from (none) to "raylenovo"
2024-04-23_12:00:00.70883 <info>  [1713873600.7087] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
2024-04-23_12:00:00.71233 <info>  [1713873600.7122] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci)
2024-04-23_12:00:00.71273 <info>  [1713873600.7127] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/rfkill/rfkill0) (platform driver ideapad_acpi)
2024-04-23_12:00:00.71573 <info>  [1713873600.7156] manager[0x572dafe85f50]: rfkill: Wi-Fi hardware radio set disabled
2024-04-23_12:00:00.71576 <info>  [1713873600.7157] manager[0x572dafe85f50]: rfkill: WWAN hardware radio set enabled
2024-04-23_12:00:00.75400 <info>  [1713873600.7538] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-team.so)
2024-04-23_12:00:00.75852 <info>  [1713873600.7584] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-wwan.so)
2024-04-23_12:00:00.75954 <info>  [1713873600.7594] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-ovs.so)
2024-04-23_12:00:00.76040 <info>  [1713873600.7603] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
2024-04-23_12:00:00.76178 <info>  [1713873600.7617] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-wifi.so)
2024-04-23_12:00:00.76241 <info>  [1713873600.7623] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-adsl.so)
2024-04-23_12:00:00.76280 <info>  [1713873600.7627] manager: rfkill: Wi-Fi disabled by radio killswitch; disabled by state file
2024-04-23_12:00:00.76292 <info>  [1713873600.7628] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
2024-04-23_12:00:00.76296 <info>  [1713873600.7629] manager: Networking is enabled by state file
2024-04-23_12:00:00.76344 <info>  [1713873600.7633] settings: Loaded settings plugin: keyfile (internal)
2024-04-23_12:00:00.76770 <info>  [1713873600.7676] dhcp: init: Using DHCP client 'internal'
2024-04-23_12:00:00.76988 <info>  [1713873600.7679] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
2024-04-23_12:00:00.76990 <info>  [1713873600.7694] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
2024-04-23_12:00:00.77208 <info>  [1713873600.7701] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
2024-04-23_12:00:00.77209 <info>  [1713873600.7710] device (lo): Activation: starting connection 'lo' (caf0f784-e9be-4cf6-928c-d7325f012141)
2024-04-23_12:00:00.77225 <info>  [1713873600.7721] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
2024-04-23_12:00:00.77322 <info>  [1713873600.7725] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
2024-04-23_12:00:00.98943 <warn>  [1713873600.9893] device (eth0): connectivity: "/proc/sys/net/ipv4/conf/eth0/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
2024-04-23_12:00:00.98997 <info>  [1713873600.9899] device (wlan0): driver supports Access Point (AP) mode
2024-04-23_12:00:00.99079 <info>  [1713873600.9907] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
2024-04-23_12:00:00.99118 <info>  [1713873600.9910] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
2024-04-23_12:00:00.99200 <info>  [1713873600.9919] device (wlan0): set-hw-addr: set MAC address to 02:A4:34:FB:95:AA (scanning)
2024-04-23_12:00:00.99230 <warn>  [1713873600.9922] device (wlan0): connectivity: "/proc/sys/net/ipv4/conf/wlan0/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
2024-04-23_12:00:00.99356 <info>  [1713873600.9934] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
2024-04-23_12:00:00.99543 <info>  [1713873600.9953] ovsdb: disconnected from ovsdb
2024-04-23_12:00:00.99560 <info>  [1713873600.9955] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
2024-04-23_12:00:00.99590 <info>  [1713873600.9958] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
2024-04-23_12:00:00.99613 <info>  [1713873600.9961] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
2024-04-23_12:00:00.99693 <info>  [1713873600.9968] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
2024-04-23_12:00:00.99957 <info>  [1713873600.9994] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
2024-04-23_12:00:00.99986 <info>  [1713873600.9997] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
2024-04-23_12:00:01.00039 <info>  [1713873601.0003] device (lo): Activation: successful, device activated.
2024-04-23_12:00:01.10307 <info>  [1713873601.1029] modem-manager: ModemManager not available
2024-04-23_12:00:01.15735 <info>  [1713873601.1573] modem-manager: ModemManager now available
2024-04-23_12:00:06.99396 <info>  [1713873606.9938] manager: startup complete
2024-04-23_12:00:13.74758 <info>  [1713873613.7474] device (eth0): carrier: link connected
2024-04-23_12:00:13.74808 <info>  [1713873613.7479] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-23_12:00:13.74902 <info>  [1713873613.7489] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-23_12:00:13.74974 <info>  [1713873613.7496] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-23_12:00:13.74993 <info>  [1713873613.7498] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:00:13.75035 <info>  [1713873613.7502] manager: NetworkManager state is now CONNECTING
2024-04-23_12:00:13.75085 <info>  [1713873613.7507] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:00:13.75205 <info>  [1713873613.7519] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:00:13.75267 <info>  [1713873613.7526] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-23_12:00:16.96735 <info>  [1713873616.9672] agent-manager: agent[da50d2fbd10dd483,:1.16/org.kde.plasma.networkmanagement/1000]: agent registered
2024-04-23_12:00:19.75258 <info>  [1713873619.7525] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-23_12:00:19.76529 <info>  [1713873619.7652] dhcp4 (eth0): canceled DHCP transaction
2024-04-23_12:00:19.76531 <info>  [1713873619.7652] dhcp4 (eth0): state changed no lease
2024-04-23_12:00:19.76631 <info>  [1713873619.7662] manager: NetworkManager state is now DISCONNECTED
2024-04-23_12:00:27.31210 <info>  [1713873627.3119] device (eth0): carrier: link connected
2024-04-23_12:00:27.31274 <info>  [1713873627.3124] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-23_12:00:27.31373 <info>  [1713873627.3134] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-23_12:00:27.31432 <info>  [1713873627.3142] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-23_12:00:27.31462 <info>  [1713873627.3144] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:00:27.31496 <info>  [1713873627.3149] manager: NetworkManager state is now CONNECTING
2024-04-23_12:00:27.31545 <info>  [1713873627.3153] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:00:27.31626 <info>  [1713873627.3161] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:00:27.31672 <info>  [1713873627.3165] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-23_12:00:34.33465 <info>  [1713873634.3345] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-23_12:00:34.35243 <info>  [1713873634.3523] dhcp4 (eth0): canceled DHCP transaction
2024-04-23_12:00:34.35247 <info>  [1713873634.3524] dhcp4 (eth0): state changed no lease
2024-04-23_12:00:34.35391 <info>  [1713873634.3538] manager: NetworkManager state is now DISCONNECTED
2024-04-23_12:00:40.86239 <info>  [1713873640.8622] device (eth0): carrier: link connected
2024-04-23_12:00:40.86295 <info>  [1713873640.8626] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-23_12:00:40.86366 <info>  [1713873640.8635] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-23_12:00:40.86432 <info>  [1713873640.8642] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-23_12:00:40.86444 <info>  [1713873640.8644] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:00:40.86486 <info>  [1713873640.8647] manager: NetworkManager state is now CONNECTING
2024-04-23_12:00:40.86610 <info>  [1713873640.8652] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:00:40.86615 <info>  [1713873640.8661] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:00:40.86762 <info>  [1713873640.8669] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-23_12:00:46.22831 <info>  [1713873646.2282] device (eth0): carrier: link connected
2024-04-23_12:00:53.23260 <info>  [1713873653.2324] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-23_12:00:53.25247 <info>  [1713873653.2523] dhcp4 (eth0): canceled DHCP transaction
2024-04-23_12:00:53.25250 <info>  [1713873653.2524] dhcp4 (eth0): state changed no lease
2024-04-23_12:00:53.25376 <info>  [1713873653.2536] manager: NetworkManager state is now DISCONNECTED
2024-04-23_12:01:21.52456 <info>  [1713873681.5244] manager: rfkill: Wi-Fi hardware radio set enabled
2024-04-23_12:01:21.76758 <info>  [1713873681.7675] audit: op="radio-control" arg="wireless-enabled:on" pid=1614 uid=1000 result="success"
2024-04-23_12:01:21.76794 <info>  [1713873681.7679] manager: rfkill: Wi-Fi now enabled by radio killswitch
2024-04-23_12:01:21.83208 <info>  [1713873681.8319] device (wlan0): supplicant interface state: internal-starting -> disconnected
2024-04-23_12:01:21.83223 <info>  [1713873681.8321] Wi-Fi P2P device controlled by interface wlan0 created
2024-04-23_12:01:21.83258 <info>  [1713873681.8325] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
2024-04-23_12:01:21.83294 <info>  [1713873681.8328] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
2024-04-23_12:01:21.83367 <info>  [1713873681.8333] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
2024-04-23_12:01:21.83401 <info>  [1713873681.8339] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:25.02215 <info>  [1713873685.0220] device (eth0): carrier: link connected
2024-04-23_12:01:25.02265 <info>  [1713873685.0224] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-04-23_12:01:25.02363 <info>  [1713873685.0235] policy: auto-activating connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-23_12:01:25.02460 <info>  [1713873685.0242] device (eth0): Activation: starting connection 'New 802-3-ethernet connection' (680fc38d-e5e3-472b-b9ba-707c31ec839a)
2024-04-23_12:01:25.02462 <info>  [1713873685.0244] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:25.02485 <info>  [1713873685.0247] manager: NetworkManager state is now CONNECTING
2024-04-23_12:01:25.02640 <info>  [1713873685.0252] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:25.02643 <info>  [1713873685.0258] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:25.02687 <info>  [1713873685.0267] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-23_12:01:26.71047 <info>  [1713873686.7103] policy: auto-activating connection 'TP-LINK_705B' (67eb0b1d-0483-49e2-9d2a-2d324e867195)
2024-04-23_12:01:26.71155 <info>  [1713873686.7109] device (wlan0): Activation: starting connection 'TP-LINK_705B' (67eb0b1d-0483-49e2-9d2a-2d324e867195)
2024-04-23_12:01:26.71157 <info>  [1713873686.7111] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:26.72587 <info>  [1713873686.7257] device (wlan0): set-hw-addr: reset MAC address to F8:28:19:C2:F0:83 (preserve)
2024-04-23_12:01:26.73157 <info>  [1713873686.7315] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:26.73190 <info>  [1713873686.7318] device (wlan0): Activation: (wifi) access point 'TP-LINK_705B' has security, but secrets are required.
2024-04-23_12:01:26.73193 <info>  [1713873686.7319] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:26.73248 <info>  [1713873686.7324] device (wlan0): supplicant interface state: disconnected -> interface_disabled
2024-04-23_12:01:26.73254 <info>  [1713873686.7325] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
2024-04-23_12:01:26.75117 <info>  [1713873686.7511] device (wlan0): supplicant interface state: interface_disabled -> inactive
2024-04-23_12:01:26.75121 <info>  [1713873686.7511] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive
2024-04-23_12:01:26.76094 <info>  [1713873686.7606] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:26.76105 <info>  [1713873686.7610] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:26.76170 <info>  [1713873686.7613] device (wlan0): Activation: (wifi) connection 'TP-LINK_705B' has security, and secrets exist.  No new secrets needed.
2024-04-23_12:01:26.76171 <info>  [1713873686.7613] Config: added 'ssid' value 'TP-LINK_705B'
2024-04-23_12:01:26.76172 <info>  [1713873686.7614] Config: added 'scan_ssid' value '1'
2024-04-23_12:01:26.76172 <info>  [1713873686.7614] Config: added 'bgscan' value 'simple:30:-70:86400'
2024-04-23_12:01:26.76172 <info>  [1713873686.7614] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
2024-04-23_12:01:26.76173 <info>  [1713873686.7615] Config: added 'psk' value '<hidden>'
2024-04-23_12:01:26.82727 <info>  [1713873686.8271] device (wlan0): supplicant interface state: inactive -> authenticating
2024-04-23_12:01:26.82729 <info>  [1713873686.8272] device (p2p-dev-wlan0): supplicant management interface state: inactive -> authenticating
2024-04-23_12:01:26.82932 <info>  [1713873686.8292] device (wlan0): supplicant interface state: authenticating -> associating
2024-04-23_12:01:26.82933 <info>  [1713873686.8293] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
2024-04-23_12:01:26.90403 <info>  [1713873686.9039] device (wlan0): supplicant interface state: associating -> completed
2024-04-23_12:01:26.90408 <info>  [1713873686.9040] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "TP-LINK_705B"
2024-04-23_12:01:26.90410 <info>  [1713873686.9040] device (p2p-dev-wlan0): supplicant management interface state: associating -> completed
2024-04-23_12:01:26.90425 <info>  [1713873686.9042] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:26.90487 <info>  [1713873686.9047] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
2024-04-23_12:01:27.68342 <info>  [1713873687.6833] dhcp4 (wlan0): state changed new lease, address=192.168.0.102, acd pending
2024-04-23_12:01:27.83582 <info>  [1713873687.8356] manager: rfkill: Wi-Fi hardware radio set disabled
2024-04-23_12:01:27.83585 <info>  [1713873687.8357] device (wlan0): state change: ip-config -> unavailable (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:27.85533 <info>  [1713873687.8552] dhcp4 (wlan0): canceled DHCP transaction
2024-04-23_12:01:27.85535 <info>  [1713873687.8553] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
2024-04-23_12:01:27.85537 <info>  [1713873687.8553] dhcp4 (wlan0): state changed no lease
2024-04-23_12:01:27.87287 <info>  [1713873687.8727] device (wlan0): set-hw-addr: set MAC address to FA:7E:43:0F:67:E1 (scanning)
2024-04-23_12:01:27.87674 <info>  [1713873687.8760] audit: op="radio-control" arg="wireless-enabled:off" pid=1614 uid=1000 result="success"
2024-04-23_12:01:27.87683 <info>  [1713873687.8767] manager: rfkill: Wi-Fi now disabled by radio killswitch
2024-04-23_12:01:27.87815 <info>  [1713873687.8780] device (p2p-dev-wlan0): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')
2024-04-23_12:01:42.63549 <info>  [1713873702.6354] dhcp4 (eth0): state changed new lease, address=192.168.1.3, acd pending
2024-04-23_12:01:42.77199 <info>  [1713873702.7719] dhcp4 (eth0): state changed new lease, address=192.168.1.3
2024-04-23_12:01:42.77260 <info>  [1713873702.7725] policy: set 'New 802-3-ethernet connection' (eth0) as default for IPv4 routing and DNS
2024-04-23_12:01:42.79187 <info>  [1713873702.7917] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:42.80841 <info>  [1713873702.8083] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:42.80874 <info>  [1713873702.8086] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
2024-04-23_12:01:42.80933 <info>  [1713873702.8091] manager: NetworkManager state is now CONNECTED_SITE
2024-04-23_12:01:42.80971 <info>  [1713873702.8094] device (eth0): Activation: successful, device activated.
2024-04-23_12:02:03.67913 <info>  [1713873723.6790] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
2024-04-23_12:02:03.68009 <info>  [1713873723.6797] policy: set 'New 802-3-ethernet connection' (eth0) as default for IPv6 routing and DNS
2024-04-23_12:02:04.67869 <info>  [1713873724.6785] dhcp6 (eth0): state changed new lease
2024-04-23_12:02:13.22902 <info>  [1713873733.2283] manager: NetworkManager state is now CONNECTED_GLOBAL

Below is the output of ip a; ip r after stoping NetworkManager
Code: [Select]
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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 proto kernel_lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 54:e1:ad:97:61:1d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
       valid_lft 604711sec preferred_lft 604711sec
    inet6 2409:8a3c:4cc:d370:ec73:21c8:e8b2:63be/64 scope global dynamic noprefixroute
       valid_lft 259169sec preferred_lft 172769sec
    inet6 fe80::4bcf:cbef:e9f4:1aec/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether f8:28:19:c2:f0:83 brd ff:ff:ff:ff:ff:ff
default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.3 metric 100
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.3 metric 100

Which command should I run to bring up both wired and wifi connections  without any dhcp?

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #13
Which command should I run to bring up both wired and wifi connections  without any dhcp?
Based on your output to bring up a wired connection on a freshly booted system with no network managers enabled (though can generally work otherwise)
Code: [Select]
ip link set eth0 up
ip addr add 192.168.1.3/24 broadcast 192.168.1.255 dev eth0
ip route add default via 192.168.1.1

If you have no nameserver in /etc/resolv.conf
Code: [Select]
echo "nameserver 1.1.1.1" > /etc/resolv.conf

Like I say there's confusion in this thread. Lot's of references to wifi and rrfkill which is irrelevant if you are trying to fix the wired connection.

And when you say "wired connection often, but not always, keeps deactivting."
It would help to provide the ip a and ip r output both before and after it stops working.
and try ping tests. Both domain and ip based
Code: [Select]
ping 1.1.1.1
ping google.com

Re: Wired connection keeps deactiviting after waking up from sleep

Reply #14
I have another Windows laptop ...

"Ceterum censeo M$ esse delendam"
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "