nice Brother! hahaha!! i think you made a Super Pfsense Server.  ;D  8)

@PiBa: You would enable that option if you 'need' the client-ip of the actual client for logging/permissions/other and cannot accomplish that by other means like x-forward-for header or proxy-protocol. Its certainly usefull, but causes some trouble as well.. (there is a warning message with it for a reason ;) ) Ok thank you. Everything is setup now the way we want it. Just a new cloud infrastructure coming as well. Then back to my usual programming day job ;) Thanks again for your help :)

Hi. @yahav02: hi javcasta this script work on https web site ? thenks It is not my script. You must go to the source: How To Block File Uploads Using Squid ACL’s http://nanlyx.blogspot.ie/2013/04/how-to-block-file-uploads-using-squid.html Regards

In answer to my own question I seem to have found a solution on this post. https://forum.pfsense.org/index.php?topic=72605.msg396370#msg396370

Hi BlueKobold, thanks for your reply. im not running a bridge im just trying to get to the ipsec nets on my pfsense. we are using sonicwalls now and it works, but i want to replace them with pfsense boxes, and i cant get this to work.

Of course, of course. Thanks i'll give that a shot. And no, it's on a separate port with a very strong password.

Hi John Thanks again goes to you for the great work. Yes this topic can be closed. Thanks pfsense team

Thanks.

@tigs: What do these result mean in real life? Nothing because you need -elapsed on there for it to tell you anything meaningful in a real-world context.

See:``` https://forum.pfsense.org/index.php?topic=121732.0 This thread is done for me. Thanks everyone!

start by looking in for clue's in the system logs & posting the relevant parts. also post the crashdump on pastbin & link it here

During install, there's a "Rescue config.xml" option, IIRC.

Got the logs. No idea how the consultant reached his conclusion as the system.log has no entries until a couple of hours after the outage started. In fact, none of the logs with entries during the timeframe around the outage show anything vaguely helpful except for documenting the precise time when things began going south; the timing-out of OpenvPN connections, the retry attempts for IPsec. Anyone know what a duplicate IP address looks like in the logs?