On 8/23/15 10:44 PM, Volker Kuhlmann wrote:
> On Mon 24 Aug 2015 16:22:04 NZST +1200, Brady, Mike wrote:
>
>> It is not ticked on any (three) of the machines that I have just
>> looked at. This is not something that I would have ever changed.
>
> Perhaps my memory is wrong and I did change mine.
On Mon 24 Aug 2015 16:22:04 NZST +1200, Brady, Mike wrote:
> It is not ticked on any (three) of the machines that I have just
> looked at. This is not something that I would have ever changed.
Perhaps my memory is wrong and I did change mine. Why have an advanced
option that stops the whole thin
On 2015-08-24 15:25, Volker Kuhlmann wrote:
OK found it. Under access restrictions, the option
"Disable all except ntpq and ntpdc queries (default: disabled)."
must NOT be ticked! The default is ticked. This seems to prevent ntpd
altogether from talking to the time servers.
That looks like a
Oh, god, not again...
Search the list archives from about a month ago.
The consensus was, roughly, that the Ubiquity UniFi products were pretty good
but had some quirks.
As i recall, everything else discussed was either:
-insanely expensive, or
-crap (or both), or
-only works well for one or two
Does anyone have any recommendations for a/ac models, AP only, as is
only radio, no router/switch stuff? Dumb is good, I use pfsense already
and don't need more complexity in closed-source buggy devices.
Single-RJ45 perfect, as soon as there are LAN and WAN ports the problems
start (like everyone t
On Mon 24 Aug 2015 14:11:22 NZST +1200, Brady, Mike wrote:
> I think that the INIT states indicate that you are not in fact
> synced.
Yes, I took that for granted. But why? ntpdate to the same servers
connects fine. Default pfsense config - well I added one time server and
enabled ntpq.
It looks
On 2015-08-24 13:32, Volker Kuhlmann wrote:
On Mon 24 Aug 2015 12:16:28 NZST +1200, Brady, Mike wrote:
No issues here (also Pacific/Auckland) with any 2.2 release.
Well, mine is a stock 2.2.x install, about 12 months old, upgraded a
few
times to minor point releases. I hacked the php of squi
On Mon 24 Aug 2015 12:16:28 NZST +1200, Brady, Mike wrote:
> No issues here (also Pacific/Auckland) with any 2.2 release.
Well, mine is a stock 2.2.x install, about 12 months old, upgraded a few
times to minor point releases. I hacked the php of squid, squidguard and
ssh (out of necessity, no BUI
On 2015-08-24 11:33, Volker Kuhlmann wrote:
On Fri 26 Jun 2015 14:54:38 NZST +1200, Brian Caouette wrote:
Anyone else notice the clock is broke on 2.2.3? Anything time related
is seriously off.
Agreed. It's broken in 2.2.4 too.
At least the upgrade to 2.2.4 did not change the time zone
(Paci
Hello,
Le 2015-08-24 10:33, Volker Kuhlmann a écrit :
On Fri 26 Jun 2015 14:54:38 NZST +1200, Brian Caouette wrote:
Time synchronisation does not happen. I configured 2 time servers, both
reachable, and the system time is wrong.
pfsense # ntpdate -qu 0.pfsense.pool.ntp.org time.paradise.net.nz
On Fri 26 Jun 2015 14:54:38 NZST +1200, Brian Caouette wrote:
> Anyone else notice the clock is broke on 2.2.3? Anything time related
> is seriously off.
Agreed. It's broken in 2.2.4 too.
At least the upgrade to 2.2.4 did not change the time zone
(Pacific/Auckland) for me. I can no longer tell f
Adding the three lines
dnssec
dnssec-check-unsigned
trust-anchor=.,19036,8,2,49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
to dnsmasq in pfSense makes dnsmasq dnsssec aware. Is there a reason why
there is no tickable box to enable this in the GUI or wh
12 matches
Mail list logo
