You are not logged in.

Pages: 1

#1 2021-09-22 07:01:05

thecodingowl
Member
Registered: 2021-09-11
Posts: 6

[SOLVED] Experiencing wireless network crashes

Hi,

I have a strange problem with my wireless network on one of my installations of arch linux in combination with NetworkManager.
The problem seem to appear on my wireless connection only. I had the machine connected via cable and have not experienced the issue.
On the other side, the issue persists when I change hardware. I changed to multiple intel chipsets and an Atheros, I even swapped the harddrive into a completely different machine, but this had no effect.
I can not detect any entries related to this issue in the logs, so it is really hard for me to figure out what exactly happens here.
The crash is happening in the following way: All network activity over the wifi interface report a "Temporary issue in name resolution", doesn't matter if browser, file operations or ping. I can "fix" the issue either by restarting NetworkManager by 'nmcli networking down/up' or by just "klicking" on the wifi network in the Gnome UI, triggering NetworkManager to reconnect to the network. The UI also reports that the Network is connected, but there is no Internet, but the router does not recognize the PC after the connection crashed.

I am really lost now, because I tried to fix this issue with multiple configuration changes, but nothing worked.
I already tried adding '11n_disable' and 'bt_coex_active' from the issues section of https://wiki.archlinux.org/title/Networ … less#Intel, but since I changed hardware and tried with an Atheros and Intel cards without BT, it was to no avail.
Since this is a work machine, I have multiple VPNs, one of them is a GlobalProtect VPN which required their aweful proprietary software. I removed that for the very first measure against the issue, but I can not guarantee that the software removed itself completely.
Maybe I am overlooking something here, but I am pretty sure this issue is connected to my configuration.

I collected some infos after the last crash, please let me know if I can provide any more info:

systemctl list-unit-files --state=enabled

UNIT FILE                          STATE   VENDOR PRESET
cups.path                          enabled disabled     
bluetooth.service                  enabled disabled     
cups.service                       enabled disabled     
gdm.service                        enabled disabled     
getty@.service                     enabled enabled      
NetworkManager-dispatcher.service  enabled disabled     
NetworkManager-wait-online.service enabled disabled     
NetworkManager.service             enabled disabled     
systemd-homed-activate.service     enabled disabled     
systemd-homed.service              enabled enabled      
systemd-timesyncd.service          enabled enabled      
cups.socket                        enabled disabled     
systemd-userdbd.socket             enabled enabled      
remote-fs.target                   enabled enabled      
pamac-cleancache.timer             enabled disabled

lshw -C network

  *-network                 
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: enp3s0
       version: 06
       serial: d4:3d:7e:38:27:d0
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=5.14.2-arch1-2 firmware=rtl8168e-3_0.0.4 03/27/12 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:17 ioport:d000(size=256) memory:f7204000-f7204fff memory:f7200000-f7203fff
  *-network
       description: Wireless interface
       product: AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn]
       vendor: Qualcomm Atheros
       physical id: 1
       bus info: pci@0000:05:01.0
       logical name: wlp5s1
       version: 01
       serial: 54:e6:fc:d7:e0:43
       width: 32 bits
       clock: 66MHz
       capabilities: bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath9k driverversion=5.14.2-arch1-2 firmware=N/A ip=192.168.178.32 latency=168 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:16 memory:f7100000-f710ffff

systemctl status NetworkManager.service

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Wed 2021-09-22 07:47:40 CEST; 42min ago
       Docs: man:NetworkManager(8)
   Main PID: 527 (NetworkManager)
      Tasks: 3 (limit: 19113)
     Memory: 17.9M
        CPU: 583ms
     CGroup: /system.slice/NetworkManager.service
             └─527 /usr/bin/NetworkManager --no-daemon

Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4736] device (wlp5s1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4738] device (wlp5s1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4743] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4747] manager: NetworkManager state is now CONNECTED_SITE
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4748] policy: set 'Ditscheid' (wlp5s1) as default for IPv4 routing and DNS
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4819] device (wlp5s1): Activation: successful, device activated.
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.6550] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 22 08:24:16 arbeitsrechner NetworkManager[527]: <info>  [1632291856.0406] dhcp6 (wlp5s1): activation: beginning transaction (timeout in 45 seconds)
Sep 22 08:24:16 arbeitsrechner NetworkManager[527]: <info>  [1632291856.0413] policy: set 'Ditscheid' (wlp5s1) as default for IPv6 routing and DNS
Sep 22 08:24:16 arbeitsrechner NetworkManager[527]: <info>  [1632291856.0565] dhcp6 (wlp5s1): state changed unknown -> bound

