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?
Is the dhcp server for your LAN closely-coupled with the Ethernet switch?
Might it be that the IP address lease from the dhcp server is expiring and that is being communicated to the switch so that the address becomes marked as invalid in the arp table?
I have an RPi3b+ with a cabled ethernet connection to a simple unmanaged ethernet switch and it has an uptime of 100+ days without seeing this issue. The dhcp server is elsewhere on the LAN.
I suspect your LAN configuration rather than the RPi3B.
Sample data -
Code:
pi@RPi3BplusOffice:~ $ uptime 11:49:30 up 103 days, 20:27, 2 users, load average: 0.00, 0.01, 0.00pi@RPi3BplusOffice:~ $ ip link show eth02: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:fd:34:bd brd ff:ff:ff:ff:ff:ffpi@RPi3BplusOffice:~ $ cat /proc/cpuinfo[ ... ]Hardware: BCM2835Revision: a020d3Serial: 000000004afd34bdpi@RPi3BplusOffice:~ $ Statistics: Posted by B.Goode — Mon Jul 08, 2024 10:58 am