Re: [AFMUG] OT DHCP update

2016-10-18 Thread That One Guy /sarcasm
> > On 10/18/2016 1:26 PM, Chuck McCown wrote: > > Yep, this could be like Y2K. Once the clock rolls, I don’t think NTP yet > has a field showing epoch number so how do you differentiate between 1900 > and 2036? > > *From:* Paul Stewart > *Sent:* Tuesday, October 18,

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Paul Stewart
0 years to prepare for it. >>> >>> >>> bp >>> >>> >>> On 10/18/2016 1:26 PM, Chuck McCown wrote: >>>> Yep, this could be like Y2K. Once the clock rolls, I don’t think NTP yet >>>> has a field showing epoch num

Re: [AFMUG] OT DHCP update

2016-10-18 Thread George Skorup
? *From:* Paul Stewart *Sent:* Tuesday, October 18, 2016 2:23 PM *To:* af@afmug.com *Subject:* Re: [AFMUG] OT DHCP update Clock rolls over … On Oct 18, 2016, at 4:13 PM, Chuck McCown wrote: A few weeks ago I was requesting help in thinking through some DHCP lease issues. Turns out, we think, t

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Paul Stewart
> > > bp > > > On 10/18/2016 1:26 PM, Chuck McCown wrote: >> Yep, this could be like Y2K. Once the clock rolls, I don’t think NTP yet >> has a field showing epoch number so how do you differentiate between 1900 >> and 2036? >> >> From: Paul S

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Chuck McCown
Too bad for the programs that use NTP numbering as the time and date. From: Bill Prince Sent: Tuesday, October 18, 2016 2:32 PM To: af@afmug.com Subject: Re: [AFMUG] OT DHCP update Once 2036, or even 2035 shows up, set a flag somewhere that we are preparing for rollover. Heck, do it now

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Chuck McCown
that their clocks are getting set to 0xh by something. I doubt NTP is reporting that date. From: That One Guy /sarcasm Sent: Tuesday, October 18, 2016 2:28 PM To: af@afmug.com Subject: Re: [AFMUG] OT DHCP update my helmet is at the shop right now, so forgive my ignorance. but what? On

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Bill Prince
6? *From:* Paul Stewart *Sent:* Tuesday, October 18, 2016 2:23 PM *To:* af@afmug.com *Subject:* Re: [AFMUG] OT DHCP update Clock rolls over … On Oct 18, 2016, at 4:13 PM, Chuck McCown wrote: A few weeks ago I was requesting help in thinking through some DHCP lease issues. Turns out, we think, tha

Re: [AFMUG] OT DHCP update

2016-10-18 Thread That One Guy /sarcasm
and 2036? > > *From:* Paul Stewart > *Sent:* Tuesday, October 18, 2016 2:23 PM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] OT DHCP update > > Clock rolls over … > > > > On Oct 18, 2016, at 4:13 PM, Chuck McCown wrote: > > A few weeks ago I was requesting help in t

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Chuck McCown
Yeah the NTP clock numbering system. Affects everything. From: Bill Prince Sent: Tuesday, October 18, 2016 2:26 PM To: af@afmug.com Subject: Re: [AFMUG] OT DHCP update +1. That would be my guess too. bp On 10/18/2016 1:23 PM, Paul Stewart wrote: Clock rolls over … On Oct 18

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Bill Prince
+1. That would be my guess too. bp On 10/18/2016 1:23 PM, Paul Stewart wrote: Clock rolls over … On Oct 18, 2016, at 4:13 PM, Chuck McCown > wrote: A few weeks ago I was requesting help in thinking through some DHCP lease issues. Turns out, we think, that there w

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Chuck McCown
Yep, this could be like Y2K. Once the clock rolls, I don’t think NTP yet has a field showing epoch number so how do you differentiate between 1900 and 2036? From: Paul Stewart Sent: Tuesday, October 18, 2016 2:23 PM To: af@afmug.com Subject: Re: [AFMUG] OT DHCP update Clock rolls over

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Jaime Solorza
First contact? On Oct 18, 2016 2:13 PM, "Chuck McCown" wrote: > A few weeks ago I was requesting help in thinking through some DHCP lease > issues. Turns out, we think, that there were some Calix system clock > fruitiness. > > Anyone care to guess what is magic about February 7, 2036? >

Re: [AFMUG] OT DHCP update

2016-10-18 Thread Paul Stewart
Clock rolls over … > On Oct 18, 2016, at 4:13 PM, Chuck McCown wrote: > > A few weeks ago I was requesting help in thinking through some DHCP lease > issues. Turns out, we think, that there were some Calix system clock > fruitiness. > > Anyone care to guess what is magic about February 7,

[AFMUG] OT DHCP update

2016-10-18 Thread Chuck McCown
A few weeks ago I was requesting help in thinking through some DHCP lease issues. Turns out, we think, that there were some Calix system clock fruitiness. Anyone care to guess what is magic about February 7, 2036?