I’ve got a brand new ipfire installation (Core 162) and I had a power failure followed by a cable service outage thanks to some downed lines that helped me test automatic recovery. The bad news is that my red0 interface did not re-acquire any IP via DHCP after the cable modem re-acquired link.
Sequence of events:
- power fails, so ipfire box and cable modem are off
- power restored
- cable modem turns on but can’t connect to the ISP because the line is down in the neighbourhood
- ipfire turns on at the same time, and green network works fine, but because the bridged cable modem has no link to the ISP, no DHCP responses happen, of course
- cable lines are repaired and the modem automatically comes online successfully (untouched)
- ipfire red0 remains in the same state, without an IP assigned.
- ipfire requires a reboot in order to retry a lease on red0
I run my cable modem in bridge mode and just switched to ipfire a couple of days ago after manually running a “normal” Linux system as a firewall for over 20 years. I’ve never had this problem with the isc-dhcp-server service in Debian which has handled many similar events for decades.
My symptoms seem the same as those in this thread, where the DHCP client service in ipfire just isn’t even (re-)trying to get a lease.
I haven’t customized ipfire at all other than normal things in the UI except for a tiny custom file in /etc/unbound/local.d/ to override some irrelevant DNS results.
I will see what other information I can gather.