My RPi Zero which uses 32-bit lite RPi OS and runs Pi-hole, and is acting as the IPv4 and IPv6 DHCP server, is killing IPv6 in my home network, because when the IPv6 prefix's lease is renewed, the RPi Zero doesn't recognise the renewed lease, instead believing it an old prefix that my router is broadcasting.
What can I do to get the Pi Zero to recognise that the IPv6 prefix is current, and start using it and advertising it?
Frustratingly, a reboot fixes the problem, which is clearly not a solution!
IPv6 network configuration:dnsmasq IPv6 DHCP configuration:Pi-hole diagnosis entry:40 seconds of Pi-hole log file entries:
What can I do to get the Pi Zero to recognise that the IPv6 prefix is current, and start using it and advertising it?
Frustratingly, a reboot fixes the problem, which is clearly not a solution!
IPv6 network configuration:
Code:
cat /etc/NetworkManager/conf.d/ipv6.conf [connection]ipv6.addr-gen-mode=1ipv6.ip6-privacy=2Code:
cat /etc/dnsmasq.d/dhcpv6.confdhcp-range=::,constructor:eth0,ra-names,ra-stateless,64Code:
DNSMASQ_WARN: no address range available for DHCPv6 request via eth0Code:
2025-05-02 04:24:40.468 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:24:41.470 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:24:41.479 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:24:41.480 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:24:41.481 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:24:41.503 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:24:41.505 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:24:42.503 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:24:43.589 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:24:44.592 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:24:44.601 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:24:44.602 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:24:44.603 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:24:44.614 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:24:44.616 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:24:45.614 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:24:46.734 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:24:47.737 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:24:47.745 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:24:47.747 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:24:47.748 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:24:47.772 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:24:47.774 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:24:48.772 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:24:50.133 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:24:51.150 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:24:51.159 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:24:51.160 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:24:51.161 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:24:51.176 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:24:51.178 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:24:52.176 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:24:53.265 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:24:54.267 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:24:54.276 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:24:54.277 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:24:54.278 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:24:54.281 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:24:54.298 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:24:55.282 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:24:56.310 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:24:57.312 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:24:57.320 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:24:57.322 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:24:57.323 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:24:57.326 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:24:57.328 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:24:58.326 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:24:59.373 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:25:00.872 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:25:00.892 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:25:00.893 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:25:00.894 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:25:00.896 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:25:00.897 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:25:01.896 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:25:03.067 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:25:04.069 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:25:04.103 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:25:04.104 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:25:04.105 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:25:04.108 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:25:04.109 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:25:05.108 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:25:06.143 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:25:07.145 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:25:07.152 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:25:07.153 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:25:07.154 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:25:07.172 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:25:07.174 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:25:08.157 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:25:09.208 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:25:10.210 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:25:10.220 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:25:10.229 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:25:10.230 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:25:10.237 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:25:10.238 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:25:11.237 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:25:12.304 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:25:13.306 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:25:13.313 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:25:13.314 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:25:13.315 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:25:13.318 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:25:13.319 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:25:14.318 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:25:15.353 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:25:16.355 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:25:16.364 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:25:16.365 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:25:16.366 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:25:16.369 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:25:16.371 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>2025-05-02 04:25:17.370 RTR-ADVERT(eth0) <IPv6-prefix>2025-05-02 04:25:18.398 router advertisement on <IPv6-prefix>, old prefix for eth02025-05-02 04:25:19.401 RTR-ADVERT(eth0) <IPv6-prefix> old prefix2025-05-02 04:25:19.409 DHCPv6 stateless on <IPv6-prefix>, constructed for eth02025-05-02 04:25:19.410 DHCPv4-derived IPv6 names on <IPv6-prefix>, constructed for eth02025-05-02 04:25:19.420 router advertisement on <IPv6-prefix>, constructed for eth02025-05-02 04:25:19.433 SLAAC-CONFIRM(eth0) <device1-IPv6-address> <device1>2025-05-02 04:25:19.434 SLAAC-CONFIRM(eth0) <device2-IPv6-address> <device2>Statistics: Posted by jeremym — Thu May 01, 2025 7:12 pm