I'm using Fedora 31 on my Notebook. Everything works well, except for Fedora dropping the wifi connection after a while, making it necessary to reconnect to the network. Every few minutes after reconnecting the behaviour repeats itself. I have no idea what the reasons are for that. It often happens when I download files (putting "load" on the network) but sometimes also without any obvious reason. The problem first appeared under Fedora 30 and stayed after the upgrade to Fedora 31. Output from journalctl -b -u NetworkManager: -- Logs begin at Sun 2019-07-14 01:05:47 CEST, end at Sat 2019-11-16 23:42:15 CET. -- Nov 16 23:35:19 localhost.localdomain systemd: Starting Network Manager... Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8189] NetworkManager (version 1.20.6-1.fc31) is starting... (after a restart) Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8191] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf) Nov 16 23:35:19 localhost.localdomain systemd: Started Network Manager. Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8260] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8355] manager[0x5559cd8e80f0]: monitoring kernel firmware directory '/lib/firmware'. Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3382] hostname: hostname: using hostnamed Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3385] hostname: hostname changed from (none) to "localhost.localdomain" Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3390] dns-mgr[0x5559cd8cd240]: init: dns=default,systemd-resolved rc-manager=symlink Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3401] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.3/0000:05:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3403] manager[0x5559cd8e80f0]: rfkill: Wi-Fi hardware radio set enabled Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3403] manager[0x5559cd8e80f0]: rfkill: WWAN hardware radio set enabled Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3479] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-wifi.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3486] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-adsl.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3511] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-team.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3553] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-bluetooth.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3559] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-wwan.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3561] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3563] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3565] manager: Networking is enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3567] dhcp-init: Using DHCP client 'internal' Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3644] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-settings-plugin-ifcfg-rh.so") Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3644] settings: Loaded settings plugin: keyfile (internal) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3838] device (lo): carrier: link connected Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3845] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3886] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3951] settings: (enp4s0): created default wired connection 'Kabelgebundene Verbindung 1' Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3986] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4067] device (wlp5s0): driver supports Access Point (AP) mode Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4079] manager: (wlp5s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4127] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.7252] device (wlp5s0): set-hw-addr: set MAC address to 96:1B:95:D7:6D:B2 (scanning) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0023] modem-manager: ModemManager available Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0103] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0157] supplicant: wpa_supplicant running Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0157] device (wlp5s0): supplicant interface state: init -> starting Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0323] manager: (virbr0-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/5) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0446] device (virbr0-nic): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0458] device (virbr0-nic): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0583] sup-iface[0x5559cd8fe130,wlp5s0]: supports 5 scan SSIDs Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0596] device (wlp5s0): supplicant interface state: starting -> ready Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0597] Wi-Fi P2P device controlled by interface wlp5s0 created Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0599] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0602] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0610] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0613] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0631] sup-iface: failed to cancel p2p connect: P2P cancel failed Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3859] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3906] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3924] device (virbr0): Activation: starting connection 'virbr0' (dc059138-81a5-4d0a-bb5e-725c891ae6bf) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3935] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3947] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3976] device (virbr0-nic): Activation: starting connection 'virbr0-nic' (d3fd587b-3b1e-418f-9fa9-dc52709be3e1) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3980] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3991] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4045] device (virbr0-nic): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4060] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4066] device (virbr0-nic): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4073] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4083] manager: NetworkManager state is now CONNECTED_LOCAL Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4108] device (virbr0): Activation: successful, device activated. Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4127] device (virbr0-nic): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4203] device (virbr0): bridge port virbr0-nic was attached Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4203] device (virbr0-nic): Activation: connection 'virbr0-nic' enslaved, continuing activation Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4214] device (virbr0-nic): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4270] device (virbr0-nic): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4274] device (virbr0-nic): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4291] device (virbr0-nic): Activation: successful, device activated. Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4363] device (virbr0-nic): state change: activated -> unmanaged (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4374] device (virbr0): bridge port virbr0-nic was detached Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4374] device (virbr0-nic): released from master device virbr0 Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7709] policy: auto-activating connection 'Wifi-SSID' (b11eeab9-1cd2-40cf-b02e-719ac7a2cbcb) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7722] device (wlp5s0): Activation: starting connection 'Wifi-SSID' (b11eeab9-1cd2-40cf-b02e-719ac7a2cbcb) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7731] device (wlp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7741] manager: NetworkManager state is now CONNECTING Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7777] device (wlp5s0): set-hw-addr: reset MAC address to 58:00:E3:D0:B5:0F (preserve) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7887] device (wlp5s0): supplicant interface state: ready -> disabled Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7889] device (p2p-dev-wlp5s0): supplicant management interface state: ready -> disabled Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7892] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7897] device (wlp5s0): Activation: (wifi) access point 'Wifi-SSID' has security, but secrets are required. Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7898] device (wlp5s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7901] sup-iface[0x5559cd8fe130,wlp5s0]: wps: type pbc start... Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7939] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7946] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7950] device (wlp5s0): Activation: (wifi) connection 'Wifi-SSID' has security, and secrets exist. No new secrets needed. Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7952] Config: added 'ssid' value 'Wifi-SSID' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7952] Config: added 'scan_ssid' value '1' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7953] Config: added 'bssid' value '54:67:51:B8:29:2A' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7954] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7955] Config: added 'psk' value '' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7982] device (wlp5s0): supplicant interface state: disabled -> inactive Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7982] device (p2p-dev-wlp5s0): supplicant management interface state: disabled -> inactive Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.8098] device (wlp5s0): supplicant interface state: inactive -> scanning Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.8099] device (p2p-dev-wlp5s0): supplicant management interface state: inactive -> scanning Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5410] device (wlp5s0): supplicant interface state: scanning -> authenticating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5412] device (p2p-dev-wlp5s0): supplicant management interface state: scanning -> authenticating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5617] device (wlp5s0): supplicant interface state: authenticating -> associating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5618] device (p2p-dev-wlp5s0): supplicant management interface state: authenticating -> associating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6162] device (wlp5s0): supplicant interface state: associating -> associated Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6162] device (p2p-dev-wlp5s0): supplicant management interface state: associating -> associated Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6367] device (wlp5s0): supplicant interface state: associated -> 4-way handshake Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6367] device (p2p-dev-wlp5s0): supplicant management interface state: associated -> 4-way handshake Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7563] device (wlp5s0): supplicant interface state: 4-way handshake -> completed Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7564] device (wlp5s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Wifi-SSID" Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7564] device (p2p-dev-wlp5s0): supplicant management interface state: 4-way handshake -> completed Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7651] device (wlp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7656] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds) Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8962] dhcp4 (wlp5s0): state changed unknown -> bound Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8970] device (wlp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8993] device (wlp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8995] device (wlp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9002] manager: NetworkManager state is now CONNECTED_LOCAL Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9017] manager: NetworkManager state is now CONNECTED_SITE Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9018] policy: set 'Wifi-SSID' (wlp5s0) as default for IPv4 routing and DNS Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9062] device (wlp5s0): Activation: successful, device activated. Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9069] manager: startup complete Nov 16 23:35:31 localhost.localdomain NetworkManager: [1573943731.0336] manager: NetworkManager state is now CONNECTED_GLOBAL Nov 16 23:35:32 localhost.localdomain NetworkManager: [1573943732.0747] policy: set 'Wifi-SSID' (wlp5s0) as default for IPv6 routing and DNS Nov 16 23:35:34 localhost.localdomain NetworkManager: [1573943734.5034] agent-manager: req[0x5559cd9eb540, :1.201/org.gnome.Shell.NetworkAgent/1000]: agent registered Nov 16 23:40:47 localhost.localdomain NetworkManager: [1573944047.5176] manager: NetworkManager state is now CONNECTED_SITE The general journal shows the following before dropping the connection: Nov 16 23:40:40 localhost.localdomain systemd: Starting Tracker metadata database store and lookup manager... Nov 16 23:40:40 localhost.localdomain systemd: Started Tracker metadata database store and lookup manager. Nov 16 23:40:47 localhost.localdomain NetworkManager: [1573944047.5176] manager: NetworkManager state is now CONNECTED_SITE Nov 16 23:40:47 localhost.localdomain systemd: Starting Network Manager Script Dispatcher Service... Nov 16 23:40:47 localhost.localdomain systemd: Started Network Manager Script Dispatcher Service. Nov 16 23:40:47 localhost.localdomain audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 16 23:40:57 localhost.localdomain systemd: NetworkManager-dispatcher.service: Succeeded. Nov 16 23:40:57 localhost.localdomain audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 16 23:41:11 localhost.localdomain tracker-store: OK Nov 16 23:41:11 localhost.localdomain systemd: tracker-store.service: Succeeded. I also get the following error during the creation phase of the connection: Nov 16 23:43:08 localhost.localdomain systemd: Started Network Manager Script Dispatcher Service. Nov 16 23:43:08 localhost.localdomain kernel: wlp5s0: deauthenticating from 54:67:51:b8:29:2a by local choice (Reason: 3=DEAUTH_LEAVING) Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=54:67:51:b8:29:2a reason=3 locally_generated=1 Nov 16 23:43:08 localhost.localdomain wpa_supplicant: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0 Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6104] sup-iface[0x5559cd8fe130,wlp5s0]: connection disconnected (reason -3) Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6110] device (wlp5s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6136] dhcp4 (wlp5s0): canceled DHCP transaction Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6136] dhcp4 (wlp5s0): state changed bound -> done Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE

