Does the White Russian 0.9 DynDNS client suck just as much?

VirginSnow at vfemail.net VirginSnow at vfemail.net
Mon May 14 09:22:02 EDT 2007


Per Ben's recommendation, after last month's SLUG talk on OpenWRT, I
upgraded my Linksys box to White Russian 0.9.  I installed ez-ipupdate
and configured it with my DynDNS settings in webif^2 (the spiffy hot
rod web interface recommended by the same).

And... this morning, my DynDNS hosname expired. :(

The webif clearly shows an update interval of 2160000 seconds (25
days).  The DynDNS syslog is empty (meaning that the DynDNS client
hasn't done squat since last reboot). And there isn't any button
labeled "forced update".  What gives?

Interestingly, the box reports the current time as its "uptime":

# date; uptime
Mon May 14 09:18:51 EDT 2007
 09:18:51 up 21:16, load average: 0.00, 0.00, 0.00

The system's uptime and date (which is synchronized with an NTP
server) appear identical - to the second.  Could it be that this is
preventing the DynDNS daemon from updating at proper intervals?

OpenWRT was recommended as a way of getting around using Linksys's
broken DynDNS client.  But this system seems just as broken!


More information about the gnhlug-discuss mailing list