OK I think I've replicated this locally. We are digging into it....

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

Can't be patched as normal unfortunately. I'm hoping the next build is available soon but can't say when for certain.

@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)

Actually it looks like we have replicated it locally so may not need it. I'll let you know, thanks!

@stephenw10 said in 25.03-BETA on hyper-v 100% CPU-usage:

If you boot a test pfSense VM in Hyper-V does it also show that?

You mean the 25.03-BETA problem? Even if I would set one up, I "lost" all my registrations for another Plus. But even if I could do it, it wouldn't be in much use. Really the only thing I can do is a small test run on my main pfSense but I will need to revert back after some hours.

I am already thinking to move my pfSense-VM into the nested Proxmox host I have running in Hyper-V. So much fun with all the switching/bridging. And I would need another activation for sure. In the end, I am just an (ab)user 😉

The beta build we're working on now will have that view fixed up to be more like the older display:

7eea5ce5-7f7f-479c-a38b-bad3d0d8f5c8-image.png

@stephenw10 it works now for me too. The "New Topic" button did show up.