1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Any Fix for DYNDNS update

Discussion in 'HyperWRT Firmware' started by prowler1968, Aug 7, 2006.

  1. prowler1968

    prowler1968 Network Guru Member

    It has been a while since I have seen any further discussions about the WRT firmware not updating the DYNDNS accounts as it should on a regular schedule.

    Has anyone had any luck with a startup script that would perform the updates as necessary since the Linksys firmware and derivatives (such as Thibor's excellent build of Hyperwrt) are built off the stock CRAP dyndns update code?

    Too bad Dyndns requires these periodic updates. If I had a static IP, they would not require my account to periodically update (Which, according to THEIR theory, if people do not periodically update their DYNAMIC IP address, their database becomes stagnant.) However, if you register a Static address, and never update it or delete it if it becomes invalid, would also cause database stagnation.
     
  2. turbo53

    turbo53 Network Guru Member

    Well, I've spent a little time on this and am testing a startup script right now. It SEEMS to work using the DynDns test accounts. I'm currently testing using my real account, but won't know anything for sure until early September, since I need to wait for it to expire and see what happens.
     
  3. prowler1968

    prowler1968 Network Guru Member

    Thanks for the update - I have had to manually renew my dyndns account a couple of times now since the 28 day renew period is not functioniong as planned. My cable modem did lock up a few days ago, and when it received a new IP address and I rebooted the WRT, I did receive an automatic update to my dyndns account.

    Hopefully, we'll get a fix for this soon. Actually, I don't mind logging into my account every 28 days to manually update the IP address. Does the WRT function correctly if the IP address changes from the previous IP? If it will at least update a changed IP address, then I can live with the manual update. I just don't want a period of time where I cannot get access to my computer because the IP has changed and the update failed.
     
  4. turbo53

    turbo53 Network Guru Member

    Hard to tell, since my ISP almost never changes my IP. If you want to test (no guarantees on my part!) here is my startup script. You will have to change the "userid:password" to your userid and password and change the "hostname" to your DynDns hostname. Be sure to completely disable DynDns in the HyperWRT gui. If both HyperWRT and the script are trying to manage the dynamic IP, Gawd only knows what will happen.

    This startup script initiates the ez-ipupdate program as a daemon. It will check for an updated IP once an hour (the "period=3600" entry in the config file) and will force an update every 28 days (the "max-interval=2419200 entry) if one has not already happened.

    I run a cron job every 15 minutes to check if ez-ipupdate is running and start it if it is not. The reason that I don't run ez-ipupdate from the startup script is that I found it would force a DynDns update on each router reboot. Don't ask me why!!?? But by delaying the startup of the program via the cron job, I seem to have fixed that problem (I hope).

    I use different filenames than the router firmware does for the config and cache files in order to prevent any file naming conflicts.

    Good luck.

    =======================================================

    nvram get ddns_cache > /tmp/ez.cache

    cd /tmp
    echo "service-type=dyndns" > ez.conf
    echo "user=userid:password" >> ez.conf
    echo "host=hostname" >> ez.conf
    echo "backmx=NO" >> ez.conf
    echo "wildcard" >> ez.conf
    echo "daemon" >> ez.conf
    echo "execute=/sbin/ddns_success" >> ez.conf
    echo -n "interface=" >> ez.conf
    nvram get wan_ifname >> ez.conf
    echo "max-interval=2419200" >> ez.conf
    echo "period=3600" >> ez.conf
    echo "resolv-period=60" >> ez.conf

    echo "#!/bin/sh" > ez.bat
    echo "cd /tmp" >> ez.bat
    echo "if !(pidof ez-ipupdate > /dev/null)" >> ez.bat
    echo "then" >> ez.bat
    echo "/usr/sbin/ez-ipupdate -c /tmp/ez.conf -b /tmp/ez.cache" >> ez.bat
    echo "fi" >> ez.bat
    chmod +x ez.bat

    echo "*/15 * * * * root /tmp/ez.bat" > /tmp/cron.d/check_ezip
    touch /tmp/crontab
     
  5. prowler1968

    prowler1968 Network Guru Member

    Thanks Turbo - I'll try your script and see what happens. Keep us updated if you discover any problems with the script in the future and you don't get that 28 day renewal.
     
  6. mstombs

    mstombs Network Guru Member

    My startup script (not changed since I last posted it) has solved the problem for me, it tries to update once a day. There is a problem with startup though, the router does not use the cached ip/date on power up and always attempts an abusive update which means the dyndns and wrt54 can get out of sync. This script does sem to work if the power up update is sccessful though. The Tarifa project appears to have solved the problem, I guess it would not be too hard to integrate into Thibor's software but I don't yet have the ability!

    Code:
    echo "#!/bin/sh" > /tmp/my_dyndns
    echo "sleep 60" >> /tmp/my_dyndns
    echo "while true; do" >> /tmp/my_dyndns
    echo "ez-ipupdate -c /tmp/ddns.conf -b /tmp/ddns.cache" >> /tmp/my_dyndns
    echo 'fbuf=$(cat /tmp/ddns.cache)' >> /tmp/my_dyndns
    echo 'if [ "$(nvram get ddns_cache)" != "$fbuf" ]; then' >> /tmp/my_dyndns
    echo 'nvram set ddns_cache=$fbuf; nvram commit' >> /tmp/my_dyndns
    echo 'echo "nvram updated" >> /tmp/my_dyndns.log' >> /tmp/my_dyndns
    echo 'else' >> /tmp/my_dyndns
    echo 'echo "no update" >> /tmp/my_dyndns.log' >> /tmp/my_dyndns
    echo 'fi' >> /tmp/my_dyndns
    echo "sleep 86400" >> /tmp/my_dyndns
    echo "done" >> /tmp/my_dyndns
    chmod 700 /tmp/my_dyndns
    /tmp/my_dyndns &
     
  7. turbo53

    turbo53 Network Guru Member

    mstombs:

    Do you have a link to Tarifa? I'd be interested in taking a look. I tried Googling it but couldn't find it.

    Thanks.
     
  8. prowler1968

    prowler1968 Network Guru Member

    mstombs:

    Does your script actually update the dyndns record on a daily basis, or does it only check the ip address once a day and update if necessary?

    If this is a daily update, does this not qualify as an abusive update?
     
  9. marcelo_cr

    marcelo_cr Guest

    My solution for this problem was:
    1- configure dyndns through the web interface.
    2- add the folowing line at startup script
    echo "*/10 * * * * root /usr/sbin/ez-ipupdate -c /tmp/ddns.conf -b /tmp/ddns.cache" > /etc/cron.d/dyndns

    This will check every 10 minutes if the IP change then update dyndns.
     
  10. mstombs

    mstombs Network Guru Member

    The ez-ipupdate code keeps a cache copy of the IP address and update time and does not contact dyndns.com unnecessarily. The problem I have found is that the caches are not preserved across power cycles/ reboots and the stored time may not match that at dyndns.com (which may still allow your account to timeout).

    There's a hint from another post above. Maybe the update code runs too early on power up before the router has collected its IP via DHCP and then synchronized its clock.
     
  11. mstombs

    mstombs Network Guru Member

    Its not far away...

    http://www.linksysinfo.org/portal/forums/showthread.php?t=47353

    NB is now based on the same linksys codebase as Hyperwrt Thibor - so they experienced the same dyndns problems. When I last looked the final code was different in detail in too many places so I gave up. I haven't tried the Tarifa firmware so do not know what other features it has - it also seems to be primarily targetted for WRT54G not GS hardware.
     
  12. turbo53

    turbo53 Network Guru Member

    Ah...I see. Thought Tarifa was just a DDNS client, not an entire router firmware release. I may still take a look though, but since I'm about to go on vacation in a couple of days (finally!!) it's kinda low on my priority list. :)

    Thanks for the info.
     
  13. prowler1968

    prowler1968 Network Guru Member

    Thanks for the update - I think that the script is definitely worth a try if it has worked well for you.

    Regarding the "hint", do you have any modifications that should be made to the script to allow it to run later in the boot cycle and give more predictable results?
     
  14. digitalgeek

    digitalgeek Network Guru Member

    I am not sure what the problem is... I have configured my Dyndns via the web interface and everytime my IP by my ISP(DSL) it is updated with DynDNS and I am always able to access my network remotely.

    Is there another problem I am not aware of?
     
  15. prowler1968

    prowler1968 Network Guru Member

    The problem is the update mechanism does not work consistently. When I rebooted my router and modem a couple weeks ago, I received a new IP address for the first time in several months. The router updated the IP address correctly on this reboot.

    Dyndns requires the update to be performed even if the IP address does not change and will send you e-mail notification if the update is not done around day 30. By day 35, Dyndns will close your account.

    The problem comes when the IP address does not change. The router is not forcing an update of the IP address (even though it has not changed, Dyndns needs the update).

    This really is not a problem for me. If I receive the e-mail, I will update the IP manually. My concern is that I will have an IP change and the router will not update the IP at Dyndns, leaving me unable to access my computer remotely.
     
  16. Thibor

    Thibor Super Moderator Staff Member Member

    your concerns are unfounded, it has been shown that if the IP changes, ddns reacts to that change and updates the ddns record. the issue is that if the IP doesn't change, ddns does not perform an automated update within the 30 day period. if you update manually when you receive the mail from DynDNS, there is nothing to worry about.
     
  17. prowler1968

    prowler1968 Network Guru Member

    Thats what I wanted to hear!!

    I (mis)understood from previous posts on this topic that the update code was not running as a deamon and sometimes would not get re-started, causing a failure of the IP update when the IP changed.

    As long as the update daemon is active and can update when the IP address changes, I have no problem taking care of the periodic manual updates between IP changes.

    BTW Thibor - Great job on this firmware. The added features/stability are awesome compared to what Linksys gave us.
     
  18. mstombs

    mstombs Network Guru Member

    The ez-ipupdate code is not run in daemon mode - when the WAN IP updates the code is specifically run. You can start the ez-ipupdate task in daemon mode but the task gets killed and restarted (at least when dyndns is enabled). I don't know why the Linksys code is written like this, I can only guess that the ancient ez-ipupdate cannot detect all WAN IP changes itself - but it does seem to work with auto DHCP setups.

    The problem I (and others) have is that our ISP rarely changes the WAN IP, and if you don't pick up and act on th 30 day warning email your 'free' account gets deleted. The Linksys code just doesn't do the timed update after 28 days. In trying to fix this there is another problem at boot-up with the code not using the vram cached variables (old IP and update time), and always attempting to update dyndns (which is regarded as abusive). My script will only work if the IP was indeed updated at the cached time. I have yet to look at the two other alternatives offerred in this thread using cron jobs as a replacement or addition to the linksys code.
     
  19. digitalgeek

    digitalgeek Network Guru Member

    I still don't understand... my IP updates are made with out any problem... although I am using the rock solid Thibor 15c
     
  20. prowler1968

    prowler1968 Network Guru Member

    That's the topic I was referring to. I thought the ez-ipupdate was not running as a daemon. I, too, have the issue where my ISP rarely changes my IP address. It only recently changed after I locked up the router/modem by using the router disconnected from the modem. It was a couple of days before I realized that the modem was locked up and the power off/on cycle obtained a new IP address, which Thibor 15c correctly updated to Dyndns.

    I WISH that the 28 day update interval would correctly update the Dyndns record, but can definitely live with a monthly manual update if the router correctly updates the Dyndns account IF there is a change in the IP address.

    Then again, if your script is correctly allowing the same functionality PLUS updating correctly in the 28 day time frame, then maybe that deserves a try instead.
     
  21. mgnewman

    mgnewman LI Guru Member

    It doesn't work for me. I think I have ddns configured properly and I know I am using the correct host name, user name and password. When I go to my account page on dyndns.org it shows that my IP address has not been updated since August 17, 2006. I have had several dynamic IP addresses since then which have not been updated.

    The status line on the ddns page shows: unknown return code.

    The IP address shown is correct. However, dyndns simply does not get updated.

    What am I doing wrong?

    Firmware Version: v4.71.1, Hyperwrt 2.1b1 + Thibor15c

    WRT54G Version 2.0

    edit: I should add that I can manually update the address on the dyndns "modify" page.
     
  22. Thibor

    Thibor Super Moderator Staff Member Member

    you aren't doing anything wrong. the fact that you have a return code(even though it's unknown) means that it tried to update, but the update failed for whatever reason
     
  23. mgnewman

    mgnewman LI Guru Member

    So, what can I do about it?
     
  24. alphacom64

    alphacom64 Guest

    My Startup Script

    This is my Startup Script:

    STARTDDNS="/tmp/startddns.sh"
    CRONFILE="/etc/cron.d/dyndns"

    echo "#!/bin/sh" > $STARTDDNS

    echo "cat /tmp/ddns.conf /tmp/ddns-customopt.conf > /tmp/ddns_custom.conf" >> $STARTDDNS

    echo "/usr/sbin/ez-ipupdate -c /tmp/ddns_custom.conf -b /tmp/ddns.cache" >> $STARTDDNS

    chmod 700 $STARTDDNS

    echo "max-interval=2419200" >> /tmp/ddns-customopt.conf

    echo "*/10 * * * * root $STARTDDNS" > $CRONFILE
     
  25. mstombs

    mstombs Network Guru Member

    Try the Tarifa firmware? And if that works Merge Jchuit's Tarifa changes into Hyperwrt Thibor!

    I haven't managed to get around the issue with rebooting and cached IP/time with scripts alone.
     
  26. turbo53

    turbo53 Network Guru Member

    Well....It Worked.

    Earlier in this thread I posted a script to run ez-ipupdate as a deamon and set it to update DynDns once every 28 days. My DynDns account just updated after 28 days and 9 minutes. Since I configured ez-ipupdate to check for updates once an hour, the extra 9 minutes was probably due to that setting.

    Now, if only Cox only would change my IP so that I could check if that works properly :)

    Anyway, the startup script is posted earlier in this thread for anyone who wants to try it. Please note that this is just tested with DynDns and not any other dynamic DNS service.
     
  27. mstombs

    mstombs Network Guru Member

    I guess the router was on and not rebooted for all this time as well?
     
  28. turbo53

    turbo53 Network Guru Member

    Yes, that's right.

    This morning I manually rebooted the router in order to see if the reboot would force an unnecessary DynDns update. It didn't. The cached value for the DynDns update yesterday was preserved across the reboot, as it should be.
     
  29. mstombs

    mstombs Network Guru Member

    Now I am confused, the stock Linksys firmware doesn't save the IP and update time correctly across reboots, but I can't see in your script where you save the data to NVRAM then recover it on reboot (which would be straightforward to add). The cache file on /tmp will be be cleared on reboot. So if you don't save it perhaps the code does - I need to look again!
     
  30. turbo53

    turbo53 Network Guru Member

    My script (and HyperWrt as well) includes the following line in the ez-ipupdate configuration file: "execute=/sbin/ddns_success"

    Whenever DynDns is updated sucessfully, the "ddns_success" code is executed. This code saves the time and IP in the nvram variable "ddns_cache" which preserves it across reboots. I didn't need to do anything special for this - it is already there. What my script accomplishes is to fix 3 issues.

    1. It runs ez-ipupdate in daemon mode and has it check once an hour for updates to the IP. Obviously, you can shorten this time if you want. There is even an article on the DynDns web site talking about how Linksys didn't run the program in daemon mode. The article claims that this is now fixed, but it isn't. Here is a link to the article: http://www.dyndns.com/news/releases/archives/2003/11/288.html

    2. As you pointed out earlier in this thread, it seems that the firmware runs ez-ipupdate too early during the startup process, before the IP address is acquired and the clock synced. Here is what I suspect is happening. When ez-ipupdate is first run, it sees an IP address of 0.0.0.0 which it stores as the current IP. This wipes out the stored IP address in the cache. A few seconds later the router acquires its IP address, which is usually the same as the old one, but the old one has now been erased from the cache. As a result, the program sees this as a new IP and does an abusive update on each reboot. I fixed this by starting it via a cron job which runs every 15 minutes. The job checks to see if ez-ipupdate is already running, and starts it if it isn't. This gives the router time to finish its startup processing and acquire an IP address and set the proper time. 15 minutes is almost certainly longer than necessary, but it works.

    3. The cron job also fixes a third problem I discovered. If you run ez-ipupdate in daemon mode, and then make a router configuration change, ez-ipupdate is terminated (don't know why). The 15 minute check will restart the program if this happens.

    These changes seem to have fixed the problem for me, at least through one DynDns expiration period. Gotta wait 28 days for the next test: :)
     
  31. mstombs

    mstombs Network Guru Member

    OK, I am sold on turbo53's script. In experimentation I found that sometimes the nvram was cleared on reboot and not reset by ddns_success so I have added a check to correct this.

    The only other change I've made is to use the stored dyndns contents to use the variables set by the web interface - which remain even when the linksys code dyndns code is disabled.

    I'll now wait 28 days to check...

    Code:
    nvram get ddns_cache > /tmp/ez.cache
    
    cd /tmp
    cat > ez.conf <<-EOF1
    	service-type=dyndns
    	user=$(nvram get ddns_username):$(nvram get ddns_passwd)
    	host=$(nvram get ddns_hostname)
    	backmx=NO
    	wildcard
    	daemon
    	execute=/sbin/ddns_success
    	interface=$(nvram get wan_ifname)
    	max-interval=2419200
    	period=3600
    	resolv-period=60
    EOF1
    
    cat > ez.bat <<-EOF2
    #!/bin/sh
    cd /tmp
    if !(pidof ez-ipupdate > /dev/null) 
    then
    	/usr/sbin/ez-ipupdate -c /tmp/ez.conf -b /tmp/ez.cache
    fi
    fbuf=\$(cat /tmp/ez.cache)
    if [ "\$(nvram get ddns_cache)" != "\$fbuf" ]; then
    	nvram set ddns_cache=\$fbuf; nvram commit
    fi
    EOF2
    
    chmod +x ez.bat
    
    echo "*/15 * * * * root /tmp/ez.bat" > /tmp/cron.d/check_ezip
    touch /tmp/crontab
     
  32. turbo53

    turbo53 Network Guru Member

    mstombs:

    Thanks for the update and I'm glad this has been of help.

    There is one additional issue that this script doesn't address. ez-ipupdate is configured to wake up once an hour to check if it needs to do anything. So if your ISP changes your IP address, there could be up to an hour's delay before DynDns is updated. You can always reduce this to a smaller number (e.g. 5 minutes) but that increases the load on the router and is usually not necessary.

    My ISP rarely changes my IP (I think it has changed once in 4 or 5 years), but if other ISPs change them more frequently, and if you cannot tolerate a delay in updating DynDns, then this could be a problem.

    I think I have a fix for this, but I have no way of testing it since I can't force an IP change. If anyone can test this, I'd be glad to post the additional script.
     
  33. mstombs

    mstombs Network Guru Member

    My cable IP rarely changes and if it does it is at 3am after some local network reconfiguration, I can force a change by cloning/uncloning my MAC address but this is not a good test as you need to save the WRT54GS config then reboot the cable modem.

    I can't help but think there are some connection protocols that don't work with ez-ipupdate daemon mode. You can see in the linksys code this option is commented out - also the ez-ipupdate code is 'killed' when a WAN change occurs (as far as I can tell).

    I would expect ez-ipupdate takes lower resources running in daemon mode and checking evry hour than re-running it from scratch?
     
  34. turbo53

    turbo53 Network Guru Member

    It wouldn't require running ez-ipupdate from scratch.

    If you send the TERM signal to ez-ipupdate it will wake up and see if there is anything to do. What I have done is write a script that is called from UDHCPC whenever the IP is renewed. (The firmware already uses this feature, I just chain to the existing one). So whenever the IP is renewed, I send a TERM to ez-ipupdate. Pretty simple actually.

    But if ez-ipupdate is terminated on an IP change, then you're right, it is a moot point since the cron job will just restart it and it should notice the change.
     
  35. prowler1968

    prowler1968 Network Guru Member

    @mstombs -

    Is this code meant to be run stand-alone or with the dyndns enabled in the web interface?
     
  36. turbo53

    turbo53 Network Guru Member

    DynDns should be DISABLED on the web interface.

    As MSTOMBS points out, the nvram variables are remembered even after you disable dynamic dns in the GUI. In order to use this script, be sure that the following nvram variables have the correct values, just to be on the safe side:

    "ddns_username" should be your dyndns user id
    "ddns_passwd" should be your dyndns password
    "ddns_hostname" should be your dyndns host name
     
  37. rljo

    rljo Network Guru Member

    So, guys,

    Did it work after the 28 days elapsed?

    thanks,
    Bob
     
  38. mstombs

    mstombs Network Guru Member

    Well, I didn't get a 'hostname about to expire' email so I have just checked dyndns.com - my IP address hasn't changed and

    which is about 28 days since I last changed the script (could be 5 or 6 hours off due to reporting timezones). If local time could well be ISP related.

    Not a 100% test though as my router has been power cycled (accidentally) at some point and restarted after new wireless client and static dhcp configured and tested (worked fine when MAC filter in router and WPA in client configured correctly!).
     
  39. mstombs

    mstombs Network Guru Member

    Router has not been booted for

    Code:
    Firmware Version :   	v4.71.1, Hyperwrt 2.1b1 + Thibor15c [May 12 2006]
    Uptime :   	29 days, 07:36:10
    changes to access restrictions/ wireless clients etc have been made

    dyndns successfully update at

    Code:
    Thu Nov 2 09:00:04 2006
    - found how to set local timezone on dyndns.com this changed previous update to

    Code:
    Thu Oct 5 08:30:03 2006
    so 28 day update works for me now
     
  40. prowler1968

    prowler1968 Network Guru Member

    @mstombs:

    Thanks for your effort (as well as others) for refining the dyndns update script to the level that you have and updates appear to be working as expected.

    I am now ready to try the script but would like a little direction:

    This script can but cut and pasted into the startup script window in Hyperwrt, correct?

    If I find that the script is causing a problem (which I don't expect at this point), how do you go about clearing the script?

    My thoughts are to save my configuration. Apply the script. If necessary, clear the NVRAM and restore the settings should I have an issue. Any other advice on working with scripts?
     
  41. mstombs

    mstombs Network Guru Member

    Here is the complete content of my startup script. The first line allows me to access my cable modem, nothing to do with dyndns:-

    Code:
    ifconfig vlan1:0 192.168.100.2 netmask 255.255.255.0
    nvram get ddns_cache > /tmp/ez.cache
    
    cd /tmp
    cat > ez.conf <<-EOF1
    	service-type=dyndns
    	user=$(nvram get ddns_username):$(nvram get ddns_passwd)
    	host=$(nvram get ddns_hostname)
    	backmx=NO
    	wildcard
    	daemon
    	execute=/sbin/ddns_success
    	interface=$(nvram get wan_ifname)
    	max-interval=2419200
    	period=3600
    	resolv-period=60
    EOF1
    
    cat > ez.bat <<-EOF2
    #!/bin/sh
    cd /tmp
    if !(pidof ez-ipupdate > /dev/null) 
    then
    	/usr/sbin/ez-ipupdate -c /tmp/ez.conf -b /tmp/ez.cache
    fi
    fbuf=\$(cat /tmp/ez.cache)
    if [ "\$(nvram get ddns_cache)" != "\$fbuf" ]; then
    	nvram set ddns_cache=\$fbuf; nvram commit
    fi
    EOF2
    
    chmod +x ez.bat
    
    echo "*/15 * * * * root /tmp/ez.bat" > /tmp/cron.d/check_ezip
    touch /tmp/crontab
    This script assumes the following variables have been saved through the standard ddns setup page

    "ddns_username" should be your dyndns user id
    "ddns_passwd" should be your dyndns password
    "ddns_hostname" should be your dyndns host name

    The standard ddns service should then be disabled and this setting 'saved'.

    The router should be rebooted (for example by power cycle).

    To startup script is stored in nvram, so clearing the nvram also clears the script (as well as all you other settings). It should also be sufficient to clear the startup contents in the web interface, saving then rebooting to clear the service from your router.

    To check that things are working use the Adminstration - Run command to give the command

    ps

    which should result in a screen containing a line with similar contents to:-
    Code:
      PID  Uid     VmSize Stat Command
    
    29264 0           364 S   /usr/sbin/ez-ipupdate -c /tmp/ez.conf -b /tmp/ez.cach
    (The code at start will be different)

    Hope this summary is of use
     
  42. turbo53

    turbo53 Network Guru Member

    I'm glad to see this seems to be working.

    Maybe Thibor can incorporate something similar into the next HyperWRT upgrade.
     
  43. Thibor

    Thibor Super Moderator Staff Member Member

    would the caching issue be solved by moving the ddns startup further back in the boot process, say after the wan and ntp sections?
     
  44. turbo53

    turbo53 Network Guru Member

    Probably. I think we need to make sure that an IP address is acquired and the time synced before starting ez-ipupdate.

    The other issue is to start ez-ipupdate as a daemon, as the DynDns web site recommends. Unfortunately, I haven't tested this fix with the other dynamic IP services so I don't know how it would work for them.
     
  45. mstombs

    mstombs Network Guru Member

    Wouldn't that be a good idea! jchuit has apparently solved the ddns issues in the Tarifa firmware based on the same Linksys source, the published code looks similar - but different in detail.

    The Linksys author obviously considered it as the switch and interface definition are just commented out in the code. My guess it didn't work for an option other than dhcp WAN and dyndns, which is why they opted to only run ez-ipuddate 'on demand' which lost the 28 day update mode.
     

Share This Page