DHCP IP on WAN port is 0.0.0.0/8

[Offspring]

This happened a couple of weeks ago, but the IP from my ONT connection suddenly went to 0.0.0.0/8 and I've lost the ability to get any packets outside of my network. I can ping the gateway for the device, on my ISPs network, but that's as far as I can get. I've tried restoring the config, tried restoring an image backup, and I've tried to clone the MAC address of my old Amplifi router but I'm still unable to pull a proper IP. Had anyone seen anything like this, and know what I might be able to do to fix this?

Specs are a SuperMicro X10SLH-LN6TF running in Proxmox with 4 cores and 8GB of RAM.

It was running fine for about a month, then it just changed to this IP randomly during the day. No config or hardware changes were made prior to the IP deciding it was 0.0.0.0/8,.

[CJ]

Have you rebooted your ONT?  What do your logs show?

I assume you're using DHCP for the WAN so you need to figure out why you're not getting a lease.  It shouldn't have anything to do with your config.

[Offspring]

Yeah, I've rebooted the ONT a few times yet nothing changes. It's odd to me that it just happened randomly while it was already up and running, rather than after a reboot.

Which logs? The firewall logs don't help, as it's constantly just showing the system trying to reach out via the AdGuard and Unbound DNS servers and not able to go very far.

[CJ]

Yeah, I've rebooted the ONT a few times yet nothing changes. It's odd to me that it just happened randomly while it was already up and running, rather than after a reboot.

Which logs? The firewall logs don't help, as it's constantly just showing the system trying to reach out via the AdGuard and Unbound DNS servers and not able to go very far.

DHCP leases are constantly renewed, not just on reboot.  IIRC, the process typically begins somewhere between half and three quarters time remaining on the lease.

The DHCP client logs should be showing up under System: Log Files: General.  That may provide some insight.  If you go to the Interfaces: Overview page you might also have the option to force a DHCP reload to produce some logs.

If nothing shows up under either of those I would take a packet capture and see what's going on between OPNsense and your ONT.

[cookiemonster]

try system > log files >  general.
Change to Informational from the category drop down and search WAN in the search field.
Might give some clue.

[franco]

The 0.0.0.0 quirk is gone since 24.1. But the problem remains: the DHCP client could not manage to (re)assign the lease likely because the server wasn't ACK'ing it for one reason or another.


Cheers,
Franco

[CJ]

try system > log files >  general.
Change to Informational from the category drop down and search WAN in the search field.
Might give some clue.

Isn't that what I said? :D

The 0.0.0.0 quirk is gone since 24.1. But the problem remains: the DHCP client could not manage to (re)assign the lease likely because the server wasn't ACK'ing it for one reason or another.


Cheers,
Franco

I didn't realize that was a quirk in prior versions.  What was the change to fix it?  The 0.0.0.0, not the fact that DHCP isn't getting a lease.

[franco]

See https://github.com/opnsense/core/commit/549c180e92 and subsequent review link.


Cheers,
Franco

[cookiemonster]

try system > log files >  general.
Change to Informational from the category drop down and search WAN in the search field.
Might give some clue.

Isn't that what I said? :D

Oh yes. Maybe typing at the same time :)