You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2025-06-13 15:15:52
- michael8rown
- Member
- Registered: 2021-08-25
- Posts: 27
[Solved] Random network disconnects
Since around mid-April, I've been having random issues with networking on an Arch server: when this problem occurs, I cannot access the server (http, ssh, smb) from other local machines, but I can get out to websites like archlinux.org and google.com from the server. Other websites, such as goodreads.com and duckduckgo.com are unavailable.
This machine hosts a local web server and also has a VM running Debian, which has Koha ILS installed. The Arch webserver has a static IP of 10.0.0.160 and the Debian VM has a static IP of 10.0.0.42. Each reboot, the bridge gets created and the vm is started as follows:
ip link add name br0 type bridge
ip link set dev br0 up
ip address add 10.0.0.160/24 dev br0
ip route append default via 10.0.0.1 dev br0
ip link set enp1s0 master br0
ip address del 10.0.0.160/24 dev enp1s0
virsh start debian12I recently moved from Austin (Google Fiber ISP) to Albuquerque (Xfinity ISP). I did not experience this problem in Austin, so I'm wondering if this might have something to do with either my router or the ISP in general. When I have this problem, I run the following commands to fix it:
virsh shutdown debian12
ip link set br0 down
brctl delbr br0
systemctl restart NetworkManager.service
ip link add br0 type bridge
ip link set dev br0 up
ip address add 10.0.0.160/24 dev br0
ip route append default via 10.0.0.1 dev br0
ip link set enp1s0 master br0
ip address del 10.0.0.160/24 dev enp1s0
virsh start debian12The only other method of fixing it that I've tried is rebooting the entire Arch server. But I would prefer to not reboot anything and so I'd like to ask for help. The Arch server network is currently down, so I should be able to troubleshoot.
Here is the latest log showing the current disconnect, which seems to occur around 22:17:48 on June 12: http://0x0.st/8EUd.txt
And here is information I've seen requested in other similar threads:
$ ip a
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b0:41:6f:0e:4f:21 brd ff:ff:ff:ff:ff:ff
altname enxb0416f0e4f21
inet 10.0.0.160/24 brd 10.0.0.255 scope global dynamic noprefixroute enp1s0
valid_lft 168057sec preferred_lft 168057sec
inet6 2601:8c0:385:8650::339d/128 scope global dynamic noprefixroute
valid_lft 340859sec preferred_lft 340859sec
inet6 2601:8c0:385:8650:34fb:83f6:84f1:7c1b/64 scope global dynamic noprefixroute
valid_lft 298sec preferred_lft 298sec
inet6 fe80::7d61:df6a:413f:1380/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 8a:be:1e:bb:ed:9b brd ff:ff:ff:ff:ff:ff permaddr f0:20:ff:30:21:f4
altname wlp2s0
altname wlxf020ff3021f4
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether e6:a6:d3:fd:3d:18 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.160/24 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::e4a6:d3ff:fefd:3d18/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
5: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:09:cd:9a brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe09:cd9a/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever$ ip route
default via 10.0.0.1 dev br0
default via 10.0.0.1 dev enp1s0 proto dhcp src 10.0.0.160 metric 100
10.0.0.0/24 dev br0 proto kernel scope link src 10.0.0.160
10.0.0.0/24 dev enp1s0 proto kernel scope link src 10.0.0.160 metric 100$ ping -c3 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
From 10.0.0.160 icmp_seq=1 Destination Host Unreachable
From 10.0.0.160 icmp_seq=2 Destination Host Unreachable
From 10.0.0.160 icmp_seq=3 Destination Host Unreachable
--- 10.0.0.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2012ms
pipe 2$ iptables -nvL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination $ lspci -k
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453
Kernel driver in use: pcieport
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453
Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453
Kernel driver in use: pcieport
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Kernel driver in use: pcieport
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
Subsystem: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
Kernel driver in use: r8169
Kernel modules: r8169
02:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
DeviceName: Onboard LAN Brodcom
Subsystem: Intel Corporation Wi-Fi 6 AX200NGW
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
03:00.0 Non-Volatile memory controller: Phison Electronics Corporation PS5015-E15 PCIe3 NVMe Controller (DRAM-less) (rev 01)
Subsystem: Phison Electronics Corporation PS5015-E15 PCIe3 NVMe Controller (DRAM-less)
Kernel driver in use: nvme
Kernel modules: nvme
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lucienne (rev c1)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0123
Kernel driver in use: amdgpu
Kernel modules: amdgpu
04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
Kernel driver in use: ccp
Kernel modules: ccp
04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
Kernel driver in use: xhci_hcd
04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
Kernel driver in use: xhci_hcd
04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Audio Coprocessor (rev 01)
Subsystem: Advanced Micro Devices, Inc. [AMD] Audio Coprocessor
Kernel driver in use: snd_rn_pci_acp3x
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63, snd_sof_amd_acp70
04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller
DeviceName: HD Audio Controller
Subsystem: Advanced Micro Devices, Inc. [AMD] Device d270
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
05:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function (rev 81)
Subsystem: Advanced Micro Devices, Inc. [AMD] Device 7901
05:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode]
Kernel driver in use: ahci$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
acpid.service | multi-user.target.wants
bluetooth.service | bluetooth.target.wants
br0.timer | multi-user.target.wants
ckJobs.timer | timers.target.wants
ckUpd.timer | timers.target.wants
cups.path | multi-user.target.wants
cups.service | multi-user.target.wants
cups.service | printer.target.wants
cups.socket | sockets.target.wants
dbus-org.bluez.service | system
dbus-org.fedoraproject.FirewallD1.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service | system
dbus-org.freedesktop.timesync1.service | system
default.target | system
display-manager.service | system
durangoStatus.timer | timers.target.wants
firewalld.service | multi-user.target.wants
gcr-ssh-agent.socket | sockets.target.wants
getty@tty1.service | getty.target.wants
gnome-keyring-daemon.socket | sockets.target.wants
goToSleep.timer | timers.target.wants
hiTemp.timer | timers.target.wants
httpd.service | multi-user.target.wants
lbBkup.timer | timers.target.wants
libvirtd-admin.socket | sockets.target.wants
libvirtd-ro.socket | sockets.target.wants
libvirtd.service | multi-user.target.wants
libvirtd.socket | sockets.target.wants
mariadb.service | multi-user.target.wants
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
p11-kit-server.socket | sockets.target.wants
paccache.timer | timers.target.wants
pipewire-pulse.socket | sockets.target.wants
pipewire-session-manager.service | user
pipewire.socket | sockets.target.wants
reflector.timer | timers.target.wants
remote-fs.target | multi-user.target.wants
smb.service | multi-user.target.wants
sshd.service | multi-user.target.wants
systemd-boot-update.service | sysinit.target.wants
systemd-resolved.service | sysinit.target.wants
systemd-timesyncd.service | sysinit.target.wants
virtlockd-admin.socket | sockets.target.wants
virtlockd.socket | sockets.target.wants
virtlogd-admin.socket | sockets.target.wants
virtlogd.socket | sockets.target.wants
vmCtrl.timer | timers.target.wants
wc.timer | timers.target.wants
wireplumber.service | pipewire.service.wants
xdg-user-dirs-update.service | default.target.wants$ resolvectl status
Global
Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
Current DNS Server: 8.8.8.8
DNS Servers: 8.8.8.8 8.8.4.4
Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com
2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google
Link 2 (enp1s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 8.8.8.8
DNS Servers: 8.8.8.8 8.8.4.4 2001:558:feed::1 2001:558:feed::2
Default Route: yes
Link 3 (wlo1)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
Link 4 (br0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
Link 5 (vnet0)
Current Scopes: LLMNR/IPv6 mDNS/IPv6
Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: noNote: In Austin, I was not running systemd-resolved. This is something I started using in the hopes of solving this problem.
$ nmcli g
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN METERED
connected full enabled disabled missing enabled no (guessed) $ nmcli conn show
NAME UUID TYPE DEVICE
Wired connection 1 5745e71f-976c-317c-a85c-d26cb15f318d ethernet enp1s0
br0 b550fcac-1fa9-4601-9ffb-b0d14c5bb2b7 bridge br0
lo cb5d4008-004c-403f-bb7d-c458aef2fc0e loopback lo
vnet0 d2c0ca6a-db4f-47e8-a3d4-76c15597d77d tun vnet0
Bueno c28149c2-6e62-402b-9813-70453f725e48 wifi --
Bueno2 17a10c99-5aa9-4ded-8085-2387bf475915 wifi -- $ nmcli connection show Wired\ connection\ 1
connection.id: Wired connection 1
connection.uuid: 5745e71f-976c-317c-a85c-d26cb15f318d
connection.stable-id: --
connection.type: 802-3-ethernet
connection.interface-name: enp1s0
connection.autoconnect: yes
connection.autoconnect-priority: -999
connection.autoconnect-retries: -1 (default)
connection.multi-connect: 0 (default)
connection.auth-retries: -1
connection.timestamp: 1749788359
connection.permissions: --
connection.zone: --
connection.controller: --
connection.master: --
connection.slave-type: --
connection.port-type: --
connection.autoconnect-slaves: -1 (default)
connection.autoconnect-ports: -1 (default)
connection.down-on-poweroff: -1 (default)
connection.secondaries: --
connection.gateway-ping-timeout: 0
connection.ip-ping-timeout: 0
connection.ip-ping-addresses: --
connection.ip-ping-addresses-require-all:-1 (default)
connection.metered: unknown
connection.lldp: default
connection.mdns: -1 (default)
connection.llmnr: -1 (default)
connection.dns-over-tls: -1 (default)
connection.mptcp-flags: 0x0 (default)
connection.wait-device-timeout: -1
connection.wait-activation-delay: -1
802-3-ethernet.port: --
802-3-ethernet.speed: 0
802-3-ethernet.duplex: --
802-3-ethernet.auto-negotiate: no
802-3-ethernet.mac-address: --
802-3-ethernet.cloned-mac-address: --
802-3-ethernet.generate-mac-address-mask:--
802-3-ethernet.mac-address-denylist: --
802-3-ethernet.mtu: auto
802-3-ethernet.s390-subchannels: --
802-3-ethernet.s390-nettype: --
802-3-ethernet.s390-options: --
802-3-ethernet.wake-on-lan: default
802-3-ethernet.wake-on-lan-password: --
802-3-ethernet.accept-all-mac-addresses:-1 (default)
ipv4.method: auto
ipv4.dns: 8.8.8.8,8.8.4.4
ipv4.dns-search: --
ipv4.dns-options: --
ipv4.dns-priority: 0
ipv4.addresses: --
ipv4.gateway: --
ipv4.routes: --
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.routing-rules: --
ipv4.replace-local-rule: -1 (default)
ipv4.dhcp-send-release: -1 (default)
ipv4.routed-dns: -1 (default)
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: yes
ipv4.dhcp-client-id: --
ipv4.dhcp-iaid: --
ipv4.dhcp-dscp: --
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname-deprecated: yes
ipv4.dhcp-send-hostname: -1 (default)
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.dhcp-hostname-flags: 0x0 (none)
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.required-timeout: -1 (default)
ipv4.dad-timeout: -1 (default)
ipv4.dhcp-vendor-class-identifier: --
ipv4.dhcp-ipv6-only-preferred: -1 (default)
ipv4.link-local: 0 (default)
ipv4.dhcp-reject-servers: --
ipv4.auto-route-ext-gw: -1 (default)
ipv4.shared-dhcp-range: --
ipv4.shared-dhcp-lease-time: 0 (default)
ipv6.method: auto
ipv6.dns: --
ipv6.dns-search: --
ipv6.dns-options: --
ipv6.dns-priority: 0
ipv6.addresses: --
ipv6.gateway: --
ipv6.routes: --
ipv6.route-metric: -1
ipv6.route-table: 0 (unspec)
ipv6.routing-rules: --
ipv6.replace-local-rule: -1 (default)
ipv6.dhcp-send-release: -1 (default)
ipv6.routed-dns: -1 (default)
ipv6.ignore-auto-routes: no
ipv6.ignore-auto-dns: no
ipv6.never-default: no
ipv6.may-fail: yes
ipv6.required-timeout: -1 (default)
ipv6.ip6-privacy: -1 (default)
ipv6.temp-valid-lifetime: 0 (default)
ipv6.temp-preferred-lifetime: 0 (default)
ipv6.addr-gen-mode: default
ipv6.ra-timeout: 0 (default)
ipv6.mtu: auto
ipv6.dhcp-pd-hint: --
ipv6.dhcp-duid: --
ipv6.dhcp-iaid: --
ipv6.dhcp-timeout: 0 (default)
ipv6.dhcp-send-hostname-deprecated: yes
ipv6.dhcp-send-hostname: -1 (default)
ipv6.dhcp-hostname: --
ipv6.dhcp-hostname-flags: 0x0 (none)
ipv6.auto-route-ext-gw: -1 (default)
ipv6.token: --
proxy.method: none
proxy.browser-only: no
proxy.pac-url: --
proxy.pac-script: --
GENERAL.NAME: Wired connection 1
GENERAL.UUID: 5745e71f-976c-317c-a85c-d26cb15f318d
GENERAL.DEVICES: enp1s0
GENERAL.IP-IFACE: enp1s0
GENERAL.STATE: activated
GENERAL.DEFAULT: yes
GENERAL.DEFAULT6: yes
GENERAL.SPEC-OBJECT: --
GENERAL.VPN: no
GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/ActiveConnection/7
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/Settings/3
GENERAL.ZONE: --
GENERAL.MASTER-PATH: --
IP4.ADDRESS[1]: 10.0.0.160/24
IP4.GATEWAY: 10.0.0.1
IP4.ROUTE[1]: dst = 10.0.0.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 10.0.0.1, mt = 100
IP4.DNS[1]: 8.8.8.8
IP4.DNS[2]: 8.8.4.4
DHCP4.OPTION[1]: broadcast_address = 10.0.0.255
DHCP4.OPTION[2]: dhcp_client_identifier = 01:b0:41:6f:0e:4f:21
DHCP4.OPTION[3]: dhcp_lease_time = 172800
DHCP4.OPTION[4]: dhcp_server_identifier = 10.0.0.1
DHCP4.OPTION[5]: domain_name_servers = 75.75.75.75 75.75.76.76
DHCP4.OPTION[6]: expiry = 1749961159
DHCP4.OPTION[7]: host_name = durango
DHCP4.OPTION[8]: ip_address = 10.0.0.160
DHCP4.OPTION[9]: next_server = 10.0.0.1
DHCP4.OPTION[10]: requested_broadcast_address = 1
DHCP4.OPTION[11]: requested_domain_name = 1
DHCP4.OPTION[12]: requested_domain_name_servers = 1
DHCP4.OPTION[13]: requested_domain_search = 1
DHCP4.OPTION[14]: requested_host_name = 1
DHCP4.OPTION[15]: requested_interface_mtu = 1
DHCP4.OPTION[16]: requested_ms_classless_static_routes = 1
DHCP4.OPTION[17]: requested_nis_domain = 1
DHCP4.OPTION[18]: requested_nis_servers = 1
DHCP4.OPTION[19]: requested_ntp_servers = 1
DHCP4.OPTION[20]: requested_rfc3442_classless_static_routes = 1
DHCP4.OPTION[21]: requested_root_path = 1
DHCP4.OPTION[22]: requested_routers = 1
DHCP4.OPTION[23]: requested_static_routes = 1
DHCP4.OPTION[24]: requested_subnet_mask = 1
DHCP4.OPTION[25]: requested_time_offset = 1
DHCP4.OPTION[26]: requested_wpad = 1
DHCP4.OPTION[27]: routers = 10.0.0.1
DHCP4.OPTION[28]: subnet_mask = 255.255.255.0
IP6.ADDRESS[1]: 2601:8c0:385:8650::339d/128
IP6.ADDRESS[2]: 2601:8c0:385:8650:34fb:83f6:84f1:7c1b/64
IP6.ADDRESS[3]: fe80::7d61:df6a:413f:1380/64
IP6.GATEWAY: fe80::4abd:ceff:fe4c:2832
IP6.ROUTE[1]: dst = 2601:8c0:385:8650::339d/128, nh = ::, mt = 100
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 1024
IP6.ROUTE[3]: dst = 2601:8c0:385:8650::/64, nh = ::, mt = 100
IP6.ROUTE[4]: dst = ::/0, nh = fe80::4abd:ceff:fe4c:2832, mt = 100
IP6.DNS[1]: 2001:558:feed::1
IP6.DNS[2]: 2001:558:feed::2
DHCP6.OPTION[1]: dhcp6_client_id = 00:04:c2:28:95:46:b3:5c:f3:22:8d:80:f5:d4:7c:2f:95:ba
DHCP6.OPTION[2]: dhcp6_name_servers = 2001:558:feed::1 2001:558:feed::2
DHCP6.OPTION[3]: iaid = 56:50:4d:98
DHCP6.OPTION[4]: ip6_address = 2601:8c0:385:8650::339d$ nmcli connection show br0
connection.id: br0
connection.uuid: b550fcac-1fa9-4601-9ffb-b0d14c5bb2b7
connection.stable-id: --
connection.type: bridge
connection.interface-name: br0
connection.autoconnect: no
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.multi-connect: 0 (default)
connection.auth-retries: -1
connection.timestamp: 1749615524
connection.permissions: --
connection.zone: --
connection.controller: --
connection.master: --
connection.slave-type: --
connection.port-type: --
connection.autoconnect-slaves: -1 (default)
connection.autoconnect-ports: -1 (default)
connection.down-on-poweroff: -1 (default)
connection.secondaries: --
connection.gateway-ping-timeout: 0
connection.ip-ping-timeout: 0
connection.ip-ping-addresses: --
connection.ip-ping-addresses-require-all:-1 (default)
connection.metered: unknown
connection.lldp: default
connection.mdns: -1 (default)
connection.llmnr: -1 (default)
connection.dns-over-tls: -1 (default)
connection.mptcp-flags: 0x0 (default)
connection.wait-device-timeout: -1
connection.wait-activation-delay: -1
802-3-ethernet.port: --
802-3-ethernet.speed: 0
802-3-ethernet.duplex: --
802-3-ethernet.auto-negotiate: no
802-3-ethernet.mac-address: --
802-3-ethernet.cloned-mac-address: --
802-3-ethernet.generate-mac-address-mask:--
802-3-ethernet.mac-address-denylist: --
802-3-ethernet.mtu: auto
802-3-ethernet.s390-subchannels: --
802-3-ethernet.s390-nettype: --
802-3-ethernet.s390-options: --
802-3-ethernet.wake-on-lan: default
802-3-ethernet.wake-on-lan-password: --
802-3-ethernet.accept-all-mac-addresses:-1 (default)
ipv4.method: manual
ipv4.dns: --
ipv4.dns-search: --
ipv4.dns-options: --
ipv4.dns-priority: 0
ipv4.addresses: 10.0.0.160/24
ipv4.gateway: 10.0.0.1
ipv4.routes: --
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.routing-rules: --
ipv4.replace-local-rule: -1 (default)
ipv4.dhcp-send-release: -1 (default)
ipv4.routed-dns: -1 (default)
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-iaid: --
ipv4.dhcp-dscp: --
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname-deprecated: yes
ipv4.dhcp-send-hostname: -1 (default)
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.dhcp-hostname-flags: 0x0 (none)
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.required-timeout: -1 (default)
ipv4.dad-timeout: -1 (default)
ipv4.dhcp-vendor-class-identifier: --
ipv4.dhcp-ipv6-only-preferred: -1 (default)
ipv4.link-local: 0 (default)
ipv4.dhcp-reject-servers: --
ipv4.auto-route-ext-gw: -1 (default)
ipv4.shared-dhcp-range: --
ipv4.shared-dhcp-lease-time: 0 (default)
ipv6.method: link-local
ipv6.dns: --
ipv6.dns-search: --
ipv6.dns-options: --
ipv6.dns-priority: 0
ipv6.addresses: --
ipv6.gateway: --
ipv6.routes: --
ipv6.route-metric: -1
ipv6.route-table: 0 (unspec)
ipv6.routing-rules: --
ipv6.replace-local-rule: -1 (default)
ipv6.dhcp-send-release: -1 (default)
ipv6.routed-dns: -1 (default)
ipv6.ignore-auto-routes: no
ipv6.ignore-auto-dns: no
ipv6.never-default: no
ipv6.may-fail: yes
ipv6.required-timeout: -1 (default)
ipv6.ip6-privacy: -1 (default)
ipv6.temp-valid-lifetime: 0 (default)
ipv6.temp-preferred-lifetime: 0 (default)
ipv6.addr-gen-mode: default
ipv6.ra-timeout: 0 (default)
ipv6.mtu: auto
ipv6.dhcp-pd-hint: --
ipv6.dhcp-duid: --
ipv6.dhcp-iaid: --
ipv6.dhcp-timeout: 0 (default)
ipv6.dhcp-send-hostname-deprecated: yes
ipv6.dhcp-send-hostname: -1 (default)
ipv6.dhcp-hostname: --
ipv6.dhcp-hostname-flags: 0x0 (none)
ipv6.auto-route-ext-gw: -1 (default)
ipv6.token: --
bridge.mac-address: --
bridge.stp: no
bridge.priority: 32768
bridge.forward-delay: 15
bridge.hello-time: 2
bridge.max-age: 20
bridge.ageing-time: 299
bridge.group-forward-mask: 0
bridge.multicast-last-member-interval: 99
bridge.multicast-membership-interval: 25999
bridge.multicast-querier-interval: 25499
bridge.multicast-query-interval: 12499
bridge.multicast-query-response-interval:999
bridge.multicast-snooping: yes
bridge.multicast-startup-query-interval:3124
bridge.vlan-filtering: no
bridge.vlan-default-pvid: 1
bridge.vlans: --
proxy.method: none
proxy.browser-only: no
proxy.pac-url: --
proxy.pac-script: --
GENERAL.NAME: br0
GENERAL.UUID: b550fcac-1fa9-4601-9ffb-b0d14c5bb2b7
GENERAL.DEVICES: br0
GENERAL.IP-IFACE: br0
GENERAL.STATE: activated
GENERAL.DEFAULT: no
GENERAL.DEFAULT6: no
GENERAL.SPEC-OBJECT: --
GENERAL.VPN: no
GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/ActiveConnection/3
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/Settings/5
GENERAL.ZONE: --
GENERAL.MASTER-PATH: --
IP4.ADDRESS[1]: 10.0.0.160/24
IP4.GATEWAY: 10.0.0.1
IP4.ROUTE[1]: dst = 10.0.0.0/24, nh = 0.0.0.0, mt = 0
IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 10.0.0.1, mt = 0
IP6.ADDRESS[1]: fe80::e4a6:d3ff:fefd:3d18/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 256$ nmcli connection show vnet0
connection.id: vnet0
connection.uuid: d2c0ca6a-db4f-47e8-a3d4-76c15597d77d
connection.stable-id: --
connection.type: tun
connection.interface-name: vnet0
connection.autoconnect: no
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.multi-connect: 0 (default)
connection.auth-retries: -1
connection.timestamp: 1749615531
connection.permissions: --
connection.zone: --
connection.controller: b550fcac-1fa9-4601-9ffb-b0d14c5bb2b7
connection.master: b550fcac-1fa9-4601-9ffb-b0d14c5bb2b7
connection.slave-type: bridge
connection.port-type: bridge
connection.autoconnect-slaves: -1 (default)
connection.autoconnect-ports: -1 (default)
connection.down-on-poweroff: -1 (default)
connection.secondaries: --
connection.gateway-ping-timeout: 0
connection.ip-ping-timeout: 0
connection.ip-ping-addresses: --
connection.ip-ping-addresses-require-all:-1 (default)
connection.metered: unknown
connection.lldp: default
connection.mdns: -1 (default)
connection.llmnr: -1 (default)
connection.dns-over-tls: -1 (default)
connection.mptcp-flags: 0x0 (default)
connection.wait-device-timeout: -1
connection.wait-activation-delay: -1
bridge-port.priority: 32
bridge-port.path-cost: 2
bridge-port.hairpin-mode: no
bridge-port.vlans: --
tun.mode: 2 (tap)
tun.owner: --
tun.group: --
tun.pi: no
tun.vnet-hdr: yes
tun.multi-queue: no
GENERAL.NAME: vnet0
GENERAL.UUID: d2c0ca6a-db4f-47e8-a3d4-76c15597d77d
GENERAL.DEVICES: vnet0
GENERAL.IP-IFACE: vnet0
GENERAL.STATE: activated
GENERAL.DEFAULT: no
GENERAL.DEFAULT6: no
GENERAL.SPEC-OBJECT: --
GENERAL.VPN: no
GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/ActiveConnection/4
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/Settings/6
GENERAL.ZONE: --
GENERAL.MASTER-PATH: /org/freedesktop/NetworkManager/Devices/4
IP4.GATEWAY: --
IP6.ADDRESS[1]: fe80::fc54:ff:fe09:cd9a/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 256Last edited by michael8rown (2025-06-13 21:39:27)
Offline
#2 2025-06-13 20:21:38
- seth
- Member
- Registered: 2012-09-03
- Posts: 64,524
Re: [Solved] Random network disconnects
I can get out to websites like archlinux.org and google.com from the server. Other websites, such as goodreads.com and duckduckgo.com are unavailable
You're losing the IPv4 lease (check "dig -t AAAA" on the affected domains)
Jun 10 22:17:48 durango NetworkManager[830]: <info> [1749615468.8435] dhcp4 (enp1s0): state changed new lease, address=10.0.0.160
Jun 10 22:17:48 durango NetworkManager[830]: <info> [1749615468.8440] policy: set 'Wired connection 1' (enp1s0) as default for IPv4 routing and DNS
Jun 10 22:17:48 durango NetworkManager[830]: <info> [1749615468.8778] device (enp1s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jun 10 22:17:48 durango NetworkManager[830]: <info> [1749615468.8796] device (enp1s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jun 10 22:17:48 durango NetworkManager[830]: <info> [1749615468.8797] device (enp1s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jun 10 22:17:48 durango NetworkManager[830]: <info> [1749615468.8801] manager: NetworkManager state is now CONNECTED_SITEyou're getting a local lease, but NM cannot ping ping.archlinux.org
Jun 11 05:00:02 durango kernel: PM: suspend exit
Jun 11 05:00:02 durango systemd-resolved[443]: Clock change detected. Flushing caches.
Jun 11 05:00:02 durango bluetoothd[825]: Controller resume with wake event 0x0
Jun 11 05:00:02 durango systemd[1]: Started Verify integrity of password and group files.
Jun 11 05:00:02 durango systemd[1]: goToSleep.service: Deactivated successfully.
Jun 11 05:00:02 durango systemd[1]: Finished Put the system to sleep.
Jun 11 05:00:02 durango root[2737]: ACPI group/action undefined: jack/lineout / LINEOUT
Jun 11 05:00:02 durango root[2740]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Jun 11 05:00:02 durango systemd[1]: shadow.service: Deactivated successfully.
Jun 11 05:00:02 durango root[2749]: ACPI group/action undefined: jack/microphone / MICROPHONE
Jun 11 05:00:02 durango root[2751]: ACPI group/action undefined: jack/lineout / LINEOUT
Jun 11 05:00:02 durango kernel: r8169 0000:01:00.0 enp1s0: Link is Up - 100Mbps/Full - flow control rx/tx
Jun 11 05:00:02 durango kernel: br0: port 1(enp1s0) entered blocking state
Jun 11 05:00:02 durango kernel: br0: port 1(enp1s0) entered forwarding state
Jun 11 05:00:02 durango NetworkManager[830]: <info> [1749639602.9123] device (enp1s0): carrier: link connected
Jun 11 05:00:32 durango root[2788]: ACPI group/action undefined: jack/lineout / LINEOUT
Jun 11 05:00:32 durango root[2790]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Jun 11 05:02:18 durango NetworkManager[830]: <info> [1749639738.5078] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 11 05:02:18 durango systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 11 05:02:18 durango systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 11 05:02:22 durango systemd-resolved[443]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 8.8.4.4.
Jun 11 05:02:25 durango systemd-resolved[443]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 8.8.8.8.After the system wakes up you get a global connection.
Jun 12 22:15:22 durango vmCtrl[17742]: Domain 'debian12' suspended
Jun 12 22:15:22 durango systemd[1]: vmCtrl.service: Deactivated successfully.
Jun 12 22:15:22 durango systemd[1]: Finished Suspend/Resume debian12.
============ here the problems start after > 2m complete silence ===================
Jun 12 22:17:48 durango NetworkManager[830]: <info> [1749788268.6527] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Jun 12 22:17:48 durango NetworkManager[830]: <info> [1749788268.6528] dhcp4 (enp1s0): state changed no leaseNM starts a dhcp request out of nowhere which
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.0494] device (enp1s0): state change: activated -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.0500] device (enp1s0): released from controller device br0
Jun 12 22:18:34 durango NetworkManager[830]: <warn> [1749788314.0501] device (enp1s0): Activation: failed for connection 'Wired connection 1'
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.0506] device (enp1s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jun 12 22:18:34 durango systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.0881] dhcp4 (enp1s0): canceled DHCP transaction
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.0882] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.0882] dhcp4 (enp1s0): state changed no lease
Jun 12 22:18:34 durango systemd-resolved[443]: enp1s0: Bus client set default route setting: no
Jun 12 22:18:34 durango systemd-resolved[443]: enp1s0: Bus client reset DNS server list.
Jun 12 22:18:34 durango systemd[1]: Started Network Manager Script Dispatcher Service.fails after 45s so
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1563] policy: auto-activating connection 'Wired connection 1' (5745e71f-976c-317c-a85c-d26cb15f318d)
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1569] device (enp1s0): Activation: starting connection 'enp1s0' (3903eb4a-41d7-4c6b-a9df-2668147fcb0d)
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1570] device (enp1s0): disconnecting for new activation request.
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1571] device (enp1s0): state change: disconnected -> deactivating (reason 'new-activation', managed-type: 'full')
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1684] device (enp1s0): state change: deactivating -> disconnected (reason 'new-activation', managed-type: 'full')
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1693] device (enp1s0): Activation: starting connection 'Wired connection 1' (5745e71f-976c-317c-a85c-d26cb15f318d)
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1700] device (enp1s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1701] manager: NetworkManager state is now CONNECTING
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1702] device (enp1s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1791] device (enp1s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1791] device (br0): bridge port enp1s0 was attached
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1791] device (enp1s0): Activation: connection 'Wired connection 1' attached as port, continuing activation
Jun 12 22:18:34 durango NetworkManager[830]: <info> [1749788314.1797] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)it attempts a reconnect
Jun 12 22:18:34 durango systemd-resolved[443]: enp1s0: Bus client set default route setting: yes
Jun 12 22:18:34 durango systemd-resolved[443]: enp1s0: Bus client set DNS server list to: 8.8.8.8, 8.8.4.4
Jun 12 22:18:44 durango systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.0491] device (enp1s0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.0495] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.0505] device (br0): detached bridge port enp1s0
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.0506] device (enp1s0): released from controller device br0
Jun 12 22:19:19 durango NetworkManager[830]: <warn> [1749788359.0507] device (enp1s0): Activation: failed for connection 'Wired connection 1'
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.0510] device (enp1s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')which despite the "CONNECTED_GLOBAL" fails
Jun 12 22:19:19 durango kernel: r8169 0000:01:00.0 enp1s0: left allmulticast mode
Jun 12 22:19:19 durango kernel: r8169 0000:01:00.0 enp1s0: left promiscuous mode
Jun 12 22:19:19 durango kernel: br0: port 1(enp1s0) entered disabled state
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.0948] dhcp4 (enp1s0): canceled DHCP transaction
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.0949] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.0949] dhcp4 (enp1s0): state changed no lease
Jun 12 22:19:19 durango systemd-resolved[443]: enp1s0: Bus client set default route setting: no
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.1267] policy: auto-activating connection 'Wired connection 1' (5745e71f-976c-317c-a85c-d26cb15f318d)
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.1270] device (enp1s0): Activation: starting connection 'Wired connection 1' (5745e71f-976c-317c-a85c-d26cb15f318d)
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.1270] device (enp1s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.1271] manager: NetworkManager state is now CONNECTING
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.1272] device (enp1s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.1362] device (enp1s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.1367] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Jun 12 22:19:19 durango systemd-resolved[443]: enp1s0: Bus client set default route setting: yes
Jun 12 22:19:19 durango systemd-resolved[443]: enp1s0: Bus client set DNS server list to: 8.8.8.8, 8.8.4.4
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.1620] dhcp4 (enp1s0): state changed new lease, address=10.0.0.160, acd pending
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.3415] dhcp4 (enp1s0): state changed new lease, address=10.0.0.160
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.3427] policy: set 'Wired connection 1' (enp1s0) as default for IPv4 routing and DNS
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.3638] device (enp1s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jun 12 22:19:19 durango systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 12 22:19:19 durango systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.4222] device (enp1s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.4223] device (enp1s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.4225] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 12 22:19:19 durango NetworkManager[830]: <info> [1749788359.4227] device (enp1s0): Activation: successful, device activated.so try once more and at this point you should™? have an IPv4 lease again.
Jun 12 22:19:20 durango NetworkManager[830]: <info> [1749788360.8341] dhcp6 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Jun 12 22:19:20 durango NetworkManager[830]: <info> [1749788360.8355] policy: set 'Wired connection 1' (enp1s0) as default for IPv6 routing and DNS
Jun 12 22:19:20 durango systemd-resolved[443]: enp1s0: Bus client set DNS server list to: 8.8.8.8, 8.8.4.4, 2001:558:feed::1, 2001:558:feed::2
Jun 12 22:19:20 durango NetworkManager[830]: <info> [1749788360.8467] dhcp6 (enp1s0): state changed new lease, address=2601:8c0:385:8650::339d
Jun 12 22:19:29 durango systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.and IPv6
Part of the action is probably your manula intervention, but the problem seems to start when NM attempts a re-lease after 41h and 13 minutes and your dhcp server (router?) does not respond.
The Arch webserver has a static IP of 10.0.0.160 and the Debian VM has a static IP of 10.0.0.42.
===>>> so why is there any dhcp request itfp?
If that's actually intended
a) what's the lease time for the server (configured in the dhcp server/router)?
b) You could try to replace the dhcp client, https://wiki.archlinux.org/title/Networ … HCP_client - you also might want to change the ID method (clientid/duid)
c) does the debian VM issue dhcp requests as well?
Offline
#3 2025-06-13 21:38:43
- michael8rown
- Member
- Registered: 2021-08-25
- Posts: 27
Re: [Solved] Random network disconnects
Thanks, seth. I ended up getting it back up without rebooting anything. Your question
===>>> so why is there any dhcp request itfp?
prompted me to look at the wired connection settings in GNOME settings. Sure enough, IPv4 was set to "Automatic (DHCP)". I thought I had everything configured to be manual (static ip), so I have no idea why this is getting bumped to Automatic.
I'm not exactly sure which one of these steps worked to get it back up, but here's what I did:
In GNOME settings, I switched the wired connection back to manual and set the ip/netmask/gateway to what I expect them to be.
I restarted NetworkManager.
I pinged 10.0.0.1, but still nothing.
I ran nm-connection-editor as non-root and edited both the Wired Connection 1 connection and the br0 connection, setting both to "manual" ipv4 and entering the valid ip/netmask/gateway.
I restarted NetworkManager again.
I pinged 10.0.0.1 and I finally got a response.
My guess is, the real fix was in using nm-connection-editor to set ipv4 back to manual (?).
I still don't understand why dhcp was kicking in in the first place because I thought I had it set to manual. But maybe when I moved and got a new ISP I adjusted something that started causing this. Hopefully now that I've deliberately set it back to manual with the static ip entered it will stay that way.
Thanks again!
Offline
Pages: 1