journalctl _PID=527

-- Boot af2bf355add74dc5985bbad9778943fb --
Feb 09 10:35:26 archlinux systemd-journald[527]: Journal started
Feb 09 10:35:26 archlinux systemd-journald[527]: Runtime Journal (/run/log/journal/9da90ddd647e45329cbe67c02e88d754) is 8.0M, max 634.6M, 626.6M free.
Feb 09 10:35:26 archlinux systemd-journald[527]: Time spent on flushing to /var/log/journal/9da90ddd647e45329cbe67c02e88d754 is 132.125ms for 1672 entries.
...skipping...
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.2027] audit: op="connection-activate" uuid="e41b4beb-5edf-474c-b071-06193ea9dfa6" name="Ditscheid" pid=9255 uid=1000 result="success"
Sep 22 08:24:09 arbeitsrechner audit[527]: USYS_CONFIG pid=527 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=e41b4beb-5edf-474c-b071-06193ea9dfa6 name="Ditscheid" pid=9255 uid=1000 result=success exe="/usr/bin/Net>
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.3673] device (wlp5s1): supplicant interface state: completed -> disconnected
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.3673] device (p2p-dev-wlp5s1): supplicant management interface state: completed -> disconnected
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.3674] device (wlp5s1): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.3800] dhcp4 (wlp5s1): canceled DHCP transaction
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.3800] dhcp4 (wlp5s1): state changed bound -> terminated
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.3803] dhcp6 (wlp5s1): canceled DHCP transaction
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.3803] dhcp6 (wlp5s1): state changed bound -> terminated
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.3937] device (wlp5s1): set-hw-addr: set MAC address to 0A:B3:83:90:70:25 (scanning)
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.4020] manager: NetworkManager state is now DISCONNECTED
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.4022] device (wlp5s1): Activation: starting connection 'Ditscheid' (e41b4beb-5edf-474c-b071-06193ea9dfa6)
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.4030] device (wlp5s1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.4031] manager: NetworkManager state is now CONNECTING
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.4075] device (wlp5s1): set-hw-addr: reset MAC address to 54:E6:FC:D7:E0:43 (preserve)
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.4192] device (wlp5s1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.4195] device (wlp5s1): Activation: (wifi) access point 'Ditscheid' has security, but secrets are required.
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.4195] device (wlp5s1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:09 arbeitsrechner NetworkManager[527]: <info>  [1632291849.4196] sup-iface[968365f1a9dfcb6b,0,wlp5s1]: wps: type pbc start...
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2097] device (wlp5s1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2100] device (wlp5s1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2101] device (wlp5s1): Activation: (wifi) connection 'Ditscheid' has security, and secrets exist.  No new secrets needed.
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2101] Config: added 'ssid' value 'Ditscheid'
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2102] Config: added 'scan_ssid' value '1'
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2102] Config: added 'bgscan' value 'simple:30:-70:86400'
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2102] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2102] Config: added 'auth_alg' value 'OPEN'
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2102] Config: added 'psk' value '<hidden>'
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2178] device (wlp5s1): supplicant interface state: disconnected -> scanning
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2178] device (p2p-dev-wlp5s1): supplicant management interface state: disconnected -> scanning
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2435] device (wlp5s1): supplicant interface state: scanning -> authenticating
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.2436] device (p2p-dev-wlp5s1): supplicant management interface state: scanning -> authenticating
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.3799] device (wlp5s1): supplicant interface state: authenticating -> associating
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.3799] device (p2p-dev-wlp5s1): supplicant management interface state: authenticating -> associating
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.3910] device (wlp5s1): supplicant interface state: associating -> associated
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.3910] device (p2p-dev-wlp5s1): supplicant management interface state: associating -> associated
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4013] device (wlp5s1): supplicant interface state: associated -> 4way_handshake
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4014] device (p2p-dev-wlp5s1): supplicant management interface state: associated -> 4way_handshake
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4452] device (wlp5s1): supplicant interface state: 4way_handshake -> completed
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4452] device (wlp5s1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Ditscheid"
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4453] device (p2p-dev-wlp5s1): supplicant management interface state: 4way_handshake -> completed
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4454] device (wlp5s1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4457] dhcp4 (wlp5s1): activation: beginning transaction (timeout in 45 seconds)
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4681] dhcp4 (wlp5s1): state changed unknown -> bound, address=192.168.178.32
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4689] device (wlp5s1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4736] device (wlp5s1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4738] device (wlp5s1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4743] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4747] manager: NetworkManager state is now CONNECTED_SITE
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4748] policy: set 'Ditscheid' (wlp5s1) as default for IPv4 routing and DNS
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.4819] device (wlp5s1): Activation: successful, device activated.
Sep 22 08:24:14 arbeitsrechner NetworkManager[527]: <info>  [1632291854.6550] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 22 08:24:16 arbeitsrechner NetworkManager[527]: <info>  [1632291856.0406] dhcp6 (wlp5s1): activation: beginning transaction (timeout in 45 seconds)
Sep 22 08:24:16 arbeitsrechner NetworkManager[527]: <info>  [1632291856.0413] policy: set 'Ditscheid' (wlp5s1) as default for IPv6 routing and DNS
Sep 22 08:24:16 arbeitsrechner NetworkManager[527]: <info>  [1632291856.0565] dhcp6 (wlp5s1): state changed unknown -> bound

