Thanks for your response.  I killed the proc, made sure all packages are up to date, and it's been fine for several hours now.  I will be scheduling the upgrade to 2.2.6 in the next 14 days - this sits in front of a customer portal, so we have to give them at least 14 days before we interrupt service :)  maybe I'll get the chance to build a redundant unit out of this…..

You know it's getting really bad when you spend sleepless nights desperately trying to solve a tough firewall issue, only to eventually find the most useful information in all of the internet ends up being a solution to your exact problem which you yourself wrote four years ago. https://forum.pfsense.org/index.php?topic=48891.0 The PXE boot still is not working, but the proxy appears to be passing traffic now. I will write this up as a bug/feature this time since I never got any feedback the last time, and then I forgot about it.

Oh yeah this has me drooling!!!  F__K that would be sweet ;) I may have to do this – heheeheh!!! If you want the 3.1.1 version, I compile it all the time for windows both 32 and 64 bit..  Since nobody else seem to be doing it that I could find.. You can grab it here http://files.budman.pw/

Yes. Only DHCP server. Everything else works just fine. I should say that I am running 2.3 so maybe there is a bug?

Dear Jimo and Johnpoz, Thank you for the answers! I totally forgot the caching mechanism. It's clear. Have a nice day!

https://doc.pfsense.org/index.php/Main_Page There are also about a zillion guides, tutorials and videos online about pfSense.

Seems like in 2.2.6 the problem gets worse.

/var/log contains all of the available logs, including system and ipsec.  I'm just guessing with the ipsec log, since it may only have connection-related details and not anything about the plumbing.

I've used NTopNG (you can install this from the Packages section on your PFS) to monitor traffic and to get long-term stats as well. The only thing to be aware of is the disk space that NTop can use up over time, so make sure you have a sufficiently large drive to handle the logs.

@KOM: I bitched about this already: https://forum.pfsense.org/index.php?topic=104969.0 and was told you can use Save As, but that only saves the html of the frame, not the actual content.  So you're stuck extracting the URL manually from the dense wall of code. Just tried Firefox Downloadhelper , works great, thanks!

there is no complete CLI (yet) there is no API (yet) both are in the pipeline for the (distant) future. It is possible to import/replace/adjust the xml from command line. https://doc.pfsense.org/index.php/How_can_I_reload_the_config_after_manually_editing_config.xml

@cmb: There is no need to rehash when using bash. I was supposing it. Thanks you.

I just booted directly from an USB installer and everything went smoothly. My Mac mini is from 2012, if you have an older one might be different!

If your ISP will support it pfSense will bond connections using MLPPP. Ive used this with my ISP for a number of years now and it works good.  Just one WAN address.