pfSense

Jim Pingle wrote:

The bug you linked is already fixed in 2.4.5-p1 and it was unlikely to be related to anything except accessing the GUI.

In my case the whole firewall would lock up for 30 seconds several times an hour. The dpinger process would hijack all of the CPU. All network traffic would come to a screeching halt. If I killed dpinger, it would eventually recover, only to recur again. I've found no reference to anything that sounds remotely like it other than the one I linked, and it most definitely was not limited to the GUI.

Upgrading to 2.5.0-DEV fixed it. I don't remember what version I was on before, but if it's possible to find that out from the firewall, I'm happy to share it so you can be a little less smug.

As for the rest of it, I've reported that after upgrading to 2.5.0-DEV the firewall no longer honored the pre-existing, working multi-WAN configuration and included steps I had to take to resolve it. You, as a developer or whatever you are, should be able to say, "oh interesting, that sounds like it might be X or Y, and we'll take a look."

Forums are most often the blind leading the blind, and I didn't come here asking for help. I came here telling you that your 2.5.0-DEV is broken and how I was able to work around it. Ignore it if you want - it's still broken.