said in Endpoint-independent Outbound NAT (eimnat) rules: And those two options should be mutually exclusive, I see no point in allowing both in one rule. I have to stop myself again. It does make sense. First it should try for Static Port. If it can't, it should use EIM. Btw. the second linked test-site always returns the same result to me, seems to be broken.

Once 25.11 is released we may port back frr10 to it.

What i ended up doing is to go the shell route (thanks for the suggestion, @SteveITS) and started to kill processes like php-fpm and openvpn, which still showed up despite me stopping the service. Update worked fine after that.

@Gertjan thanks. Clearing the DHCP leases did the trick. I cleared them before I upgraded and when the upgrade completed Unbound was happy.

@stephenw10 thank you

Hmm, that's very generic. That function is used by numerous things. Was anything else logged at the time?

@p1erre said in [solved] wireguard issue: same like there: https://forum.netgate.com/post/1229105 but the bug fix for redmine#16475 should be in the latest RC, so disabling limiters shouldn't be required? I had a limiter for buffer bloat active on the WAN when I tested earlier, so perhaps what you saw was another bug manifesting? Btw, I didn't test remote access WG in any of the previous 25.11 versions so I have nothing to compare with.

@Gertjan said in Kea registrations: Looks like you have a ' or " in one of your host names. no, the errors were caused by cached leases from previous RC. Once I had cleared them the issues was gone.

I found a config created just before the package removal fest begun and managed to restore it. There's no automatic installation of packages it seems, and manually installing Nexus gives me this, unhelpful...: [image: 1764196584371-screenshot-2025-11-26-at-23.35.47-resized.png] However, I managed to install it running "pkg install pfSense-pkg-Nexus". The other packages have also been reinstalled, and my pfSense appears to be back in action, fingers crossed.

@marcosm But it is only the DHCP entries that are duplicated, none of the other entries are which suggests it's something specific to DHCP

Yes.

@pst said in Some observations testing 25.11.r.20251118.1708 on Netgate 2100: DNS lookup of DHCPv6 leases As has been reported elsewhere, I noticed DNS lookup is not working for IPv6 addresses. Currently : nslookup host gives me the ipv4 address, and nslookup host.t gives the ipv6 address. Marcos was able to successfully address it yesterday.

Thanks for the report. This will be fixed in the release.

I've been seeing the same since last week. One or two insta-refreshes is all it's been taking.

@marcosm Appreciate all this clarification. Thanks.

Well it far higher than even the 1M default we usually set and that is generally far bigger than it needs to be. But you also show only 1400 states which is nothing. If you exhaust the mbufs that would definitely cause a problem. But you should also see that logging an error.

@SteveITS Thank you!!

Are you able to reproduce this, e.g. by rolling back the BE and trying the update again?

@marcosm I just upgraded to the latest version, and the Wireguard service is now running.