Dhcp fails with: inet prefix is expected rather than ""

So, this is an issue with the install procedure. Even though the device gets an address acknowledged from DHCP server, the ping fails, and the first time setup stops.

The error in question:

dhcp fails with: inet prefix is expected rather than “”

Because I can’t have network, I can’t capture the full logs, but I took a photo of when trying to get networking in a helper shell.

I can’t provide all the requested info on my system, because it failed to install.

But, it is the latest download for pinebook pro.

8.15.2 master MichaIng

Is this an issue with the installer script?

Should the argument have been instead? I have dozens of devices that work fine with my dhcp-server. Why can’t dietpi use the IP address, as acknowledged by the dhcp-server?

1 Like

I fixed this by doing the following:

Changed my x.x.x.x/14 LAN to a x.x.x.x/16 LAN.

The 18-bit address space appeared to overwhelm dietpi. And since it was larger than I needed for a home network, I changed my router to a smaller LAN address space.

1 Like

not sure if this is related to DietPi. Because we don’t do any special on network configuration. We use Debian standard ifupdown to manage the network. Maybe @MichaIng could have a look.

I’ve never really seen or dealt with an address space larger than 8 bits. And indeed 16 bits seem would be the next I’d think of, instead of starting in the middle of an octal, for very large networks where 254 addresses are not sufficient.

To me it seems like the router is passing the address space in an uncommon way, using the network mask behind tha backslash, instead of the CIDR bits notation, at least based on the output.

However, ifupdown seems to indeed handle this somehow strange. It throws an error message, but then says it bound to the address, while nothing was bound to.

I’ll test this when I find time. Generally I think any network size is supported, as long as the format is correct. While other network managers/OSes may handle things more graceful, at least Debian/ifupdown does the way your DHCP server provides the info.