I'm having an odd problem with a Raspberry PI Zero W. It seems to be not
renewing it's dhcp lease:
Dec 31 10:09:17 raspberrypi-bank dhcpcd[271]: wlan0: DHCP lease expired
Dec 31 10:09:17 raspberrypi-bank avahi-daemon[233]: Withdrawing
address record for 10.0.0.131 on wlan0.
Dec 31 10:09:17 raspberrypi-bank avahi-daemon[233]: Leaving mDNS
multicast group on interface wlan0.IPv4 with address \
10.0.0.131.
Dec 31 10:09:17 raspberrypi-bank avahi-daemon[233]: Interface
wlan0.IPv4 no longer relevant for mDNS.
Dec 31 10:09:17 raspberrypi-bank dhcpcd[271]: wlan0: deleting route to
10.0.0.0/24
Dec 31 10:09:17 raspberrypi-bank dhcpcd[271]: wlan0: deleting default
route via 10.0.0.9
Dec 31 10:09:18 raspberrypi-bank avahi-daemon[233]: Got SIGHUP, reloading.
Dec 31 10:09:18 raspberrypi-bank avahi-daemon[233]: No service file
found in /etc/avahi/services.
Dec 31 10:09:18 raspberrypi-bank dhcpcd[271]: wlan0: soliciting a DHCP
lease
Dec 31 10:09:23 raspberrypi-bank dhcpcd[271]: wlan0: probing for an
IPv4LL address
Dec 31 10:09:28 raspberrypi-bank dhcpcd[271]: wlan0: using IPv4LL
address 169.254.216.59
Dec 31 10:09:28 raspberrypi-bank avahi-daemon[233]: Joining mDNS
multicast group on interface wlan0.IPv4 with address \
169.254.216.59.
Dec 31 10:09:28 raspberrypi-bank dhcpcd[271]: wlan0: adding route to
169.254.0.0/16
Dec 31 10:09:28 raspberrypi-bank dhcpcd[271]: wlan0: adding default route
Dec 31 10:09:28 raspberrypi-bank avahi-daemon[233]: New relevant
interface wlan0.IPv4 for mDNS.
Dec 31 10:09:28 raspberrypi-bank avahi-daemon[233]: Registering new
address record for 169.254.216.59 on wlan0.IPv4.
Worrying I have more than one DHCP server I ran:
nmap --script broadcast-dhcp-discover 10.0.0.0/24
Both from my regular notebook and from the Pi, and I only get the one
server I intend.
I have played with several models of Raspberry Pi over the years and
never had this problem, nor do other computer on this network have this
problem. This Pi is running "Raspbian GNU/Linux 11", says /etc/issue,
the only other Pi currently on this network says it is running "Debian
GNU/Linux 12", so being more up-to-date is an obvious thing to try.
And there are certainly more things for me to try (such as trying
logging on on 169.254.216.59 next time and see if I can get a new lease
by hand), but do any quick answers leap to minds?
Thanks,
-kb
P.S. Happy New Year!
_______________________________________________
Discuss mailing list
Discuss@lists.blu.org
http://lists.blu.org/mailman/listinfo/discuss
