Hi,

thanks for getting in touch. The behaviour you described is tracked in bug #10813.
I am currently working on  a clean solution for this and bug #11502 but this takes time. The scripts involved in this are rather old (2007) which makes the fix more of a rewrite. 

You can see my progress here: 
https://git.ipfire.org/?p=people/jschlag/ipfire-2.x.git;a=shortlog;h=refs/heads/improve_network_startup 

As this needs a very good test a will reach out to the list when i have an iso image with all necessary changes.

Greetings Jonatan
Am 09.01.2022 um 04:04 schrieb Brad Spencer <spencer@jacknife.org>:

On 1/8/2022 10:03 PM, Jose Dias wrote:
I've had dhcp do that to me and it doesn't take a power failure but a downed isp will do.

My solution is to have a script run every 5 minutes to try again and after an hour reboot ipfire again.

My desktop just died and I'm rebuilding it but I can post that script if it's helpful.

Yes, I agree.  In the community post I linked to, I tried to explain details failure.

With my change to its startup arguments, I've been able to demonstrate that even if dhcpcd is unable to obtain an initial DHCP lease at boot, ipfire's boot sequence is not blocked, and dhcpcd does correctly keep retrying for longer than 60 seconds, and that ipfire reacts correctly when an IP is leased.  See

If you're interested, you can see my most recent followup in the community: https://community.ipfire.org/t/dhcp-client-on-red0-wont-reassign-ip-upon-reconnection/2455/38?u=spencer

So, I'm going to try this instead of rebooting.  The retries are frequent and cheap, and other (local) ipfire services remain available the whole time.

Thanks for the offer!

--
Brad Spencer