> On 14 May 2019, at 08:41, Mark Tinka wrote:
>
>
>
> On 9/May/19 02:47, Bryan Holloway wrote:
>
>>
>>
>> Hawai'i and Arizona can add/subtract without looking at the damn
>> calendar. I'm just sayin' I'd like to see more of that.
>
> Well, 2 months ago, the EU parliament voted to scrap
On 9/May/19 02:47, Bryan Holloway wrote:
>
>
> Hawai'i and Arizona can add/subtract without looking at the damn
> calendar. I'm just sayin' I'd like to see more of that.
Well, 2 months ago, the EU parliament voted to scrap daylight saving
time from 2021. This would also apply to the UK if
igent Computing Solutions
> http://www.ics-il.com
>
> Midwest-IX
> http://www.midwest-ix.com
>
>
> From: "Christopher Morrow"
> To: "nanog list"
> Sent: Thursday, May 9, 2019 2:16:59 PM
> Subject: Re: NTP for ASBRs
...
-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest-IX
http://www.midwest-ix.com
- Original Message -
From: "Christopher Morrow"
To: "nanog list"
Sent: Thursday, May 9, 2019 2:16:59 PM
Subject: Re: NTP for ASBRs?
On Thu, Ma
Royce Williams :
> > Anybody know of anything fitting that description that you might want
> > to deploy in a data center as a Stratum 1? If such a creature exists I
> > shall contrive to get my lunch hooks on one and write a driver for it.
>
> That would be fantastic. I mentioned it on Freenode
On Thu, May 9, 2019 at 3:12 PM Andy Smith wrote:
>
> Hello,
>
> On Wed, May 08, 2019 at 10:27:30PM -0400, Christopher Morrow wrote:
> > UTC is nice
> > EST is nice
> > PDT is nice..
> >
> > pick one, deal with the eccentricities of that decision without
> > foisting your religion on the rest of
Hello,
On Wed, May 08, 2019 at 10:27:30PM -0400, Christopher Morrow wrote:
> UTC is nice
> EST is nice
> PDT is nice..
>
> pick one, deal with the eccentricities of that decision without
> foisting your religion on the rest of me. :)
Yes and no. Anything non-UTC can cause issues when working
Bryan Holloway wrote:
> On 5/8/19 7:55 PM, Brian Kantor wrote:
> > On Wed, May 08, 2019 at 07:47:56PM -0500, Bryan Holloway wrote:
> > >
> > > When a NOC-ling, in their own local timezone, says, "hey, what happened
> > > two hours ago?", they have to make a calculation.
> >
> > Clocks are cheap.
On Wed, May 8, 2019 at 11:12 PM Eric S. Raymond wrote:
> Chris Adams :
> > Once upon a time, Royce Williams said:
> > > The La Crosse 404-1235UA-SS UltrAtomic (not affiliated, just a fan)
> tracks
> > > DST - and even leap seconds. They have much better reach than previous
> > > similar clocks.
Chris Adams :
> Once upon a time, Royce Williams said:
> > The La Crosse 404-1235UA-SS UltrAtomic (not affiliated, just a fan) tracks
> > DST - and even leap seconds. They have much better reach than previous
> > similar clocks.
>
> Looks like somebody finally brought a clock to market that uses
On Wed, May 8, 2019, at 14:21, Lars Prehn wrote:
> Hi everyone,
>
> do you NTP sync your AS boundary routers? If so, what are incentives for
> doing so? Are there incentives, e.g. security considerations, not to do it?
Hi,
We (and I suppose a lot of others) do sync the border routers like any
Once upon a time, Royce Williams said:
> The La Crosse 404-1235UA-SS UltrAtomic (not affiliated, just a fan) tracks
> DST - and even leap seconds. They have much better reach than previous
> similar clocks.
Looks like somebody finally brought a clock to market that uses the
new-format
On Wed, May 8, 2019 at 7:16 PM Bryan Holloway wrote:
> On 5/8/19 7:55 PM, Brian Kantor wrote:
> > On Wed, May 08, 2019 at 07:47:56PM -0500, Bryan Holloway wrote:
> >> 100% true. But there is also a practical side to this ...
> >>
> >> When a NOC-ling, in their own local timezone, says, "hey,
On 5/8/19 10:15 PM, Bryan Holloway wrote:
On 5/8/19 7:55 PM, Brian Kantor wrote:
On Wed, May 08, 2019 at 07:47:56PM -0500, Bryan Holloway wrote:
100% true. But there is also a practical side to this ...
When a NOC-ling, in their own local timezone, says, "hey, what happened
two hours ago?",
On 5/8/19 7:55 PM, Brian Kantor wrote:
On Wed, May 08, 2019 at 07:47:56PM -0500, Bryan Holloway wrote:
100% true. But there is also a practical side to this ...
When a NOC-ling, in their own local timezone, says, "hey, what happened
two hours ago?", they have to make a calculation. And that
> isn't the point: "Pick one for all of your things, stick to that one
> thing" it's find if you pick central indiana time, if you are setting
> the same everywhere and keeping it update properly
i find the time zone they choose says a lot about an operation. can be
a flag of parochialism.
On Wed, May 8, 2019 at 9:42 PM Valdis Klētnieks wrote:
>
>
> Newfoundland time, anybody? :)
>
isn't the point: "Pick one for all of your things, stick to that one thing"
it's find if you pick central indiana time, if you are setting the
same everywhere and keeping it update properly...AND you
--- valdis.kletni...@vt.edu wrote:
From: "Valdis Klētnieks"
On Wed, 08 May 2019 14:00:11 -0700, "Scott Weeks" said:
> From: Job Snijders
>
> on this topic, i strongly recommend to operate all
> devices in the Etc/UTC timezone, this makes
> coordination with external entities much easier.
>
On Wed, 08 May 2019 14:00:11 -0700, "Scott Weeks" said:
> From: Job Snijders
>
> on this topic, i strongly recommend to operate all
> devices in the Etc/UTC timezone, this makes
> coordination with external entities much easier.
>
>
>
> Yes, this! Holy
On Wed, May 08, 2019 at 07:47:56PM -0500, Bryan Holloway wrote:
> 100% true. But there is also a practical side to this ...
>
> When a NOC-ling, in their own local timezone, says, "hey, what happened
> two hours ago?", they have to make a calculation. And that calculation
> annoyingly depends
On 5/8/19 6:54 PM, Scott Weeks wrote:
--- br...@shout.net wrote:
From: Bryan Holloway
On 5/8/19 4:00 PM, Scott Weeks wrote:
--- j...@ntt.net wrote:
From: Job Snijders
on this topic, i strongly recommend to operate all
devices in the Etc/UTC timezone, this makes
coordination with external
--- br...@shout.net wrote:
From: Bryan Holloway
On 5/8/19 4:00 PM, Scott Weeks wrote:
> --- j...@ntt.net wrote:
> From: Job Snijders
>
> on this topic, i strongly recommend to operate all
> devices in the Etc/UTC timezone, this makes
> coordination with external entities much easier.
>
On 5/8/19 4:00 PM, Scott Weeks wrote:
--- j...@ntt.net wrote:
From: Job Snijders
on this topic, i strongly recommend to operate all
devices in the Etc/UTC timezone, this makes
coordination with external entities much easier.
Yes, this! Holy crap I
--- j...@ntt.net wrote:
From: Job Snijders
on this topic, i strongly recommend to operate all
devices in the Etc/UTC timezone, this makes
coordination with external entities much easier.
Yes, this! Holy crap I come upon a lot of networks
that
> Vincent Bernat
> Sent: Wednesday, May 8, 2019 3:22 PM
>
> ❦ 8 mai 2019 09:56 +02, Lars Prehn :
>
> > do you NTP sync your AS boundary routers? If so, what are incentives
> > for doing so? Are there incentives, e.g. security considerations, not
> > to do it?
>
> Ensure you have a firewall
On Wed, 8 May 2019 07:56:33 +
Lars Prehn wrote:
> do you NTP sync your AS boundary routers? If so, what are incentives for
> doing so? Are there incentives, e.g. security considerations, not to do it?
In addition to what others have mentioned, if these systems are to
perform route origin
On 8/May/19 16:22, Vincent Bernat wrote:
> Ensure you have a firewall rule in place to prevent people to use your
> router for NTP amplification. NTP clients are also servers. On Juniper
> devices:
Yep, that's a nasty little situation in Junos that took me a week to
figure out back in the day
On 8/May/19 09:56, Lars Prehn wrote:
> Hi everyone,
>
> do you NTP sync your AS boundary routers? If so, what are incentives
> for doing so? Are there incentives, e.g. security considerations, not
> to do it?
Yes.
There are probably a lot of technical reasons you will receive from
folk, but
On Wed, May 8, 2019 at 8:38 AM Job Snijders wrote:
>
> Dear Lars,
>
> On Wed, May 08, 2019 at 09:56:33AM +0200, Lars Prehn wrote:
> > do you NTP sync your AS boundary routers?
>
> yes
>
> > If so, what are incentives for doing so? Are there incentives, e.g.
> > security considerations, not to do
You will also need to add you localhost as a source if you want to show that
ntp association status on the router
apply-flags omit;
term allow-ntp {
from {
source-prefix-list {
ntp-server;
localhost;
}
protocol udp;
port ntp;
}
❦ 8 mai 2019 09:56 +02, Lars Prehn :
> do you NTP sync your AS boundary routers? If so, what are incentives
> for doing so? Are there incentives, e.g. security considerations, not
> to do it?
Ensure you have a firewall rule in place to prevent people to use your
router for NTP amplification.
Dear Lars,
On Wed, May 08, 2019 at 09:56:33AM +0200, Lars Prehn wrote:
> do you NTP sync your AS boundary routers?
yes
> If so, what are incentives for doing so? Are there incentives, e.g.
> security considerations, not to do it?
The major advantage of NTP syncing your routers is that it
Hi everyone,
do you NTP sync your AS boundary routers? If so, what are incentives for
doing so? Are there incentives, e.g. security considerations, not to do it?
Best regards,
Lars
33 matches
Mail list logo