dmesg

[ 1233.509535] audit: type=1100 audit(1632290759.286:208): pid=6663 uid=1000 auid=1000 ses=5 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1233.516200] audit: type=1101 audit(1632290759.292:209): pid=6663 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1233.517653] audit: type=1110 audit(1632290759.292:210): pid=6663 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1233.520819] audit: type=1105 audit(1632290759.296:211): pid=6663 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1233.523448] audit: type=1106 audit(1632290759.299:212): pid=6663 uid=1000 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1233.523663] audit: type=1104 audit(1632290759.299:213): pid=6663 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1233.547696] audit: type=1101 audit(1632290759.322:214): pid=6673 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1233.549575] audit: type=1110 audit(1632290759.326:215): pid=6673 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1233.551938] audit: type=1105 audit(1632290759.326:216): pid=6673 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1233.555901] audit: type=1106 audit(1632290759.332:217): pid=6673 uid=1000 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1242.750699] SUPR0GipMap: fGetGipCpu=0x1b
[ 1242.870857] vboxdrv: 00000000c2ab3f6f VMMR0.r0
[ 1243.119141] vboxdrv: 00000000777d9046 VBoxDDR0.r0
[ 1243.220965] VBoxNetFlt: attached to 'vboxnet3' / 0a:00:27:00:00:03
[ 1243.221241] IPv6: ADDRCONF(NETDEV_CHANGE): vboxnet3: link becomes ready
[ 1243.251927] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[ 1243.278572] device vboxnet3 entered promiscuous mode
[ 1243.278601] kauditd_printk_skb: 1 callbacks suppressed
[ 1243.278602] audit: type=1700 audit(1632290769.052:219): dev=vboxnet3 prom=256 old_prom=0 auid=1000 uid=1000 gid=1000 ses=5
[ 1243.281355] audit: type=1300 audit(1632290769.052:219): arch=c000003e syscall=16 success=yes exit=0 a0=7 a1=c0485687 a2=7f6c384c5b90 a3=0 items=0 ppid=6711 pid=7067 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=(none) ses=5 comm="EMT-0" exe="/usr/lib/virtualbox/VBoxHeadless" key=(null)
[ 1243.282054] audit: type=1327 audit(1632290769.052:219): proctitle=2F7573722F6C69622F7669727475616C626F782F56426F78486561646C657373002D2D636F6D6D656E74006D6B2D6F6E6C696E65002D2D7374617274766D0035396539363835392D366335322D343465392D613235342D646539656163313562326239002D2D7672646500636F6E666967
[ 1279.519388] audit: type=1101 audit(1632290805.292:220): pid=7862 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.520370] audit: type=1110 audit(1632290805.295:221): pid=7862 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.521699] audit: type=1105 audit(1632290805.295:222): pid=7862 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.524882] audit: type=1106 audit(1632290805.298:223): pid=7862 uid=1000 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.524887] audit: type=1104 audit(1632290805.298:224): pid=7862 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.561150] audit: type=1101 audit(1632290805.335:225): pid=7864 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.562433] audit: type=1110 audit(1632290805.335:226): pid=7864 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.563889] audit: type=1105 audit(1632290805.338:227): pid=7864 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.569845] audit: type=1106 audit(1632290805.338:228): pid=7864 uid=1000 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.569852] audit: type=1104 audit(1632290805.338:229): pid=7864 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 1279.887111] RPC: Registered named UNIX socket transport module.
[ 1279.887116] RPC: Registered udp transport module.
[ 1279.887116] RPC: Registered tcp transport module.
[ 1279.887117] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1279.945803] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 1280.065699] RPC: Registered rdma transport module.
[ 1280.065703] RPC: Registered rdma backchannel transport module.
[ 1280.181616] NFSD: Using nfsdcld client tracking operations.
[ 1280.181622] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000098)
[ 2276.928904] kauditd_printk_skb: 24 callbacks suppressed
[ 2276.928906] audit: type=1130 audit(1632291802.697:254): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2287.022979] audit: type=1131 audit(1632291812.790:255): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2323.431522] audit: type=1111 audit(1632291849.197:256): pid=527 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=e41b4beb-5edf-474c-b071-06193ea9dfa6 name="Ditscheid" pid=9255 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[ 2323.450252] audit: type=1130 audit(1632291849.217:257): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2323.451838] wlp5s1: deauthenticating from 2c:91:ab:0c:4c:a7 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 2328.466139] wlp5s1: authenticate with 2c:91:ab:0c:4c:a7
[ 2328.470543] wlp5s1: send auth to 2c:91:ab:0c:4c:a7 (try 1/3)
[ 2328.604536] wlp5s1: send auth to 2c:91:ab:0c:4c:a7 (try 2/3)
[ 2328.607265] wlp5s1: authenticated
[ 2328.607881] wlp5s1: associate with 2c:91:ab:0c:4c:a7 (try 1/3)
[ 2328.613088] wlp5s1: RX AssocResp from 2c:91:ab:0c:4c:a7 (capab=0x1431 status=0 aid=1)
[ 2328.613295] wlp5s1: associated
[ 2328.626794] wlp5s1: Limiting TX power to 20 (20 - 0) dBm as advertised by 2c:91:ab:0c:4c:a7
[ 2328.671333] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s1: link becomes ready
[ 2334.016640] audit: type=1131 audit(1632291859.783:258): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2443.249309] audit: type=1100 audit(1632291969.017:259): pid=9950 uid=1000 auid=1000 ses=5 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[ 2443.250191] audit: type=1101 audit(1632291969.017:260): pid=9950 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[ 2443.250999] audit: type=1110 audit(1632291969.017:261): pid=9950 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[ 2443.252142] audit: type=1105 audit(1632291969.020:262): pid=9950 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[ 2443.885421] audit: type=1106 audit(1632291969.653:263): pid=9950 uid=1000 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[ 2443.885479] audit: type=1104 audit(1632291969.653:264): pid=9950 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[ 2487.753713] audit: type=1101 audit(1632292013.520:265): pid=9982 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[ 2487.754654] audit: type=1110 audit(1632292013.520:266): pid=9982 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[ 2487.755833] audit: type=1105 audit(1632292013.523:267): pid=9982 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'

