ddclient 0.3 - Automatic updater for Dynamic DNS

[chameleon_skin]

Update #2: Ok, I figured out the issue. Apparently the internet interfaces are not being brought up on the WD TV until after the ddclient load script runs. I would have thought that it would simply catch it on the next run, but apparently ddclient fails on subsequent runs if it can't find the ip address provider on the first run.

I have made some modifications to do exactly what you suggested, i.e. delay the start of ddclient for about three minutes to make sure that the internet interface is brought up before ddclient starts running. I tested this on my box, and now the ddclient.cache file (i.e. the one that contains the info about your current ip address) is being correctly created and populated.

I have also changed the provider of the ip address, since as mentioned in my last message the checkip.dyndns.org is really flaky (specifically, there are really three servers around the world that answer to that dns entry, depending on where you are located - one of them works great, the others fail frequently).

I'll try to upload a new app.bin with the changes tonight - when I do, please try it out and let me know if it works for you.

[b-rad.cc]

if a binary requires net connection you can always loop until online.delayer returns 0, then start.

[chameleon_skin]

Ah, I didn't know about the delayer. Looking at the code for it, it looks like it exits with status 1 if it is explicitly turned off in the config. I'll just look for that case and if it happens, wait a while before executing just in case.

[chameleon_skin]

boudcallens & bloodflower:

I posted a new version 0.2 with a few critical bugfixes in the original thread post - please grab it and let me know if it works for you now.

[PaulF]

This is so cool. An Apache web server at home. The mind boggles. How about a USB cam or ssh tunneling to my PCs? The Ruby on Rails is making more sense now, too. Thanks.

[boudcallens]

Hi chameleon_skin,

Works perfectly now. Thanks for the quick update.

BoBo

[bolts4brekfast]

using ddclient 0.2 ...

I set everything up correctly... LOCALLY.. i can put in my dyndns name and get the webend screen for my live+ box...
if i put in my dyndns name outside the network... it wont connect..
ftp and ssh connect just fine outside of the network... but why not webend (using port 80) ???
using a Linksys E3000 router. i have checked firewall settings in router.. and port forwarding..

help please.

[chameleon_skin]

Please run this command from the command line of your WDTV and post the output here:

ddclient -daemon=0 -debug -verbose -noquiet

[bolts4brekfast]

figured out the problem... my ISP is Cox Cable. I am located in (GEORGIA, USA) ... With a Cox Cable residential account.. they block port 80 any way around this?

[chameleon_skin]

Great to know - I've never heard of an ISP blocking port 80. That's evil.

You would need to change web frontend to run on a different port, but it doesn't look like there is an option for that in S00-custom-options and you can't directly modify the apache config file.

I'm thinking that you could probably set up another vhost file for apache that runs on a different port but still uses the same web frontend code. I'll look into it this week, unless b-rad sees this and beats me to it.