Re: [pfSense] Cisco VPN

2016-04-22 Thread Karl Fife
I've done this. IIRC It was a PITA. I'm having trouble finding my notes but my recollection is that the Cisco nomenclature is different. Also, the only cyphers and keys I could make work were as follows: Key exchange v1 Phase 1 Auth Auth: Mutual PSK Nego: Main Phase 1 Prop AES 128 Sha 1 DH

Re: [pfSense] NTP Drift file not retained (NanoBSD) and "clipping" of

2016-04-22 Thread Vick Khera
On Fri, Apr 22, 2016 at 5:10 PM, Karl Fife wrote: > Obviously not retained in the case of an abend, but notably ALSO not > retained during a normal reboot. Is there a strategic reason this hard-won > calibration is not retained? I agree this should be preserved the same way the RRD files and D

[pfSense] NTP Drift file not retained (NanoBSD) and "clipping" of

2016-04-22 Thread Karl Fife
It appears that pfSense 2.3 and earlier on nanoBSD does not retain its system clock calibration between reboots. On certain (certified) systems, this appears to trigger a sequence in which the offset gets further and further behind, and NTPD tries in vain to slew the clock, increasing the drif