I have a very basic wireguard connection that routes all traffic through a VPN.

[Interface]
PrivateKey = 
Address = 
DNS = 

[Peer]
PublicKey = 
AllowedIPs = 0.0.0.0,::0/0
Endpoint =

I've imported and enabled it with NetworkManager using nmcli connection import type wireguard file $conf. My problem is I have a scheduled process that I would like to _not_ go through the wireguard tunnel, _(ie come from my home IP address)_. And I'd rather not carve out an exception in the wireguard config. The solution I've tried is to setup a network namespace which is linked to eth0. That way I could bypass the wireguard connection with sudo ip netns exec clearnet. But I can't link the namespace directly to eth0 or else everything else looses access to eth0 and the internet in general. This is turning out very convoluted though because I've got to do something like eth0 -> br0 -> veth0 -> veth1 -> ns1

sudo ip netns add clearnet # create namespace
sudo ip link add veth0 type veth peer name veth1 # create veth pair
sudo ip link set veth1 netns clearnet # link the veth1 to the clearnet
sudo ip link add br0 type bridge # create bridge
sudo ip link set eth0 master br0 # connect eth0 to the bridge (lose internet here)
sudo ip link set veth0 master br0 # connect veth0 to the bridge

# turn everything on
sudo ip link set br0 up
sudo ip link set veth0 up
sudo ip netns exec clearnet ip link set veth1 up

