Help, i get disconnect ramdonly only with this wifi

I repeat a WiFi signal, every X amount of time it disconnects and the network remains gray as inactive. This is the log

Mon Oct 30 20:06:18 2023 kern.info kernel: [621311.628318] wlan0: deauthenticated from f8:ab:05:6b:c6:cf (Reason: 4=DISASSOC_DUE_TO_INACTIVITY)
Mon Oct 30 20:06:18 2023 daemon.notice netifd: Network device 'wlan0' link is down
Mon Oct 30 20:06:18 2023 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Mon Oct 30 20:06:18 2023 kern.warn kernel: [621311.641076] ath10k_pci 0000:00:00.0: peer-unmap-event: unknown peer id 2
Mon Oct 30 20:06:18 2023 kern.warn kernel: [621311.648213] ath10k_pci 0000:00:00.0: peer-unmap-event: unknown peer id 2
Mon Oct 30 20:06:18 2023 daemon.notice wpa_supplicant[23689]: wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:ab:05:6b:c6:cf reason=4
Mon Oct 30 20:06:18 2023 daemon.notice wpa_supplicant[23689]: wlan0: SME: Trying to authenticate with f8:ab:05:6b:c6:cf (SSID='Fibertel WiFi298 5.8GHz' freq=5260 MHz)
Mon Oct 30 20:06:18 2023 kern.info kernel: [621311.661425] wlan0: authenticate with f8:ab:05:6b:c6:cf
Mon Oct 30 20:06:18 2023 kern.info kernel: [621311.679646] wlan0: send auth to f8:ab:05:6b:c6:cf (try 1/3)
Mon Oct 30 20:06:18 2023 daemon.notice netifd: wwan (23708): udhcpc: received SIGTERM
Mon Oct 30 20:06:18 2023 daemon.notice netifd: Interface 'wwan' is now down
Mon Oct 30 20:06:18 2023 daemon.notice netifd: Interface 'wwan' is disabled
Mon Oct 30 20:06:18 2023 daemon.notice netifd: Interface 'wwan' is enabled
Mon Oct 30 20:06:18 2023 daemon.warn dnsmasq[2306]: no servers found in /tmp/resolv.conf.auto, will retry
Mon Oct 30 20:06:18 2023 kern.info kernel: [621311.788778] wlan0: send auth to f8:ab:05:6b:c6:cf (try 2/3)
Mon Oct 30 20:06:18 2023 kern.info kernel: [621311.898747] wlan0: send auth to f8:ab:05:6b:c6:cf (try 3/3)
Mon Oct 30 20:06:18 2023 kern.info kernel: [621311.905498] wlan0: authentication with f8:ab:05:6b:c6:cf timed out
Mon Oct 30 20:06:18 2023 kern.warn kernel: [621311.912447] ath10k_pci 0000:00:00.0: peer-unmap-event: unknown peer id 2
Mon Oct 30 20:06:19 2023 kern.info kernel: [621313.065552] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
Mon Oct 30 20:06:19 2023 kern.info kernel: [621313.072786] br-lan: port 2(wlan0-1) entered blocking state
Mon Oct 30 20:06:19 2023 kern.info kernel: [621313.078546] br-lan: port 2(wlan0-1) entered forwarding state
Mon Oct 30 20:06:19 2023 daemon.notice netifd: Network device 'wlan0-1' link is up
Mon Oct 30 20:06:31 2023 daemon.notice wpa_supplicant[23689]: wlan0: SME: Trying to authenticate with f8:ab:05:6b:c6:cf (SSID='Fibertel WiFi298 5.8GHz' freq=5260 MHz)
Mon Oct 30 20:06:31 2023 daemon.notice wpa_supplicant[23689]: wlan0: SME: Authentication request to the driver failed
Mon Oct 30 20:06:31 2023 kern.info kernel: [621324.807824] wlan0: authenticate with f8:ab:05:6b:c6:cf
Mon Oct 30 20:06:31 2023 kern.info kernel: [621324.815496] br-lan: port 2(wlan0-1) entered disabled state
Mon Oct 30 20:06:31 2023 daemon.notice netifd: Network device 'wlan0-1' link is down
Mon Oct 30 20:06:31 2023 kern.info kernel: [621325.070679] br-lan: port 2(wlan0-1) entered blocking state
Mon Oct 30 20:06:31 2023 kern.info kernel: [621325.076462] br-lan: port 2(wlan0-1) entered forwarding state
Mon Oct 30 20:06:31 2023 daemon.notice netifd: Network device 'wlan0-1' link is up
Mon Oct 30 20:06:32 2023 daemon.err uhttpd[1641]: luci: accepted login on /admin/network/wireless for root from 192.168.1.158
Mon Oct 30 20:06:38 2023 daemon.notice wpa_supplicant[23689]: wlan0: SME: Trying to authenticate with f8:ab:05:6b:c6:cf (SSID='Fibertel WiFi298 5.8GHz' freq=5260 MHz)
Mon Oct 30 20:06:38 2023 daemon.notice wpa_supplicant[23689]: wlan0: SME: Authentication request to the driver failed
Mon Oct 30 20:06:38 2023 daemon.notice wpa_supplicant[23689]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Fibertel WiFi298 5.8GHz" auth_failures=1 duration=10 reason=CONN_FAILED
Mon Oct 30 20:06:38 2023 kern.info kernel: [621331.565848] wlan0: authenticate with f8:ab:05:6b:c6:cf
Mon Oct 30 20:06:38 2023 kern.info kernel: [621331.573165] br-lan: port 2(wlan0-1) entered disabled state
Mon Oct 30 20:06:38 2023 daemon.notice netifd: Network device 'wlan0-1' link is down
Mon Oct 30 20:06:43 2023 daemon.notice netifd: Network device 'wlan0-1' link is up
Mon Oct 30 20:06:43 2023 kern.info kernel: [621337.122881] br-lan: port 2(wlan0-1) entered blocking state
Mon Oct 30 20:06:43 2023 kern.info kernel: [621337.128690] br-lan: port 2(wlan0-1) entered forwarding state
Mon Oct 30 20:06:45 2023 daemon.notice netifd: Interface 'wwan' is disabled
Mon Oct 30 20:06:45 2023 daemon.notice hostapd: wlan0-1: interface state ENABLED->DISABLED
Mon Oct 30 20:06:45 2023 daemon.notice hostapd: wlan0-1: AP-DISABLED
Mon Oct 30 20:06:45 2023 daemon.notice hostapd: wlan0-1: CTRL-EVENT-TERMINATING
Mon Oct 30 20:06:45 2023 daemon.err wpa_supplicant[23689]:  Failed to stop hostapd AP interfaces
Mon Oct 30 20:06:45 2023 daemon.notice wpa_supplicant[23689]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Mon Oct 30 20:06:45 2023 daemon.notice wpa_supplicant[23689]: wlan0: CTRL-EVENT-TERMINATING
Mon Oct 30 20:06:45 2023 daemon.notice hostapd: nl80211: deinit ifname=wlan0-1 disabled_11b_rates=0
Mon Oct 30 20:06:45 2023 kern.info kernel: [621338.947465] device wlan0-1 left promiscuous mode
Mon Oct 30 20:06:45 2023 kern.info kernel: [621338.952593] br-lan: port 2(wlan0-1) entered disabled state
Mon Oct 30 20:06:45 2023 kern.warn kernel: [621338.980759] ath10k_pci 0000:00:00.0: peer-unmap-event: unknown peer id 0
Mon Oct 30 20:06:45 2023 kern.warn kernel: [621338.987777] ath10k_pci 0000:00:00.0: peer-unmap-event: unknown peer id 0
Mon Oct 30 20:06:45 2023 daemon.notice netifd: Network device 'wlan0-1' link is down
Mon Oct 30 20:06:46 2023 daemon.notice netifd: radio0 (24313): command failed: Not supported (-122)
Mon Oct 30 20:06:46 2023 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Mon Oct 30 20:06:47 2023 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf```

It is probably related to the upstream connection... you may not have any control over it on your OpenWrt device.

Have you tried connecting to the upstream network with other devices like a laptop or similar? does it have a similar issue?

What is X -- minutes, hours, days? What is the specific time, and is it consistent?

2 Likes

Yes, when I'm nearby I connect directly but without problems, that's why I have no idea.
Is it the distance?
When I repeat another network it doesn't happen, could it be some configuration of the main router?

While you are connected what is the dBm level and tx/rx MCS numbers?

If the signal is marginal, expect some disconnections.