UPDATE:
My initial assessment about "incoming connections" was wrong.
Its a KEEP-ALIVE issue. After about 10 minutes the WIFI interface goes into some sort of sleep.
No journalctl messages about it.
If I ping it from PC, its dead.
But as soon as I start pinging _from_ PI to anywhere, it immediately associates and wakes up.
Never had that before (with the same router). I guess I have to figure out how to send keep-alive pings every minute or two?
My initial assessment about "incoming connections" was wrong.
Its a KEEP-ALIVE issue. After about 10 minutes the WIFI interface goes into some sort of sleep.
No journalctl messages about it.
If I ping it from PC, its dead.
But as soon as I start pinging _from_ PI to anywhere, it immediately associates and wakes up.
Code:
wpa_supplicant[571]: wlan0: CTRL-EVENT-DISCONNECTED bssid= reason=6wpa_supplicant[571]: wlan0: Trying to associate with SSID ':)'wpa_supplicant[571]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLDNetworkManager[638]: <info> device (wlan0): supplicant interface state: completed -> associatingwpa_supplicant[571]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=USNetworkManager[638]: <info> device (p2p-dev-wlan0): supplicant management interface state: completed -> associatingwpa_supplicant[571]: wlan0: Associated with :)wpa_supplicant[571]: wlan0: CTRL-EVENT-CONNECTED - Connection to :) completed [id=0 id_str=]wpa_supplicant[571]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0NetworkManager[638]: <info> device (wlan0): supplicant interface state: associating -> completedNetworkManager[638]: <info> device (p2p-dev-wlan0): supplicant management interface state: associating -> completedStatistics: Posted by Atari2601 — Thu Jun 06, 2024 9:18 pm