nmcli connection up br0 # restore internet

# give the bridge an IP address
sudo ip addr add 192.168.100.1/24 dev br0
sudo ip addr add 192.168.100.1/24 dev veth0

# give the namespace and IP address
sudo ip netns exec ip addr add 192.168.100.2/24 dev veth1

# tell the namespace to route via the bridge's IP
sudo ip netns exec ip route add default via 192.168.100.1

At this point I still don't have internet access via clearnet, much less DNS, and I'm convinced I'm doing this the _hard way_. Something like NetworkManager, systemd (which schedules the process), or docker (which executes the process) should have a short cut. Or is what I'm seeking really this complicated?

My end goal here is to have no saved network connections, no enabled Wi-Fi or networking each time I boot up my computer, so that I have to go through a sequence of steps in order to access internet. The purpose is to moderate my sceen behavior. My current way is through creating a script that uses 'nmcli' and run at startup using crontab's @reboot. But It's not working. Here is the script

#!/bin/bash

# this script disables wifi and networking

echo 'Deleting all existing connections...'
# nmcli is a command-line interface for networkmanager
# 'nmcli connection delete' -> simply deletes a connection by ID, UUID or others
# we use 'nmcli connection show' along with some filter to extract UUIDs for all conections
# TODO enable deletion of a particular connection
#connections_list=$(nmcli connection show | grep -oP '\s(\S+-\S+-\S+-\S+-\S+)\s')
#for connection in "$connections_list"; do 
    #nmcli connection show "$connection"
    #if (($? != 0)); then 
        #echo "something went wrong while deleting connection $connection" >&2
        #exit 1
    #fi
#done
nmcli connection delete $(nmcli connection show | grep -oP '\s(\S+-\S+-\S+-\S+-\S+)\s') 
if [[ $? -ne 0 ]]; then
    echo 'shit happens while deleting connections' >&1 
    exit 1
fi
echo 'All connections were deleted! now, you will have to type SSID and password again'

echo 

echo 'Disabling Wi-Fi...'
if ! nmcli radio wifi off; then 
    echo 'nmcli, command disabling wifi, is not satisfied for some reason' >&2
    exit 1
fi 
echo 'Wi-Fi is disabled.'

