@townsenk64
I have the debug build running.
It didn't occur so far., but it does take a couple of days.

@marcosm said in Dyndns "freeDNS API Version 2 (v6)" not working:

I think it's a local issue. Does the code work with both IPv4 and IPv6 (set the first line to AF_INET for IPv4)?

Yes, I do have setup one for IPv4 and one for IPv6, both were working on 24.11 for some time. The issue with IPv6 started after the upgrade to 25.3-BETA.

Parallel there are two (one IPv4 and one IPv6) setup for duckdns.org using the Custom/Custom v6 service, which are running fine too.

@Maff

fresh install cleared it up

@marcosm I did some additional testing and managed to reduce the number of occurances of the error.

First I changed the WAN config, unchecked the "Do not wait for RA" (which was previously checked for some reason).

I then released the WAN lease, which triggered one error as seen before. When I renewed the WAN lease there were no errors, progress!

25.03-BETA (amd64)
built on Mon Apr 14 18:38:00 UTC 2025
FreeBSD 15.0-CURRENT

seems to have resolved some of this.

Yup could well be that.

@michmoor it is part of the base install, this lets us update it outside of a release

Cool. Looks good here too. Let us know if you see anything else.

For reference: https://redmine.pfsense.org/issues/16128

That patch should fix this. the 0.15.14 pkg version starts and runs fine. It will be in te next build which should be available very soon.

@stephenw10
Yes pppoe0 is bound to ix0

@DarkFnh Can you post the output of 'bt' and 'show registers' at the 'db>' prompt?

@marcosm I have tested and it works well.

@marcosm said in Rules order randomly changes:

At first glance, everything seems to be working, but we won't rush. I'll test it for some more time.

Yup, it will be fixed in the next update.

@Gertjan
Yes, it looks like the issue is indeed with the zombie process. If it happens again, I'll definitely check. Thanks for the idea.

@stephenw10 said in Traceroutes appears to be broken?:

set 'Firewall State Policy' to Floating States

Works excellent if 'Firewall State Policy' is set to 'Floating States'.

Something OT: In the ''Firewall State Policy', in the explanatory paragraph for 'Interface Bound States' are two tiny typo:

" ... If a packet attempts to takes an path through ..."
should be
" ... If a packet attempts to take a path through ..."

Fix is incoming.

@patient0 said in 25.03-BETA NAT64 / PREF64 Success and feedback:

is the 2.7.2 running on a Proxmox VM too?

No - bare metal (see signature)