Messages

I just installed the latest (24.1.8) of opnsense in a Proxmox VM with the CPU set to Host for the VM. My host's CPU is an i3-10100. So I tried "None/ACPI" and "Intel" in the Thermal Sensors setting under Miscellaneous to no avail. Any thoughts?

> In pfsense, you can use a failover gateway group as a default gateway so switching happens with that.

[citation needed]

I'm speaking from experience but here's the citation:

https://docs.netgate.com/pfsense/en/latest/routing/gateways.html#managing-the-default-gateway

You can use gateway groups (https://docs.netgate.com/pfsense/en/latest/routing/gateway-groups.html) for default gateway switching. And by default, gateway groups "keep states on gateway recovery" which means that it will keep the existing states on the backup gateway "until they reconnect".

Is this what you're trying to say as well? The existing connections don't get affected by the primary gateway recovery but new connections will go through the recovered primary gateway? If so, then that is totally fine by me and I don't see any issues there.

> But why isn't the gateway priority kicking in when the primary connection goes back online

Why should it? The connection is established and working.

Because it is the "primary" connection. The established connections shouldn't get affected but new connections should go through the primary connection again.

If the expectation from the approach taken matches the implementation done there is another question. :)


Cheers,
Franco

Not really sure what you mean by this?

I get it. But why isn't the gateway priority kicking in when the primary connection goes back online? In pfsense, you can use a failover gateway group as a default gateway so switching happens with that. Is there some disadvantage with that implementation that made that feature not available in opnsense?

Talking about realistic, if a 5G connection is set as a secondary WAN in opnsense and a fiber optic connection as primary, wouldn't you want the default gateway to swtich back to the fiber optic connection when it comes back online (assuming it swtiched over to the 5G connection)?

So is this a bug? Because when using gateway switching, it technically should switch back to the primary gateway when it comes back up. Hopefully, someone from the opnsense team can confirm this.

Ahaha, I guess everyone is just assuming it gets deprecated at some point. But yeah, when KEA gets full blown, then I'm ok moving to it even if the register DHCP leases option isn't applicable for it. I'll cross the bridge when we get there.

Are you saying that when Kea becomes the only DHCP server available and ISC gets removed, the "register DHCP lease" option in unbound will be removed?

I completely agree. Patrick has been helpful to a lot of people in this forum. I don't mean any offense with my questions.

Ok, thanks for the confirmation! This is one other thing that I'm glad I switched over from pfsense to opnsense :) This issue has been existing for so many years with pfsense now and they don't care at all.

I'm wondering though. Is there a reason why "register DHCP leases" is disabled in the unbound settings by default?

Ok. So Patrick's response above is not accurate now? No offense intended. I'm just confused on replies that are a bit contradicting.

In pfsense, when unbound restarts, it loses all of its cache. I see that in opnsense, that unbound option is set to disabled/unchecked which means that restarts won't really affect them. Is that option there as a workaround for this?

The only reason I want DHCP leases registered in unbound is so that I can see their friendly names in AdguardHome as it is using unbound as a reverse DNS server. I don't care about pinging/reaching the DHCP devices by name.

@migugmail , can you confirm what exactly does the "Primary DNS" setting in the AdGuardHome plugin do when AGH listens at port 53? I don't see any documentation about it and the single line help line there is not that helpful.

I just transitioned from pfsense to opnsense and wondering if this DNS issue is solved in opnsense? When a new device goes through the DHCP process and I have "register DHCP leases" checked in Unbound, does Unbound restart itself? This has been an issue with pfsense until now and I just kept the option disabled which means I can't resolve DHCP devices.