echo 

echo 'Disabling networking...'
if ! nmcli networking off; then 
    echo 'nmcli, command disabling networking, is not happy' >&2 
    exit 1
fi
echo 'Networking is disabled.'

echo

echo 'All is good'
echo '==============================='
exit 0

Here is the corntab line (created using sudo crontab -e) @reboot /home/noor/bin/go-offline-1.0 >> /home/noor/go-offline.log 2>&1 Contents of log file:

Deleting all existing connections...
Error: NetworkManager is not running.
Error: NetworkManager is not running.
shit happens while deleting connections

I guess that at the point of executing my script in the boot process, NetwrokManager is not yet activated. Also after a quick exchange with ChatGPT, I tried to make script run as part of the shut down process rather than at startup using systemlc or sth, but it didn't work for some reason. I don't see reason to mention its details. I had an idea to alias poweroff command so that it executes my script then shut down the computer. I don't know whether it's a good idea but I am looking for a better solution anyway. I welcome all useful responses related to any part of this, including fixes to this method or completely different approach. Thank you!

I have a connection via VPN with my work. I know that internet connection (for example to 8.8.8.8) goes through my work network (only when I am connected to VPN). How to configure ip tables to force that connections to internet (for example 8.8.8.8) avoid work network ? Using @Julie help in comments I did managed to discover some options: " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> Nevertheless, after checking 'Use this connection only for resources...' I can't ping machines in VPN network. Can you tell me how should I deal with it ? I guess that I should click 'Add' and set: Address = address of some machine in VPN Netmask = I can get it from ifconfig (in VPN interface) Gateway - as in case of netmask Metri - I have no idea ? Am I right ?

I've suddenly realized wpa_supplicant is spamming my system logs with these messages:

Sep 02 08:07:17 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=648500
Sep 02 08:07:20 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=648500
Sep 02 08:07:23 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=648500
Sep 02 08:07:26 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=648500
Sep 02 08:07:29 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=432300
Sep 02 08:07:32 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=432300
Sep 02 08:07:35 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=576400
Sep 02 08:07:38 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=576400
Sep 02 08:07:41 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=576400
Sep 02 08:07:44 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=576400

I want this to stop. My WiFi works perfectly but these seemingly debug messages drive me insane and generate over 2GB of disk writes daily. For the past three days:

journalctl | grep CTRL-EVENT-SIGNAL-CHANGE | wc -l
24500

I'm using fully updated Fedora 40 with NetworkManager.

The NetworkManager has stopped working, and I can't seem to get it to start running again. If checking the status is says masked and inactive (dead). How do I fix this?

I can't connect to internet via wired, adding DSL profile with user and password. While installing kali linux 2.0 there was a warning telling that there is missing non-free firmware rtl_nic/rtl8106e-1.fw but it is in /lib/firmware/rtl_nic/ Have Realtek RTL8139/810x Fast Ethernet Adapter PCI. Was no problem on previous versions of Kali.

I want to debug a script that contains Networkmanager-dispacher-variables like DEVICE_IFACE, IP4_GATEWAY. The Networkmanager-manual describes these variables but doesn't mention how to debug them. I searched a lot but i am unable to figure out how to get the value of these variables. When i echo on the command line like echo ${DEVICE_IFACE} i get no value.

Is there any way that I can make networkmanager to assign some unique names or device derrived name instead of Auto Ethernet so that we can avoid the names conflict? After I've upgraded to Ubuntu Vivid which uses systemd(though I'm not sure if it's directly related or it's just a bug / regression of network-manager) both of my mobile broadband devices get the "Auth Ethernet" name and are unable to get connected simultaneously. I can temporarry fix it using nmcli con add type ethernet con-name my-office ifname ens3 but I would rather like to have network-manager handle this automatically (i.e. assign a random / unique conn name). Use case: I have two broadband USB devices and I need to connect to both of them. The issue is that NetworkManager displays them both as Auto Ethernet (duplicate in the network manager applet) and when I try to connect to the second network it errors out `(32) Connection 'Auto Ethernet' is already active on enp0s20u`. When I try to "edit" the connections it displays only one Auto Ethernet connection. /etc/NetworkManager/system-connections also lists only one Auto Ethernet