Last edited by thecodingowl (2021-11-20 15:47:35)

Offline

#2 2021-09-22 07:15:05

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: [SOLVED] Experiencing wireless network crashes

Temporary issue in name resolution"

Can you still ping IPs?

ping 8.8.8.8

I have multiple VPNs, one of them is a GlobalProtect VPN which required their aweful proprietary software. I removed that for the very first measure against the issue, but I can not guarantee

Dos the problem occur w/o *any* VPN?

There was recently an MTU issue w/ strongswan.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2021-09-22 07:54:56

thecodingowl
Member
Registered: 2021-09-11
Posts: 6

Re: [SOLVED] Experiencing wireless network crashes

Wow, I did not expect this quick of an answer :-)

seth wrote:

Temporary issue in name resolution"

Can you still ping IPs?

No, I can't even ping a local IP in my network.
I thought about some kind of DNS being the issue, but since direct IP access is also not possible, I ruled that out for me.

seth wrote:

Temporary issue in name resolution"

ping 8.8.8.8

I have multiple VPNs, one of them is a GlobalProtect VPN which required their aweful proprietary software. I removed that for the very first measure against the issue, but I can not guarantee

Dos the problem occur w/o *any* VPN?

There was recently an MTU issue w/ strongswan.

I have more VPNs, but I tested with disabling all of them.
I only removed the GlobalProtect VPN though. The other VPNs are configured via the NetworkManager GUI. Two are openVPN that worked on another machine without issue and another is an openConnect VPN.

