I agree with the previous reply that this does not immediately look like a plain DHCP expiration problem. Your lease timings actually show the renewals were still within the valid lease window, so the WAN should have kept working even if one renewal failed temporarily.
The more interesting part is the repeated "send_packet: Host is down" messages. In FreeBSD that usually points lower in the stack, often interface state, driver hiccups, link negotiation, or even a gateway/ONT issue. Since you're using igc1, I'd definitely look closely at Intel i225/i226 related quirks because those chipsets have had intermittent stability complaints under BSD and Linux.
I would check a few things:
* `dmesg` for link up/down events around the exact timestamps
* Interface statistics for errors or resets
* Different ethernet cable and switch/ONT port
* Disable hardware offloading temporarily in OPNsense
* Force interface speed instead of auto negotiation as a test
Also interesting that recovery happened only after several failed renewal attempts. That almost sounds like the interface temporarily lost carrier or stopped transmitting properly rather than DHCP itself being broken.
The more interesting part is the repeated "send_packet: Host is down" messages. In FreeBSD that usually points lower in the stack, often interface state, driver hiccups, link negotiation, or even a gateway/ONT issue. Since you're using igc1, I'd definitely look closely at Intel i225/i226 related quirks because those chipsets have had intermittent stability complaints under BSD and Linux.
I would check a few things:
* `dmesg` for link up/down events around the exact timestamps
* Interface statistics for errors or resets
* Different ethernet cable and switch/ONT port
* Disable hardware offloading temporarily in OPNsense
* Force interface speed instead of auto negotiation as a test
Also interesting that recovery happened only after several failed renewal attempts. That almost sounds like the interface temporarily lost carrier or stopped transmitting properly rather than DHCP itself being broken.
"