Billion UK Forum

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.

OK, I realised that I had only defined a single, guest SSID on my router's list of SSID's to be the wlan connection for my RPI4. I have since updated the wpa_supplicant.conf file to include 3 SSID's, including the primary SSID.

$ wpa_cli list_networks
Selected interface 'p2p-dev-wlan0'
network id / ssid / bssid / flags
0 Billion-AP-5g any
1 Billion-Guest1-5g any
2 Billion-Guest2-5g any

$ iwgetid
wlan0 ESSID:"Billion-AP-5g"

$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:"Billion-AP-5g"
Mode:Managed Frequency:5.18 GHz Access Point: 60:03:47:39:84:F3
Bit Rate=292.5 Mb/s Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=58/70 Signal level=-52 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:451 Invalid misc:0 Missed beacon:0

So far now when my Billion 8800AXL R2 reboots the RPI4 re-connects successfully.

This still doesn't explain why before when I just had the Billion-Guest1-5g as my sole SSID that the DHCP lease was lost on reboot. But the above changes do stop the issue from happening for my situation now.

My issue has returned. Upon upgrading FW and rebooting the router I see the following in the RPI4 syslog file:

Mar 25 10:49:50 PiTv dhcpcd[449]: wlan0: rebinding lease of 192.168.1.101
Mar 25 10:49:50 PiTv dhcpcd[449]: wlan0: soliciting an IPv6 router
Mar 25 10:49:55 PiTv dhcpcd[449]: wlan0: probing for an IPv4LL address
Mar 25 10:49:55 PiTv dhcpcd[449]: wlan0: DHCP lease expired
Mar 25 10:49:55 PiTv dhcpcd[449]: wlan0: soliciting a DHCP lease
Mar 25 10:50:00 PiTv dhcpcd[449]: wlan0: using IPv4LL address 169.254.37.102

Again, the above entries seem to appear that the 8800AXL isn't renewing the lease.

Ksaro1 wrote: ↑Sat Mar 27, 2021 1:01 pm My issue has returned. Upon upgrading FW and rebooting the router I see the following in the RPI4 syslog file:

Mar 25 10:49:50 PiTv dhcpcd[449]: wlan0: rebinding lease of 192.168.1.101
Mar 25 10:49:50 PiTv dhcpcd[449]: wlan0: soliciting an IPv6 router
Mar 25 10:49:55 PiTv dhcpcd[449]: wlan0: probing for an IPv4LL address
Mar 25 10:49:55 PiTv dhcpcd[449]: wlan0: DHCP lease expired
Mar 25 10:49:55 PiTv dhcpcd[449]: wlan0: soliciting a DHCP lease
Mar 25 10:50:00 PiTv dhcpcd[449]: wlan0: using IPv4LL address 169.254.37.102

Again, the above entries seem to appear that the 8800AXL isn't renewing the lease.

Please submit a ticket on the following link https://support.billion.uk.com/index.ph ... ets/Submit (I think I our engineers might need remote access to your router to check the route cause)

Ticket DQP-311-70948 submitted.

BTW - I'm UK based. So if engineers need to contact me I am on BST

Ksaro1 wrote: ↑Tue Mar 30, 2021 1:53 pm Ticket DQP-311-70948 submitted.

BTW - I'm UK based. So if engineers need to contact me I am on BST

Replies will be sent via our support system

This issue hasn't occurred since installing 2.52.d17.