I am running an Ubuntu 16.04 derived Linux on an embedded processor, Yocto build Kernel appears to be 4.14.141 I am bringing up a WiFi Access point on the hardware programmatically from C by enabling the radio with a call to system("nmcli r wifi on"); ( This may be superfluous at the moment but bear with me.) At which point I bring up an access point with system( "nmcli dev wifi hotspot ifname wlan0 ssid \"test\" password \"test1234\" ") So Now I have in /etc/NetworkManager/system-connections a file Hotspot.nmconnection with the correct details for this access point [connection] id=Hotspot-2 uuid=70c76bd2-0e13-492e-8a45-9094bc6e0773 type=wifi autoconnect=false permissions= [wifi] mac-address=00:04:F3:1B:BA:AE mac-address-blacklist= mode=ap ssid=test [wifi-security] group=ccmp; key-mgmt=wpa-psk pairwise=ccmp; proto=rsn; psk=test1234 [ipv4] dns-search= method=shared [ipv6] addr-gen-mode=stable-privacy dns-search= method=ignore My problem is that each time I want to use this access point I want to bring it up with a different SSID and a different password. The Access point is tied to a users session so its life is limited to that session and a set of credentials ( not available except through a passed hardware token ) The Wifi AP starts up to match the presented token and is shut down and can be destroyed after the token is removed. Attempting to modify this configuration file with nmcli system ("nmcli con mod Hotspot ssid \"newTest\" password \"newpass\" "); fails with Error: invalid . 'password'. redefining the AP with the first command results in a successful new wifi AP being created but it gains a new configuration file with a number suffix based on the previous itterations Hotspot-2, Hotspot-n etc, wont be long until my flash overflows. So how do I do this? Where and how do I define a password file which is what I gather I need or how do I change things to allow me to achieve my goal? I have a suspicion that I need to get polkit involved but that's a rabbit warren I have not been down yet.

I'm trying to use D-bus method AddAndActivate connection on interface org.freedesktop.NetworkManager to create a wifi connection. I definitely pass a PreSharedKey field with the password, but NetworkManager ignores this field, fails on connection activation and asks for a password when I try to use nmcli c up . Any ideas how to force it to save the password?

In the top bar, clicking the network icon shows a list of networks. My school's network, which on Windows I would connect to, and then visit a login page in Chrome in order for it to work, shows on the list. When I click to connect it shows it connecting, and then says that I am not connected to the Internet. I am using elementary OS 0.3 Freya. Running iwconfig shows eth0 no wireless extensions. wlan0 unassociated Nickname:"rtl_wifi" Mode:Managed Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 lo no wireless extensions.

