This is kind of unusual. Raspberry Pi 3 B+ with Aarch64 image. My SSH session keeps dying. I've noticed it happens about every half hour. When I log into the physical machine I see the IP address has changed. My DHCP server's default lease time is 60 minutes (max lease 120 minutes). 60 minutes is aggressive and it is intended to scavenge old leases quickly because of of device activity in my lab. Many devices are started up, a test is run, and then shutdown immediately. If I allow them to hang around for days or weeks then I sometimes run out of addresses in the subnet. I'm guessing the RPI is trying to renew at 30 minutes. Looking at DMESG I don't see a renew request; only a message about wlan0: [ 33.641372] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 33.658658] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 33.701586] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 33.776179] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 33.839349] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 34.384878] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 35.183999] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 380.555159] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 696.561166] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1012.565499] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1328.575936] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1644.604460] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready <disconnect around here> The RPI is the only device exhibiting the behavior. Does anyone know how to sidestep the problem? Thanks in advance. _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
