Raspberry Pi v4 cannot acquire IPv4 over wifi

Product support balenaOS
, ,
1

Hello,

After flashing an empty SSD, connecting it to a new Raspberry Pi 4, and adding it to my fleet, I noticed that it has issues procuring an IPv4 address from my WiFi. This results in one of my containers that connects to the internet failing, even though the Raspberry Pi is visible and accessible through its IPv6 even in my local network, and is visible in the dashboard.

Hardware:
Raspberry Pi v4B that runs with an SSD.

Notes:

  1. Ethernet connections work correctly and with no issues.
  2. I was worried that this might be an incompatibility between my device and the latest version of balenaOS or the supervisor process (balenaOS v6.0.23, supervisor v16.7.0 at the time of writing), so I flashed the SSD from scratch (after reading that a rollback is not possible) and set both versions (balenaOS and supervisor) to the versions that I already use in other devices in my fleet that have faced no such issues (balenaOS v5.2.8, supervisor v16.2.28). The issues persisted on this device.
  3. The issue is not permanent, but it seems…random. I boot up the device and it might work fine, I reboot it and it might face the issues again.
  4. After reading some forum posts, I added the “country” in my device’s config.json (even though it is not set in the rest of my fleet’s devices and they work fine). It did not fix the issue.

After accessing my device through SSH (which worked both through ethernet and IPv6 over WiFi), I see that the IPv4 route does not even exist.

WiFi NetworkManager config file:

[connection]
id=mywifi
type=wifi
interface-name=wlan0

[wifi]
mode=infrastructure
ssid=mywifi

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=mypassword

[ipv4]
method=auto

[ipv6]
addr-gen-mode=default
method=auto

[proxy]

Logs from journalctl:

Sep 23 07:29:23 f3044c2 NetworkManager[1994]: <info>  [1727076563.4967] dhcp: init: Using DHCP client 'internal'
Sep 23 07:29:30 f3044c2 NetworkManager[1994]: <info>  [1727076570.3084] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 23 07:29:31 f3044c2 NetworkManager[1994]: <info>  [1727076571.6143] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 23 07:29:32 f3044c2 NetworkManager[1994]: <info>  [1727076572.9296] dhcp6 (wlan0): state changed new lease

Dashboard screenshot:
image

2

Hi, could you make sure that your access point is serving IPv4 addresses to other devices? It looks like the access point might be configured to server IPv6 addresses only.

1 Like