Sometimes wifi disconnecting repeatedly. Sometime disconnecting after hours or after 30mins, i couldnt find the cause. And sometimes when running sudo docker exec -it 96414b09135d bash also it disconnects after minutes. i tried setting sudo nano /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf wifi.powersave = 2 and tried 1. sudo ifconfig wlp2s0 down 2. sudo iwconfig wlan0 power off 3. sudo ifconfig wlp2s0 up 4. sudo service network-manager restart and tried systemctl list-unit-files --state enabled keyboard-setup.service enabled enabled ModemManager.service enabled enabled network-manager.service enabled enabled networkd-dispatcher.service enabled enabled Also tried, sudo wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf Successfully initialized wpa_supplicant Failed to open config file '/etc/wpa_supplicant/wpa_supplicant.conf', error: No such file or directory Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'. Also tried sudo nano /etc/NeworkManager/NetworkManger.conf [device] wifi.scan-rand-mac-address=no Tried : 1. sudo service bluetooth restart 2. sudo modprobe wl sudo lshw -C network 3. sudo apt install network-manager 4. git clone https://github.com/mehedihshakeel/BroadcomInstaller2017.git git clone https://github.com/prasathlk/BroadcomInstaller2019.git cd BroadcomInstaller2019/ ./Broadcom.sh Here /etc/pm/sleep.d$ ls 10_grub-common 10_unattended-upgrades-hibernate config Here echo "options QCA9377 fwlps=N" | sudo tee /etc/modprobe.d/QCA9377.conf options QCA9377 fwlps=N Here sudo nano /etc/dhcp/dhclient.conf #timeout 300; Here dpkg -S $(which NetworkManager) network-manager: /usr/sbin/NetworkManager Here is my apt policy network-manager network-manager: Installed: 1.22.10-1ubuntu2.2 Candidate: 1.22.10-1ubuntu2.2 Version table: *** 1.22.10-1ubuntu2.2 500 500 http://in.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages Here are my sudo journalctl -fu NetworkManager [1637549618.0666] dhcp6 (wlp2s0): state changed unknown -> bound [1637549996.3364] sup-iface[0x55dc05fec3d0,wlp2s0]: connection disconnected (reason -3) [1637549996.4370] manager: rfkill: Wi-Fi now disabled by radio killswitch [1637549996.4374] device (wlp2s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed') [1637549996.4665] dhcp4 (wlp2s0): canceled DHCP transaction [1637549996.4666] dhcp4 (wlp2s0): state changed bound -> done [1637549996.4672] dhcp6 (wlp2s0): canceled DHCP transaction [1637549996.4672] dhcp6 (wlp2s0): state changed bound -> done --------------------- [1637553729.6989] sup-iface[0x55dc05fec1f0,wlp2s0]: connection disconnected (reason -3) [1637553729.6992] device (wlp2s0): supplicant interface state: completed -> disconnected [1637553729.6992] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> disconnected [1637553729.7093] device (wlp2s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') [1637553729.7305] dhcp4 (wlp2s0): canceled DHCP transaction [1637553729.7306] dhcp4 (wlp2s0): state changed bound -> done [1637553729.7314] dhcp6 (wlp2s0): canceled DHCP transaction [1637553729.7314] dhcp6 (wlp2s0): state changed bound -> done --------------------- [1637553946.7590] sup-iface[0x55dc05fec1f0,wlp2s0]: connection disconnected (reason -4) [1637553946.7982] device (wlp2s0): supplicant interface state: completed -> disconnected [1637553946.7982] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> disconnected [1637553950.8662] device (wlp2s0): supplicant interface state: disconnected -> scanning [1637553950.8662] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning [1637553962.0505] device (wlp2s0): link timed out. [1637553962.0529] device (wlp2s0): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed') [1637553962.0610] device (wlp2s0): Activation: failed for connection 'WIFINAME' [1637553962.0650] device (wlp2s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') [1637553962.0985] dhcp4 (wlp2s0): canceled DHCP transaction [1637553962.0986] dhcp4 (wlp2s0): state changed bound -> done [1637553962.1123] manager: NetworkManager state is now CONNECTED_LOCAL [1637553980.3890] manager: rfkill: Wi-Fi hardware radio set disabled [1637553980.3891] device (wlp2s0): state change: disconnected -> unavailable (reason 'none', sys-iface-state: 'managed') [1637553980.3930] audit: op="radio-control" arg="wireless-enabled" pid=1512 uid=1000 result="success" [1637553980.3934] device (p2p-dev-wlp2s0): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed') [1637553980.3962] manager: rfkill: Wi-Fi now disabled by radio killswitch [1637553984.3856] manager: rfkill: Wi-Fi hardware radio set enabled [1637553984.6532] audit: op="radio-control" arg="wireless-enabled" pid=1512 uid=1000 result="success" [1637553984.6538] manager: rfkill: Wi-Fi now enabled by radio killswitch [1637553984.8032] sup-iface[0x55dc05fec100,wlp2s0]: supports 5 scan SSIDs [1637553984.8048] device (wlp2s0): supplicant interface state: starting -> ready [1637553984.8049] device (p2p-dev-wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') [1637553984.8055] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')

I have a network interface that is configured for static ip address. When I reboot I have to always open the NetworkManager GUI and click "connect" button. ## How do you automatically enable network interface at system startup?

I recently upgraded from linux mint 21.0 to 21.3. After upgrading Networkmanager has seem to imported my existing wireguard connections (*/etc/wireguard/wg0.conf*) which results in it being displayed in the tray icon. This results in not seeing if I am connected to a wifi or previously if I am connected to a vpn. I tried the following: 1 Removing the connection nmcli connection delete wg0 2 Add the following to */etc/NetworkManager/NetworkManager.conf* [keyfile] unmanaged-devices=interface-name:wg0 After a restart the wg0 connection reappears in the tray icon. I bring up my wg0.conf via a systemd unit file and I don't want Networkmanager to manage or display my wireguard connections. How to accomplish this?

