Bipac 8800AXL R2 reboot loses Raspberry Pi 4 DHCP lease
Posted: Sun Mar 07, 2021 10:44 am
I reboot my Bipac 8800AXL R2 router on a weekly basis and I am finding the my new RPI 4 loses the wifi connectivity to this router on reboot.
I see the following entries in /var/log/syslog at the time of the reboot:
Mar 7 02:01:20 PiTv dhcpcd[449]: wlan0: carrier acquired
Mar 7 02:01:20 PiTv dhcpcd[449]: wlan0: IAID 32:ba:68:5b
Mar 7 02:01:20 PiTv dhcpcd[449]: wlan0: adding address fe80::c68f:e6c6:7b0f:9f88
Mar 7 02:01:20 PiTv avahi-daemon[376]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::c68f:e6c6:7b0f:9f88.
Mar 7 02:01:20 PiTv avahi-daemon[376]: New relevant interface wlan0.IPv6 for mDNS.
Mar 7 02:01:20 PiTv avahi-daemon[376]: Registering new address record for fe80::c68f:e6c6:7b0f:9f88 on wlan0.*.
Mar 7 02:01:20 PiTv dhcpcd[449]: wlan0: soliciting an IPv6 router
Mar 7 02:01:21 PiTv dhcpcd[449]: wlan0: rebinding lease of 192.168.1.113
Mar 7 02:01:26 PiTv dhcpcd[449]: wlan0: probing for an IPv4LL address
Mar 7 02:01:26 PiTv dhcpcd[449]: wlan0: DHCP lease expired
Mar 7 02:01:26 PiTv dhcpcd[449]: wlan0: soliciting a DHCP lease
Mar 7 02:01:30 PiTv dhcpcd[449]: wlan0: using IPv4LL address 169.254.168.194
Mar 7 02:01:30 PiTv avahi-daemon[376]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.168.194.
Mar 7 02:01:30 PiTv dhcpcd[449]: wlan0: adding route to 169.254.0.0/16
Mar 7 02:01:30 PiTv dhcpcd[449]: wlan0: adding default route
Mar 7 02:01:30 PiTv avahi-daemon[376]: New relevant interface wlan0.IPv4 for mDNS.
Mar 7 02:01:30 PiTv avahi-daemon[376]: Registering new address record for 169.254.168.194 on wlan0.IPv4.
Mar 7 02:01:33 PiTv dhcpcd[449]: wlan0: no IPv6 Routers available
I then have to reboot the RPI 4 to re-connect to the WiFi. Is there anything I can do to have the RPI 4 automatically re-connect on reboot of the router?
I have been searching online but I can't find anything about this condition where the RPI 4 has WiFi connectivity working perfectly fine until the router is rebooted and then it fails to connect.
I see the following entries in /var/log/syslog at the time of the reboot:
Mar 7 02:01:20 PiTv dhcpcd[449]: wlan0: carrier acquired
Mar 7 02:01:20 PiTv dhcpcd[449]: wlan0: IAID 32:ba:68:5b
Mar 7 02:01:20 PiTv dhcpcd[449]: wlan0: adding address fe80::c68f:e6c6:7b0f:9f88
Mar 7 02:01:20 PiTv avahi-daemon[376]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::c68f:e6c6:7b0f:9f88.
Mar 7 02:01:20 PiTv avahi-daemon[376]: New relevant interface wlan0.IPv6 for mDNS.
Mar 7 02:01:20 PiTv avahi-daemon[376]: Registering new address record for fe80::c68f:e6c6:7b0f:9f88 on wlan0.*.
Mar 7 02:01:20 PiTv dhcpcd[449]: wlan0: soliciting an IPv6 router
Mar 7 02:01:21 PiTv dhcpcd[449]: wlan0: rebinding lease of 192.168.1.113
Mar 7 02:01:26 PiTv dhcpcd[449]: wlan0: probing for an IPv4LL address
Mar 7 02:01:26 PiTv dhcpcd[449]: wlan0: DHCP lease expired
Mar 7 02:01:26 PiTv dhcpcd[449]: wlan0: soliciting a DHCP lease
Mar 7 02:01:30 PiTv dhcpcd[449]: wlan0: using IPv4LL address 169.254.168.194
Mar 7 02:01:30 PiTv avahi-daemon[376]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.168.194.
Mar 7 02:01:30 PiTv dhcpcd[449]: wlan0: adding route to 169.254.0.0/16
Mar 7 02:01:30 PiTv dhcpcd[449]: wlan0: adding default route
Mar 7 02:01:30 PiTv avahi-daemon[376]: New relevant interface wlan0.IPv4 for mDNS.
Mar 7 02:01:30 PiTv avahi-daemon[376]: Registering new address record for 169.254.168.194 on wlan0.IPv4.
Mar 7 02:01:33 PiTv dhcpcd[449]: wlan0: no IPv6 Routers available
I then have to reboot the RPI 4 to re-connect to the WiFi. Is there anything I can do to have the RPI 4 automatically re-connect on reboot of the router?
I have been searching online but I can't find anything about this condition where the RPI 4 has WiFi connectivity working perfectly fine until the router is rebooted and then it fails to connect.