It happened again and I have another cut from the journalctl:

Sep 22 10:25:57 arbeitsrechner wpa_supplicant[667]: wlp5s1: WPA: Group rekeying completed with 2c:91:ab:0c:4c:a7 [GTK=CCMP]
Sep 22 10:27:06 arbeitsrechner audit[28651]: USER_AUTH pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res>
Sep 22 10:27:06 arbeitsrechner kernel: audit: type=1100 audit(1632299226.145:410): pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="kevin" exe="/usr/bin/sudo" hostname=? ad>
Sep 22 10:27:06 arbeitsrechner kernel: audit: type=1101 audit(1632299226.149:411): pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? termina>
Sep 22 10:27:06 arbeitsrechner kernel: audit: type=1110 audit(1632299226.149:412): pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
Sep 22 10:27:06 arbeitsrechner kernel: audit: type=1105 audit(1632299226.152:413): pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? term>
Sep 22 10:27:06 arbeitsrechner audit[28651]: USER_ACCT pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Sep 22 10:27:06 arbeitsrechner audit[28651]: CRED_REFR pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Sep 22 10:27:06 arbeitsrechner audit[28651]: USER_START pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Sep 22 10:27:06 arbeitsrechner sudo[28651]: pam_systemd_home(sudo:account): Not a user managed by systemd-homed: No home for user kevin known
Sep 22 10:27:06 arbeitsrechner sudo[28651]:    kevin : TTY=pts/2 ; PWD=/home/kevin ; USER=root ; COMMAND=/usr/bin/dmesg
Sep 22 10:27:06 arbeitsrechner sudo[28651]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Sep 22 10:27:06 arbeitsrechner sudo[28651]: pam_unix(sudo:session): session closed for user root
Sep 22 10:27:06 arbeitsrechner audit[28651]: USER_END pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Sep 22 10:27:06 arbeitsrechner audit[28651]: CRED_DISP pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Sep 22 10:27:06 arbeitsrechner kernel: audit: type=1106 audit(1632299226.175:414): pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
Sep 22 10:27:06 arbeitsrechner kernel: audit: type=1104 audit(1632299226.175:415): pid=28651 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
Sep 22 10:27:08 arbeitsrechner org.gnome.Polari[3808]: Retrying with irc.dk.quakenet.org:6667
Sep 22 10:27:09 arbeitsrechner gnome-shell[1040]: Can't update stage views actor MetaWindowGroup is on because it needs an allocation.
Sep 22 10:27:09 arbeitsrechner gnome-shell[1040]: Can't update stage views actor MetaWindowActorX11 is on because it needs an allocation.
Sep 22 10:27:09 arbeitsrechner gnome-shell[1040]: Can't update stage views actor MetaSurfaceActorX11 is on because it needs an allocation.
Sep 22 10:27:11 arbeitsrechner discord.desktop[28669]: --2021-09-22 10:27:11--  https://sentry.io/api/146342/minidump/?sentry_key=384ce4413de74fe0be270abe03b2b35a
Sep 22 10:27:11 arbeitsrechner discord.desktop[28669]: SSL_INIT
Sep 22 10:27:11 arbeitsrechner discord.desktop[28669]: CA-Zertifikat »/etc/ssl/certs/ca-certificates.crt« wurde geladen
Sep 22 10:27:21 arbeitsrechner discord.desktop[28669]: Auflösen des Hostnamens sentry.io (sentry.io)… fehlgeschlagen: Die Wartezeit für die Verbindung ist abgelaufen.
Sep 22 10:27:21 arbeitsrechner discord.desktop[28669]: wget: Host-Adresse »sentry.io« kann nicht aufgelöst werden
Sep 22 10:27:21 arbeitsrechner discord.desktop[28668]: Unexpected crash report id length
Sep 22 10:27:21 arbeitsrechner discord.desktop[28668]: Failed to get crash dump id.
Sep 22 10:27:21 arbeitsrechner discord.desktop[28668]: Report Id:
Sep 22 10:27:21 arbeitsrechner discord.desktop[28683]: --2021-09-22 10:27:21--  https://sentry.io/api/146342/minidump/?sentry_key=384ce4413de74fe0be270abe03b2b35a
Sep 22 10:27:21 arbeitsrechner discord.desktop[28683]: SSL_INIT
Sep 22 10:27:21 arbeitsrechner discord.desktop[28683]: CA-Zertifikat »/etc/ssl/certs/ca-certificates.crt« wurde geladen
Sep 22 10:27:22 arbeitsrechner sudo[28686]: pam_systemd_home(sudo:account): Not a user managed by systemd-homed: No home for user kevin known
Sep 22 10:27:22 arbeitsrechner kernel: audit: type=1101 audit(1632299242.935:416): pid=28686 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? termina>
Sep 22 10:27:22 arbeitsrechner kernel: audit: type=1110 audit(1632299242.935:417): pid=28686 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? ad>
Sep 22 10:27:22 arbeitsrechner kernel: audit: type=1105 audit(1632299242.938:418): pid=28686 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? term>
Sep 22 10:27:22 arbeitsrechner audit[28686]: USER_ACCT pid=28686 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="kevin" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Sep 22 10:27:22 arbeitsrechner audit[28686]: CRED_REFR pid=28686 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res>
Sep 22 10:27:22 arbeitsrechner audit[28686]: USER_START pid=28686 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Sep 22 10:27:22 arbeitsrechner sudo[28686]:    kevin : TTY=pts/2 ; PWD=/home/kevin ; USER=root ; COMMAND=/usr/bin/journalctl _PID=527
Sep 22 10:27:22 arbeitsrechner sudo[28686]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Sep 22 10:27:31 arbeitsrechner discord.desktop[28683]: Auflösen des Hostnamens sentry.io (sentry.io)… fehlgeschlagen: Die Wartezeit für die Verbindung ist abgelaufen.
Sep 22 10:27:31 arbeitsrechner discord.desktop[28683]: wget: Host-Adresse »sentry.io« kann nicht aufgelöst werden
Sep 22 10:27:31 arbeitsrechner discord.desktop[28682]: Unexpected crash report id length

