[169163] in North American Network Operators' Group
Re: OpenNTPProject.org
daemon@ATHENA.MIT.EDU (Blake Dunlap)
Mon Feb 17 10:29:55 2014
In-Reply-To: <53022764.8080709@xmission.com>
From: Blake Dunlap <ikiris@gmail.com>
Date: Mon, 17 Feb 2014 09:28:16 -0600
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Peer means it considers the other side an equal and they will mutually skew
time together. If you have peer on for devices you don't consider your time
servers, you're opening yourself up to problems.
-Blake
On Mon, Feb 17, 2014 at 9:14 AM, Pete Ashdown <pashdown@xmission.com> wrote:
> On 2/17/14, 7:26 AM, George, Wes wrote:
> > I'll note that this is less than 140 chars, and therefore fits nicely in
> a
> > tweet.
> >
> > If you're on twitter, Signal boost the PSA, please.
> >
> > My edited example:
> https://twitter.com/wesgeorge/status/435404354242478080
> >
> > Wes George
> >
> >
> >
> > On 2/16/14, 10:03 PM, "Kate Gerry" <kate@quadranet.com> wrote:
> >
> >> add these to your ntp.conf
> >> restrict default kod nomodify notrap nopeer noquery
> >> restrict -6 default kod nomodify notrap nopeer noquery
>
> I seem to recall some issue with older Windows clients using peer for
> synchronization. Does not having "nopeer" contribute to DDoS
> amplification?
>
>
>
