Thanks for all the responses.
Just to recap... this is the context
How do I know when connectivity is broken? Usually when my SSH sessions freeze on my corporate MacBook. I have my problem rPi on a bench w/a monitor, when it looses connectivity wlan0 is not provisioned (i.e. ifconfig -a, no IP address). /etc/os-release says 13.1 (Trixie).
"nmcli radio wifi on|off" executed the commands but did not restore connectivity. So far, only a restart has restore connectivity.
I will see about getting something from journalctl.
Just to recap... this is the context
When I returned home this week, there was one rPi without connectivity and 3 other rPi still connected to my home WAP. My ISP uses WiMax and the WAP is a LinkSys wrt54g. It is not weird for me to return home and need to reset the WiMax router to get everything (not only rPi) to work.My ISP is unreliable, it is normal to loose connectivity for many hours. When connectivity is restored, my rpi4 do not reconnect via WiFi. Right now, I reboot every 24 hours via cron just in case. This seems unsophisticated, how can I make WiFi restart without rebooting?
rpi4 hosts on "Raspberry Pi OS Lite (64 bit)" (no desktop).
How do I know when connectivity is broken? Usually when my SSH sessions freeze on my corporate MacBook. I have my problem rPi on a bench w/a monitor, when it looses connectivity wlan0 is not provisioned (i.e. ifconfig -a, no IP address). /etc/os-release says 13.1 (Trixie).
"nmcli radio wifi on|off" executed the commands but did not restore connectivity. So far, only a restart has restore connectivity.
I will see about getting something from journalctl.
Statistics: Posted by guycole — Sun Nov 16, 2025 6:24 pm