@kiokoman Ive done this and I'm gonna wait and see what happens.

Ps. That was the simplest and the smoothest restore process of any restore Ive ever done in my whole life.

Same here.

The new "experimental" mode is iftop and it's what we plan to use from here on.

Both binaries will exist on the firewall for now, but the one that gets used is the one you select in that option.

@derelict said in Very big pull request:

Yes that looks like #gitfail. (I am guilty of doing exactly the same thing).

Yep! Don't ask me how I recognized what the problem is ... 😁.

I would look at the other packages that have python as a dependency like pfBlockerNG:
https://github.com/pfsense/FreeBSD-ports/tree/devel/net/pfSense-pkg-pfBlockerNG-devel

Steve

Thank you @vesalius it is fixed now.

right
I didn't realize it was mandatory 🙄

Unrelated; service_watchdog seems to have not responded on this one.

Perhaps I should be less stupid and make sure service watchdog is actually configured...

@stephenw10 not sure ill make sure to see if 2 processes for miniupnp next time. Thanks for the reply

yup 1000%

OK thx

@motific Not sure; not using pfblocker-ng.

I have reverted to the latest Stable version and it is now working as expected. I will leave it like that for now, and maybe set up a 2.5 test again in a short while.

Elfranko

I didn't find issues at all, I'm not using traffic shapers or any super advanced feature. I think.

In the end I sort of panicked and restored the official version just for peace of mind. I think it might be ready to go, at least in VMs.

@jimp said in pfsense crash report happens daily then reboots:

I'd blame the bxe driver.

appreciate the feedback ive uploaded the file in text document if that helps.

textdump.txt