9 Apr 2006

D-Link and their NTP vandalism

Here is an interesting article about how badly implemented firmware by DLink cause a Danish NTP operator a lot of money, problems and time.

To put it simply, computers update their clocks using a method call NTP (Network Time Protocol) whereby they ask timekeeper servers (NTP server) for the correct time.

In order for many functions of the computer to work properly, accurate time is extremely important. This goes for hardware like network routers too. Here comes the stupid part. It seems that the popular router maker D-Link has make a mistake and included a private NTP server in their list of NTP servers in a new version of their router firmware without asking permission. In the end, lots and lots of routers around the world start asking the poor NTP server for the correct time and all the addition bandwidth adds up and is very very costly to the person who is running the NTP pro bono publico.

The problem is D-Link is not admitting to the mistake and puts a lawyer who probably does not know what he is dealing with on the case.

Well, if you are using a D-Link router, check if you are using one of the offending firmware versions. Upgrade quickly if there is a fixed firmware available. Else do write to D-Link to ask for a fix.

This issue highlights some problems:
  1. Hardware router firmware writers might not be competent. If you are relying on them to protect your office or home network from external threats, think again.
  2. The slow network traffic you are experiencing might not be the fault of your ISP. You could be sending out thousands of network packets because your computer has been taken over. And no I am not kidding! If your network card/wireless adapter is blinking like crazy when you are not doing anything that connects to the web, you are it!
  3. Not everyone can be programmers. Simple as it may seems, especially with all the new and friendly IDE available now, it takes a lot to be a skilled programmer. A lot. Be nice when you meet a competent one.

No comments: