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?

No.

Use a BSD system. Install pfSense to the other disk, then mount that old disk on the new pfSense install.

I'm a little confused about what you are doing. If you want to connect machines in site 2 to some of the machines in site 1, just make the phase 2 match 192.168.100.32/29. Don't know why you are changing gateways, etc. Anything on site 1's LAN is going to be directly connected, messing with your subnet masks is not the way of it. If you want to restrict traffic between machines on the LAN, put them on different interfaces/subnets.

Those are logs from the pfSense GUI, not from squid.

It's dead simple. There isn't much to debug or much to go wrong. Most of the time any error is from an incorrect password.

Yeah I have read that DNSSec might cause the issue, but I can't boot the system. So how should I disable DNSSec?