The wpa group rekeying happens from time to time and I suspected it to be the issue, but I found nothing fishy about it on the internet and it does not happen consistently before the connection crashes, so I am unsure if it has something to do with the issue at all.

Last edited by thecodingowl (2021-09-22 08:33:09)

Offline

#4 2021-09-22 13:31:48

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: [SOLVED] Experiencing wireless network crashes

Sep 22 10:25:57 arbeitsrechner wpa_supplicant[667]: wlp5s1: WPA: Group rekeying completed with 2c:91:ab:0c:4c:a7 [GTK=CCMP]
…
Sep 22 10:27:06 arbeitsrechner sudo[28651]: pam_systemd_home(sudo:account): Not a user managed by systemd-homed: No home for user kevin known

That's rather suspicious (though there seems no direct issue w/ the re-key itself)
Since you've tried multiple client HW, can you switch the AP and/or disable re-keying there?

You could also try to use iwd (in doubt as NM backend, https://wiki.archlinux.org/title/Networ … Fi_backend )

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2021-09-23 09:44:51

thecodingowl
Member
Registered: 2021-09-11
Posts: 6

Re: [SOLVED] Experiencing wireless network crashes

Hi,

I changed my NM backend to iwd, but appearently nothing changed, but I have new information:

I ran a bunch of ping commands and there are mysterious outcommings:

 kevin  ~  ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 Bytes von 8.8.8.8: icmp_seq=1 ttl=118 Zeit=13.5 ms
64 Bytes von 8.8.8.8: icmp_seq=2 ttl=118 Zeit=15.7 ms
64 Bytes von 8.8.8.8: icmp_seq=3 ttl=118 Zeit=12.3 ms
64 Bytes von 8.8.8.8: icmp_seq=4 ttl=118 Zeit=13.4 ms
64 Bytes von 8.8.8.8: icmp_seq=5 ttl=118 Zeit=11.6 ms
64 Bytes von 8.8.8.8: icmp_seq=6 ttl=118 Zeit=81.0 ms
^C
--- 8.8.8.8 ping statistics ---
6 Pakete übertragen, 6 empfangen, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 11.611/24.598/81.047/25.275 ms

 kevin  ~  ping 192.168.178.1
PING 192.168.178.1 (192.168.178.1) 56(84) bytes of data.
^C
--- 192.168.178.1 ping statistics ---
268 Pakete übertragen, 0 empfangen, 100% packet loss, time 270571ms

 kevin  ~  ping archlinux.org
ping: archlinux.org: Temporärer Fehler bei der Namensauflösung

 kevin  ~  2  ping 95.217.163.246
PING 95.217.163.246 (95.217.163.246) 56(84) bytes of data.
^C
--- 95.217.163.246 ping statistics ---
115 Pakete übertragen, 0 empfangen, 100% packet loss, time 115526ms

 kevin  ~  ping 8.8.8.8 
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 Bytes von 8.8.8.8: icmp_seq=1 ttl=118 Zeit=14.7 ms
64 Bytes von 8.8.8.8: icmp_seq=2 ttl=118 Zeit=11.2 ms
64 Bytes von 8.8.8.8: icmp_seq=3 ttl=118 Zeit=14.4 ms
64 Bytes von 8.8.8.8: icmp_seq=4 ttl=118 Zeit=13.3 ms
^C
--- 8.8.8.8 ping statistics ---
4 Pakete übertragen, 4 empfangen, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 11.170/13.380/14.675/1.384 ms

 kevin  ~  ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
^C
--- 1.1.1.1 ping statistics ---
167 Pakete übertragen, 0 empfangen, 100% packet loss, time 168211ms

As you can see, a ping on archlinux.org results in the message: "Temporary failure in domain name resolve"
A ping to the IP of archlinux.org (95.217.163.246) results in hanging of ping and a 100% package loss.
A ping on 1.1.1.1 results in the same, as well as a ping on my local routers network address (192.168.178.1).
Myseriously, a ping on 8.8.8.8, Googles name server, results in it getting answers totally fine.

I have no clue what is broken and no clue why this happens hmm

Offline

#6 2021-09-23 13:13:26

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: [SOLVED] Experiencing wireless network crashes

Does 8.8.8.8 take a different route than anything else?

ip a; ip r; iptables -nvL

(Also: is this reproducible, so the success wasn't just a fluke?)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2021-09-27 06:52:13

thecodingowl
Member
Registered: 2021-09-11
Posts: 6

Re: [SOLVED] Experiencing wireless network crashes

So I am back after the weekend and I have to wait for the issue to occur again, but when it's running fine, like it is right now, it is looking like this:

 kevin  ~  ip a; ip r; sudo iptables -nvL
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 
       valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether d4:3d:7e:38:27:d0 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 54:e6:fc:d7:e0:43 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.32/24 brd 192.168.178.255 scope global dynamic noprefixroute wlan0
       valid_lft 860971sec preferred_lft 860971sec
    inet6 2a01:c23:80a4:ed00:a9d0:519a:dc1d:f371/64 scope global dynamic noprefixroute 
       valid_lft 7157sec preferred_lft 3557sec
    inet6 fe80::a80:b2b1:224:a037/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
default via 192.168.178.1 dev wlan0 proto dhcp metric 600 
192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.32 metric 600 
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         

 kevin  ~  traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  _gateway (192.168.178.1)  3.630 ms  4.635 ms  10.083 ms
 2  loopback1.0003.acln.02.fra.de.net.telefonica.de (62.52.201.194)  23.080 ms  23.056 ms  23.045 ms
 3  bundle-ether30.0004.dbrx.02.fra.de.net.telefonica.de (62.53.0.192)  21.673 ms  21.680 ms  21.671 ms
 4  bundle-ether2.0005.prrx.02.fra.de.net.telefonica.de (62.53.9.53)  22.961 ms bundle-ether1.0005.prrx.02.fra.de.net.telefonica.de (62.53.10.51)  22.959 ms  22.950 ms
 5  72.14.198.209 (72.14.198.209)  22.940 ms  22.932 ms 72.14.213.76 (72.14.213.76)  26.605 ms
 6  * * *
 7  dns.google (8.8.8.8)  21.429 ms  14.100 ms  15.207 ms

 kevin  ~  traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  _gateway (192.168.178.1)  3.986 ms  3.941 ms  5.927 ms
 2  loopback1.0003.acln.02.fra.de.net.telefonica.de (62.52.201.194)  21.019 ms  20.994 ms  20.975 ms
 3  bundle-ether30.0003.dbrx.02.fra.de.net.telefonica.de (62.53.0.190)  20.854 ms bundle-ether30.0004.dbrx.02.fra.de.net.telefonica.de (62.53.0.192)  20.850 ms  20.834 ms
 4  bundle-ether1.0005.prrx.02.fra.de.net.telefonica.de (62.53.10.51)  20.815 ms  23.732 ms  23.724 ms
 5  * * *
 6  one.one.one.one (1.1.1.1)  23.576 ms * *

Edit:
And after it happened again, I have the same result as last week, where I could ping 8.8.8.8 but nothing else.
Traceroute looks like this:

 kevin  ~  traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  _gateway (192.168.178.1)  13.986 ms  23.910 ms  28.481 ms
 2  62.52.201.194 (62.52.201.194)  37.292 ms  37.302 ms  40.373 ms
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  8.8.8.8 (8.8.8.8)  15.548 ms  19.775 ms  19.797 ms

 kevin  ~  traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  _gateway (192.168.178.1)  8.514 ms  15.034 ms  15.753 ms
 2  62.52.201.194 (62.52.201.194)  28.465 ms  28.496 ms  28.496 ms
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Last edited by thecodingowl (2021-09-27 07:54:49)

Offline

#8 2021-11-20 15:44:58

thecodingowl
Member
Registered: 2021-09-11
Posts: 6

Re: [SOLVED] Experiencing wireless network crashes

I think this issue was indeed linked to wpa_supplicant.
I checked again and found wpa_supplicant still running as a process.
I removed it commpletely and the issues stopped.
I have a new machine now and installed a new archlinux instance, linked to the network by cable, so I can not recreate the issue now, but I would guess this was solved by switching the provider from wpa_supplicant to something else in NetworkManager.
Thanks very much for your help, though.

Offline

Pages: 1

Board footer

Powered by FluxBB