Score:0

20.04 Cloud-init appears to disable ipv4 DHCP on eth0

ng flag

I'm doing a fresh install of 20.04 on some Raspberry Pi 3s. The SD cards were flashed with Ubuntu 20.04 Server (32bit) using the RPi imager.

When cloud init finishes wlan0 has an ipv4 address from DHCP but eth0 does not. Both interfaces have ipv6 addresses.

Setting the eth0 address with dhclient eth0 -v gives the interface the correct address, but that does not survive a reboot.

Despite what it says in /etc/netplan/50-cloud-init.yaml, adding the file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg containing the line network: {config: disabled} fails to stop cloud init on subsequent reboots.

How do I configure the system to get a persistant ipv4 address from DHCP on boot?

Score:0
ng flag

It turns out this has nothing to do with cloud-init. Even after completely purging cloud-init from the system I still only get an ipv4 address on wlan0, and none on eth0.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.