No IPv4 addresses are provided until an external interface is found

[chrysn]

With hnet-full installed via OpenWRT nightlies, my router does not assign any IPv4 addresses to internal interfaces (let alone deal out ones via DHCP) until an interface is detected to be external, and possibly an IPv4 address gets assigned to one.

While this may not be a big deal in practice (given that the addresses seem to stay configured even when the external interface's link goes down), this can be offputting to newcomers with a step-by-step exploration approach, especially as devices like network printers or some Android phones refuse networks that don't deal DHCP addresses.

It may be prudent for DHCP responses to look differently when no upstream is known (dunno, eg. not announce a default route, and have shorter lease times for the clients to receive the new routes as available), but please consider handing out addresses at all.

[timcoote]

I wonder if this is related to an issue that I get when my isp bounces the dsl link: ipv4 disappears from all internal interfaces, and the log fills with lines like this:

OpenWrt odhcpd[1091]: DHCPv4 failed to detect address: Address not available, wlan1

This is a practical issue as it stops the router working properly.