I am learning about Linux networking on my Kubuntu 18.04 workstation, and I see there that both NetworkManager and networkd-dispatcher are running: oleg@eclectic:~$ sudo ps -ef | grep -i net root 56 2 0 Oct11 ? 00:00:00 [netns] root 1097 1 0 Oct11 ? 00:00:02 /usr/sbin/NetworkManager --no-daemon root 1098 1 0 Oct11 ? 00:00:00 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers root 1250 1 0 Oct11 ? 00:00:02 /usr/sbin/inetd root 1593 1097 0 Oct11 ? 00:00:00 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper... NetworkManager seems to be configured to handle "everything" by netplan: oleg@eclectic:~$ cat /etc/netplan/01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager I believe that netplan would hand everything off to networkd if NetworkManager was not installed. There are also a bunch of files in /etc/network/, and I am not sure what is handling those. A lot of packages seem to use this directory: oleg@eclectic:~$ dpkg -S /etc/network avahi-daemon, ifupdown2, wpasupplicant, openvpn, postfix, netbase, avahi-autoipd, wireless-tools, clamav-freshclam: /etc/network My initial thoughts after some Googling are that NetworkManager and networkd are both running, but netplan generates configuration such that only one is actually doing something. But I do not know how I would verify this, figure out the chain of operations, or configure it to suit my nefarious plans for dummy0. **Question:** How exactly are NetworkManager, networkd, and netplan working together? In other words, as the computer boots up, which processes hand what of to what other processes? How do tools from packages like net-tools, ifupdown2, and iproute2 and directories like /etc/network/ fit into all this? And finally, how can I figure this out myself and learn the details using the command line? **Update:** I am not looking for a high-level overview. Rather, I want to know how these components are interacting, conflicting, or avoiding conflict on the kernel level or similar.

How to export and migrate NetworkManager settings to new system? Use cases are: - reinstalling a machine - moving network configuration from laptop to desktop system (or vice-versa) All settings should be migrated, that includes: - default and custom network connections - wifi connections with passwords - VLAN configurations - VPN configurations (with keys if possible) I checked on Arch wiki and it there is nothing on migration, so I'm asking you guys and gals here.

Currently running on Fedora Server 23, I've been searching for the right way to persist commands such as: ip route add default via 10.0.2.1 dev ens32 table EXAMPLE_TABLE ip rule add from 10.1.2.50 lookup EXAMPLE_TABLE prio 1000 either through nmcli (ideally) or through some other, similarly, **sane** way. I've seen examples like lodging it on the *route-ifname* file but that don't seem to execute the default rule correctly. If you run ip route show table EXAMPLE_TABLE after a reboot you'll realize it doesn't stick - at least in my experience. Any insights into this would be lovely, thank you.

I am running NetworkManager on Debian 11. I have a script that is activated by NetworkManager dispatcher on pre-up. It has been running fine so far and now I would like to add another piece of functionality: I have a situation where it would be helpful if the script could tell dispatcher to not finalize bringing the NIC fully up from the current pre-up state, if certain conditions are met, preventing the connection from being announced to applications on the system. Is there a way to achieve that? The best I have been able to come up with is to call nmcli connection down $CONN_NAME from inside the script, but it is unclear whether that is performed before or after dispatcher brings the NIC up and applications can access the connection. I would much prefer if dispatcher would handle it and presumably guarantee that the up state is never reached. I found these resources useful but uninformative about the functionality I am looking for: https://networkmanager.dev/docs/api/latest/NetworkManager-dispatcher.html https://wiki.archlinux.org/title/NetworkManager#Network_services_with_NetworkManager_dispatcher https://blogs.oracle.com/linux/post/networkmanager-dispatcher-scripts https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/networking_guide/sec-Using_NetworkManager_with_Network_Scripts#bh-Running_Dispatcher_Scripts

glad to be on these forums! I searched around a bit on the forums, but couldn't find a good pre-existing case for this that might resolve anything. The error just happened out of nowhere after a boot-up, but I do have an "enp" type wireless device name listed at "DEVICE=" in a file named "ifcfg-[my own device name]" which can be a problem if not the case, so what happened here? When I run "systemctl restart network", I get: "job for network.service failed because the control process exited with error code". 1) Restarting anything does no good for anything. 2) I haven't tried re-installing anything - yet. 3) "ip add flush [device name]" does nothing, says my device doesn't exist. 4) Pinging 127.0.0.1 gives response. At one point, I got this message too: "failed to start lsb bring up/down networking" What suddenly happened here? I'm on a fedora30. Thx for taking the time to read this. RX