Re: [pfSense] Strange timezone behavior and then full stop

2015-08-26 Thread Wade Blackwell
Thanks Steve. On Aug 26, 2015 9:04 AM, Steve Yates st...@teamits.com wrote: Wade Blackwell wrote on Wed, Aug 26 2015 at 10:27 am: Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the

Re: [pfSense] Strange timezone behavior and then full stop

2015-08-26 Thread Steve Yates
Wade Blackwell wrote on Wed, Aug 26 2015 at 10:27 am: Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting

Re: [pfSense] Why no dnssec in dnsmasq by default?

2015-08-26 Thread Adrian Zaugg
On 24.08.15 20:35, Chris Buechler wrote: On Sun, Aug 23, 2015 at 9:28 AM, Adrian Zaugg a...@ente.limmat.ch wrote: why it is not enabled by default? ... and because all the DNS servers used as forwarders must support DNSSEC too for it work. And thank you for your answer, Chris. Regards,

[pfSense] Strange timezone behavior and then full stop

2015-08-26 Thread Wade Blackwell
Good morning PF group, I have *2.2.4-RELEASE * (amd64)running virtually in a VSPhere 5.5 environment. I just recently upgraded from 2.2.3. So I woke up to the network down, console complaining about timezones and no IP addresses on any of the interfaces. I rolled back configs from the