Hello,
I have a Raspberry Pi 3 model B running Bookworm, attached to an Ethernet switch. The Pi is set up to serve a home wifi network.
Upon booting, the network interface receives an IP address etc using DHCP, and everything works fine for a while. But usually after 24 hours or so, the interface stops working. Running "route" and "ifconfig" (I'm old fashioned) everything looks ok, but pings to the upstream router are not returned. If I cycle the interface with "nmcli disconnect" and then "up", the interface no longer gets an IP address. However, if I do a reboot, everything comes up fine.
Even if the interface is lightly used, it will stop working after a day or so. But I also get the sense that if I do a large download, that may also trigger the malfunction.
The same thing happens with another switch. I'm guessing it's not a cable problem since a reboot will immediately fix things.
Any ideas how I proceed to diagnose the problem?
I have a Raspberry Pi 3 model B running Bookworm, attached to an Ethernet switch. The Pi is set up to serve a home wifi network.
Upon booting, the network interface receives an IP address etc using DHCP, and everything works fine for a while. But usually after 24 hours or so, the interface stops working. Running "route" and "ifconfig" (I'm old fashioned) everything looks ok, but pings to the upstream router are not returned. If I cycle the interface with "nmcli disconnect" and then "up", the interface no longer gets an IP address. However, if I do a reboot, everything comes up fine.
Even if the interface is lightly used, it will stop working after a day or so. But I also get the sense that if I do a large download, that may also trigger the malfunction.
The same thing happens with another switch. I'm guessing it's not a cable problem since a reboot will immediately fix things.
Any ideas how I proceed to diagnose the problem?
Statistics: Posted by larsbrinkhoff — Mon Jul 08, 2024 7:40 am — Replies 1 — Views 52