[ previous ] [ next ] [ threads ]
 From:  Manuel Kasper <mk at neon1 dot net>
 To:  JR <tiresias at gmail dot com>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall-dev] default NTP server
 Date:  Sun, 17 Feb 2008 14:13:05 +0100
On 17.02.2008, at 12:52, JR wrote:

> While researching ntp to solve a problem with msntp on m0n0wall
> (http://m0n0.ch/wall/list/showmsg.php?id=339/75) I noticed this page
> at ntp.org basically asking developers like those of m0n0wall not to
> use pool.ntp.org as the default ntp server in the software, but to
> request a vendor zone instead. (eg. m0n0.pool.ntp.org)
> http://www.pool.ntp.org/vendors.html

Yes, that's quite interesting - if I'm not mistaken, then at the time  
I implemented (S)NTP in m0n0wall, the recommendation was for such  
projects to use pool.ntp.org. Guess this has changed in the meantime.  
I've applied for a vendor zone now and will make that the default in  
the next release. I'm also considering having it automatically replace  
pool.ntp.org with the new vendor zone in existing configs the first  
time the next version is booted (so that users can still permanently  
change it back to pool.ntp.org if they desire). Also, the default  
polling interval is probably too aggressive; I'll change that to once  
per hour.

> It's interesting that m0n0wall is even mentioned on that page, yet it
> does not follow the recommendation provided.

I've no idea why they list m0n0wall on that page. I was never  
contacted by them about this.

> I usually change my m0n0walls' ntp server anyway to get the benefit of
> using geographically closer servers, but I suspect many/most do not,
> and I think respecting the guidelines put forth by those providing the
> pool.ntp.org service is the responsible thing to do.

Yes, that's right... Thanks for digging up this information!