Comments on: When The (Net) Time Stood Still http://gigaom.com/2006/04/14/when-the-net-time-stood-still/ Sat, 11 Feb 2012 12:44:45 +0000 hourly 1 http://wordpress.com/ By: markbnj http://gigaom.com/2006/04/14/when-the-net-time-stood-still/#comment-117102 Sun, 16 Apr 2006 02:44:51 +0000 http://gigaom.wordpress.com/2006/04/14/when-the-net-time-stood-still/#comment-117102 Both the current D-link, and the previous netgear incidents are discussed above in my blog.

As someone who’s implemented a WHOLE bunch of ntp servers over the years (first thing done when installing/taking over a lab)
I can safely report that I NEVER connected to ANY stratum 1 NTP servers!
Markbnj

]]> By: DaScud http://gigaom.com/2006/04/14/when-the-net-time-stood-still/#comment-117101 Fri, 14 Apr 2006 20:38:00 +0000 http://gigaom.wordpress.com/2006/04/14/when-the-net-time-stood-still/#comment-117101 This reminds me of a similar incident a couple of years ago when Netgear wireless routers flooded the ntp server at Univ of Madison with ntp queries.
A simple firmware upgrade fixed it although i am unsure as to how many consumers are willing to “risk” performing firmware upgrades on their router or even aware that the problem exists in the first place.

It should have been easy enough to make the ntp server an options field so that a firmware update would not be required and in any case netgear et. al should at least use the ntp server pool rather than statically hardcode ntp servers without prior permission from the admins.

]]> By: Daniel Spisak http://gigaom.com/2006/04/14/when-the-net-time-stood-still/#comment-117100 Fri, 14 Apr 2006 18:04:56 +0000 http://gigaom.wordpress.com/2006/04/14/when-the-net-time-stood-still/#comment-117100 D-Link is going to have an announcement regarding this issue within the next week is my understanding. Don’t ask me what its going to be but it should bring this to a good conclusion I have been told.

]]>