ddclient-forum Mailing List for ddclient (Page 10)
Brought to you by:
supersandro2000,
wimpunk
Menu
▾
▴
ddclient-forum — Forums posts on ddclient
This list is closed, nobody may subscribe to it.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(25) |
Sep
(27) |
Oct
(37) |
Nov
(35) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(36) |
Mar
(14) |
Apr
(13) |
May
(23) |
Jun
(23) |
Jul
(10) |
Aug
|
Sep
(12) |
Oct
(7) |
Nov
(35) |
Dec
(23) |
| 2009 |
Jan
(19) |
Feb
(16) |
Mar
(15) |
Apr
(18) |
May
(8) |
Jun
(11) |
Jul
(5) |
Aug
(22) |
Sep
(4) |
Oct
(11) |
Nov
(4) |
Dec
(1) |
| 2010 |
Jan
(1) |
Feb
(2) |
Mar
(1) |
Apr
(1) |
May
(7) |
Jun
(12) |
Jul
(9) |
Aug
(2) |
Sep
(7) |
Oct
(5) |
Nov
|
Dec
(2) |
| 2011 |
Jan
|
Feb
(8) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
| 2012 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2008-12-20 16:54:24
|
Bugs item #2451365, was opened at 2008-12-19 15:14 Message generated for change (Comment added) made by ziesemer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2451365&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: service configuration Group: current version Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Mark Ziesemer (ziesemer) Assigned to: wimpunk (wimpunk) Summary: Suspect min-interval for DynDNS Initial Comment: Partially related to feature request # 2451138. Looking at line 357 in rev. 78 of ddclient, the "min-interval" variable is defaulted to 30 seconds. The configuration for DynDNS doesn't appear to reset this. Also, as far as I can tell, DynDNS doesn't require or at least doesn't specify this value. Some quick testing shows that DynDNS accepts almost immediate, successive updates, as long as it results in an IP change. As far as I can tell, this option is not user-configurable from the config file nor the command line. One point still not fully considered is that, at least for free users, DynDNS only offers TTLs of 60 seconds or 4 hours. It could be assumed that min-interval should also then be 60 seconds. However, in a worst-case scenario, DynDNS could require waiting 60 seconds to update, plus another 60 seconds could be required for the TTL to expire, resulting in a maximum of 2 minutes necessary for the change to be reflected. Allowing a min-interval of 0 for DynDNS would lower this time to the TTL value. It would also resolve the situation detailed in feature request # 2451138, without requiring additional complexities, as long as DynDNS does truly not have a stated or enforced minimum update interval. ---------------------------------------------------------------------- >Comment By: Mark Ziesemer (ziesemer) Date: 2008-12-20 10:54 Message: I'm not disputing that ddclient doesn't meet the DynDNS requirements. I believe it not only does, but is doing more than needed, as I tried to describe. I will review the latest SVN version and will follow-up to the forum as requested if needed. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-12-20 07:09 Message: Please first discuss issues on the forum and use the latest svn version to verify your theory (currently r106). Read the developper API and put links to the correct paragraphs. Ddclient has been verified and modified for and by dyndns to fit their requierements. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2451365&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-12-20 13:12:52
|
Feature Requests item #2451138, was opened at 2008-12-19 20:34 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2451138&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Priority: 5 Private: No Submitted By: Mark Ziesemer (ziesemer) Assigned to: Nobody/Anonymous (nobody) Summary: Better support / timing for on-demand updates Initial Comment: I am unfortunately stuck with wireless, cellular Internet access over PPP. It is not very reliable, and it reconnects frequently, each time receiving a new IP address. I already have my system configured to call ddclient from my /etc/ppp/ip-up.d/ . DynDNS and other providers require that updates be at least 5 minutes apart. Consider the situation where I just got reconnected, and a successful update was performed. Between 0-5 minutes later, I'm reconnected again. ddclient is unable to update the IP with DynDns, either because it properly refrains from updating more than once within the 5 minute period, or because it receives a similar error back from DynDns - I've not yet looked into which is happening. Regardless, my IP is then not updated until the next time ddclient is called, probably due to the next reconnection event, which could leave me guessing at my next IP for the next several minutes, hours, or more. The alternative is to just use the daemon mode. However, I'd much rather prefer the event-based approach, which requires one less process to remain running at all times. Additionally, running daemon mode can be considered slower than the interface hooks. If my previous update was several hours ago, and a reconnection happens just seconds into a 5-minute daemon period, it could be 4+ minutes until the IP is updated, even though an immediate update would be valid. What I'd recommend is a "follow-up" option to the non-daemon mode. This would allow for ddclient to only run when necessary. If an update is requested before the minimum required time has elapsed, it could then spawn a new process that would sleep and update as soon as allowed - taking care to have this process canceled if there is yet another reconnection event during that time. ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2008-12-20 13:12 Message: Please use the help forum to discuss such situations. You can start ddclient in deamon mode and send a HUP signal to force a renew. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2451138&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-12-20 13:09:33
|
Bugs item #2451365, was opened at 2008-12-19 21:14 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2451365&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: service configuration Group: current version >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Mark Ziesemer (ziesemer) Assigned to: wimpunk (wimpunk) Summary: Suspect min-interval for DynDNS Initial Comment: Partially related to feature request # 2451138. Looking at line 357 in rev. 78 of ddclient, the "min-interval" variable is defaulted to 30 seconds. The configuration for DynDNS doesn't appear to reset this. Also, as far as I can tell, DynDNS doesn't require or at least doesn't specify this value. Some quick testing shows that DynDNS accepts almost immediate, successive updates, as long as it results in an IP change. As far as I can tell, this option is not user-configurable from the config file nor the command line. One point still not fully considered is that, at least for free users, DynDNS only offers TTLs of 60 seconds or 4 hours. It could be assumed that min-interval should also then be 60 seconds. However, in a worst-case scenario, DynDNS could require waiting 60 seconds to update, plus another 60 seconds could be required for the TTL to expire, resulting in a maximum of 2 minutes necessary for the change to be reflected. Allowing a min-interval of 0 for DynDNS would lower this time to the TTL value. It would also resolve the situation detailed in feature request # 2451138, without requiring additional complexities, as long as DynDNS does truly not have a stated or enforced minimum update interval. ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2008-12-20 13:09 Message: Please first discuss issues on the forum and use the latest svn version to verify your theory (currently r106). Read the developper API and put links to the correct paragraphs. Ddclient has been verified and modified for and by dyndns to fit their requierements. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2451365&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-12-19 21:14:11
|
Bugs item #2451365, was opened at 2008-12-19 15:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2451365&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: service configuration Group: current version Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark Ziesemer (ziesemer) Assigned to: wimpunk (wimpunk) Summary: Suspect min-interval for DynDNS Initial Comment: Partially related to feature request # 2451138. Looking at line 357 in rev. 78 of ddclient, the "min-interval" variable is defaulted to 30 seconds. The configuration for DynDNS doesn't appear to reset this. Also, as far as I can tell, DynDNS doesn't require or at least doesn't specify this value. Some quick testing shows that DynDNS accepts almost immediate, successive updates, as long as it results in an IP change. As far as I can tell, this option is not user-configurable from the config file nor the command line. One point still not fully considered is that, at least for free users, DynDNS only offers TTLs of 60 seconds or 4 hours. It could be assumed that min-interval should also then be 60 seconds. However, in a worst-case scenario, DynDNS could require waiting 60 seconds to update, plus another 60 seconds could be required for the TTL to expire, resulting in a maximum of 2 minutes necessary for the change to be reflected. Allowing a min-interval of 0 for DynDNS would lower this time to the TTL value. It would also resolve the situation detailed in feature request # 2451138, without requiring additional complexities, as long as DynDNS does truly not have a stated or enforced minimum update interval. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2451365&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-12-19 20:34:43
|
Feature Requests item #2451138, was opened at 2008-12-19 14:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2451138&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Mark Ziesemer (ziesemer) Assigned to: Nobody/Anonymous (nobody) Summary: Better support / timing for on-demand updates Initial Comment: I am unfortunately stuck with wireless, cellular Internet access over PPP. It is not very reliable, and it reconnects frequently, each time receiving a new IP address. I already have my system configured to call ddclient from my /etc/ppp/ip-up.d/ . DynDNS and other providers require that updates be at least 5 minutes apart. Consider the situation where I just got reconnected, and a successful update was performed. Between 0-5 minutes later, I'm reconnected again. ddclient is unable to update the IP with DynDns, either because it properly refrains from updating more than once within the 5 minute period, or because it receives a similar error back from DynDns - I've not yet looked into which is happening. Regardless, my IP is then not updated until the next time ddclient is called, probably due to the next reconnection event, which could leave me guessing at my next IP for the next several minutes, hours, or more. The alternative is to just use the daemon mode. However, I'd much rather prefer the event-based approach, which requires one less process to remain running at all times. Additionally, running daemon mode can be considered slower than the interface hooks. If my previous update was several hours ago, and a reconnection happens just seconds into a 5-minute daemon period, it could be 4+ minutes until the IP is updated, even though an immediate update would be valid. What I'd recommend is a "follow-up" option to the non-daemon mode. This would allow for ddclient to only run when necessary. If an update is requested before the minimum required time has elapsed, it could then spawn a new process that would sleep and update as soon as allowed - taking care to have this process canceled if there is yet another reconnection event during that time. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2451138&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-12-14 19:52:49
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5813589 By: feng0002 Hi, Does ddclient currently support changeIP.com? If so, which protocol should be used? Thanks in advance!! ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
|
From: SourceForge.net <no...@so...> - 2008-12-14 19:15:20
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5813463 By: wimpunk You could better post your patch to the patches section and leave link about it to the forum. From my experiences people mostly search the forum but they doesn't try harder to find some help. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399427 |
|
From: SourceForge.net <no...@so...> - 2008-12-13 01:14:31
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5805781 By: calin_fastfire Ack, forgot to change the 'written by' line. Clearly I started by copying the sitelutions code : ) ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399427 |
|
From: SourceForge.net <no...@so...> - 2008-12-13 01:12:45
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5805778 By: calin_fastfire Hi guys. I've written this patch to add in freedns support to ddclient 3.7.3 .conf file example is: protocol=freedns, \ login=my-freedns.afraid.org-login, \ password=my-freedns.afraid.org-password \ myhost.afraid.com The patch: *** ddclient Fri Dec 12 15:41:43 2008 --- ddclient Fri Dec 12 17:06:23 2008 *************** my %services = ( *** 479,484 **** --- 479,494 ---- $variables{'service-common-defaults'}, ), }, + 'freedns' => { + 'updateable' => undef, + 'update' => \&nic_freedns_update, + 'examples' => \&nic_freedns_examples, + 'variables' => merge( + { 'server' => setv(T_FQDNP, 1, 0, 1, 'freedns.afraid.org', undef) }, + { 'min-interval' => setv(T_DELAY, 0, 0, 1, 0, interval('5m')),}, + $variables{'service-common-defaults'}, + ), + }, ); $variables{'merged'} = merge($variables{'global-defaults'}, $variables{'service-common-defaults'}, *************** sub nic_sitelutions_update { *** 3159,3164 **** --- 3169,3264 ---- } } } + ###################################################################### + + ###################################################################### + ## nic_freedns_examples + ###################################################################### + sub nic_freedns_examples { + return <<EoEXAMPLE; + + o 'freedns' + + The 'freedns' protocol is used by DNS services offered by freedns.afraid.org. + + Configuration variables applicable to the 'freedns' protocol are: + protocol=freedns ## + server=fqdn.of.service ## defaults to freedns.agraid.org + login=service-login ## login name and password registered with the service + password=service-password ## + fully.qualified.host ## the host registered with the service. + + Example ${program}.conf file entries: + ## single host update + protocol=freedns, \\ + login=my-freedns.afraid.org-login, \\ + password=my-freedns.afraid.org-password \\ + myhost.afraid.com + + EoEXAMPLE + } + ###################################################################### + ## nic_freedns_update + ## + ## written by Mike W. Smith + ## + ## based on http://freedns.afraid.org/api/ + ## needs this url to update: + ## http://freedns.afraid.org/api/?action=getdyndns&sha=<sha1sum of login|password> + ## This returns a list of host|currentIP|updateURL lines. + ## Pick the line that matches myhost, and fetch the URL. + ## word 'Updated' for success, 'fail' for failure. + ## + ###################################################################### + use Digest::SHA1 qw/sha1_hex/; #Not the best place for this, but it goes with the freedns update, so whatever + sub nic_freedns_update { + + + debug("\nnic_freedns_update -------------------"); + + ## First get the list of updatable hosts + my $url; + $url = "http://$config{$_[0]}{'server'}/api/?action=getdyndns&sha=".&sha1 _hex("$config{$_[0]}{'login'}|$config{$_[0]}{'password'}"); + my $reply = geturl(opt('proxy'), $url); + if (!defined($reply) || !$reply || !header_ok($_[0], $reply)) + { + failed("updating %s: Could not connect to %s for site list.", $_[0], $url); + return; + } + my @lines = split("\n", $reply); + my %freedns_hosts; + grep + { + my @rec = split(/\|/, $_); + $freedns_hosts{$rec[0]} = \@rec; + } @lines; + ## update each configured host + foreach my $h (@_) { + if(!$h){ next }; + info("setting IP address to %s for %s", $ip, $h); + verbose("UPDATE: updating %s", $h); + + if($ip ne $freedns_hosts{$h}->[1]) + { + my $reply = geturl(opt('proxy'), $freedns_hosts{$h}->[2]); + if (!defined($reply) || !$reply) { + failed("updating %s: Could not connect to %s.", $h, $freedns_hosts{$h}->[2]); + last; + } + last if !header_ok($h, $reply); + + if($reply =~ /Updated.*host/) + { + success("updating %s: good: IP address set to %s", $h, $ip); + } else { + $config{$h}{'status'} = 'failed'; + warning("SENT: %s", $freedns_hosts{$h}->[2]) unless opt('verbose'); + warning("REPLIED: %s", $reply); + failed("updating %s: Invalid reply.", $h); + } + } + } + } ###################################################################### # vim: ai ts=4 sw=4 tw=78 : ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399427 |
|
From: SourceForge.net <no...@so...> - 2008-12-10 18:40:26
|
Patches item #2407927, was opened at 2008-12-08 23:47 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2407927&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: None Priority: 5 Private: No Submitted By: mike_nelson (miken700) Assigned to: wimpunk (wimpunk) Summary: Router (wireless) Linksys WRT610N Initial Comment: Access to router Linksys WRT610N. I don't need this as the below works but in case you want to put it in or need it for support. This works, use=fw, fw=http://10.0.0.1/Status_Router.asp, fw-skip='Internet IP Address' # ddclient -geturl 10.0.0.1/Status_Router.asp > ~/temp.txt temp.txt attached (my url was changed in the output to xxx.xxx.23.27) ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-12-10 18:40 Message: I moved your bugreport to the patches section and added a link to it in the wiki. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2407927&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-12-10 18:39:44
|
Patches item #2407927, was opened at 2008-12-08 23:47 Message generated for change (Settings changed) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2407927&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: mike_nelson (miken700) Assigned to: wimpunk (wimpunk) Summary: Router (wireless) Linksys WRT610N Initial Comment: Access to router Linksys WRT610N. I don't need this as the below works but in case you want to put it in or need it for support. This works, use=fw, fw=http://10.0.0.1/Status_Router.asp, fw-skip='Internet IP Address' # ddclient -geturl 10.0.0.1/Status_Router.asp > ~/temp.txt temp.txt attached (my url was changed in the output to xxx.xxx.23.27) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2407927&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-12-08 23:47:24
|
Bugs item #2407927, was opened at 2008-12-08 15:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2407927&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: router configuration Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: mike_nelson (miken700) Assigned to: wimpunk (wimpunk) Summary: Router (wireless) Linksys WRT610N Initial Comment: Access to router Linksys WRT610N. I don't need this as the below works but in case you want to put it in or need it for support. This works, use=fw, fw=http://10.0.0.1/Status_Router.asp, fw-skip='Internet IP Address' # ddclient -geturl 10.0.0.1/Status_Router.asp > ~/temp.txt temp.txt attached (my url was changed in the output to xxx.xxx.23.27) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2407927&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-12-05 19:28:22
|
Patches item #2393339, was opened at 2008-12-05 11:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2393339&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Steve Fink (sphink) Assigned to: Nobody/Anonymous (nobody) Summary: Implement redirects Initial Comment: I've been affected by the www.zoneedit.com -> dynamic.zoneedit.com redirect for a while now, and I finally got around to diagnosing what was going on. I have updated my .conf file now, but I suggest this patch to implement redirects (at least 301, 302, and 307 redirects) to fix it without needing to update the .conf files. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2393339&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-11-26 22:21:57
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5721003 By: wimpunk You can try to fetch your IP from your router. It probably has a status page which can be used by ddclient to fetch your ip. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
|
From: SourceForge.net <no...@so...> - 2008-11-26 20:27:06
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5720439 By: rloc Two days after I sent the above message the system came up of its own accord without any intervention on my part. I then experienced a power failure earlier today and the server is once again unavailable through it's URL but available via its IP address. Here is a post from the Dyndns community forum which I don't fully understand but which may point to the root of the problem: "If it's any help, I can confirm that Telkom ZA do use transparent proxies and it's always the proxy IP that's reported to the webserver, not the customer's. (Though that may be buried in an "X-Forwarded-For' or somesuch header, I've never looked). What's more, viewing my Apache server logs when a Telkom customer visits I see pretty well every single (sub-) request coming from a different 'client' IP. Ie., requests get routed through the various proxies at random. First time I saw that behaviour I thought it was a sophisticated DOS attack or somesuch! So the default IP displayed by the DynDNS config page will always be wrong (unless it does something clever with the request headers). Can't help with a workaround I'm afraid, the only router I know is Smoothwall, which has DynDNS updating built-in. Other than suggest you get a router with that capability." Being a Telkom ZA user, this applies to me. I do not understand what a transparent proxy is and does this prevent Dyndns and / or ddclient ever working reliably? Thanks again... ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
|
From: SourceForge.net <no...@so...> - 2008-11-24 07:28:28
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5704711 By: wimpunk I'm sorry to tell you so but it is a configuration issue. Please post the configuration you think ddclient uses on http://ddclient.pastebin.ca/ or another pastebin and put a link here. Since you told me you had a use=if, if=eth0 and since there's nothing about it in your logging, I really think ddclient isn't using the configuration file you think he uses. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399427 |
|
From: SourceForge.net <no...@so...> - 2008-11-24 02:18:19
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5703552 By: stevenorr No. I don't seem to have a problem with ddclient finding the config file. ddclient --help says -file path : load configuration information from 'path' (default: /etc/ddclient.conf). -cache path : record address used in 'path' (default: /var/cache/ddclient/ddclient.cache). The problem is that it's not actually connecting to zonedit.com to do the update. I put a copy of the debug output up if that helps: http://steveo.syslang.net/ddclient-debug.txt I changed the username and passwd to protect the guilty. Does anyone see anything wrong here? ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399427 |
|
From: SourceForge.net <no...@so...> - 2008-11-23 20:48:58
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5702072 By: wimpunk By default ddclient uses /etc/ddclient/ddclient.conf as configuration and /var/cache/ddclient/ddclient.cache as cache file. some distributions changes this location to the old one (as far as I know, ubuntu does, I don't know if fedora does) Since your ddclient doesn't work like it should, I would suggest to specify the configuration file by using the --file option. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399427 |
|
From: SourceForge.net <no...@so...> - 2008-11-23 20:12:39
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5701905 By: stevenorr I just loaded Fedora 9 and it looks like the conf file is /etc/ddclient.conf and the cache file is supposed to be in /var/run/ddclient but it's an empty directory despite that the docs say that there should be a /etc/ddclient/ddclient.conf. If I run ddclient --help is says -cache path : record address used in 'path' (default: /var/cache/ddclient/ddclient.cache). If I run ddclient -daemon=0 -debug -verbose -noquiet, at the end it says DEBUG: get_ip: using ip, ip reports <undefined> WARNING: unable to determine IP address but in my conf file it says use=if, if=eth0 Also, in my .conf file I say: login=me # default login password=somethinggoog # default password mx=syslang.net # default MX #backupmx=yes|no # host is primary MX? wildcard=yes # add wildcard CNAME? server=dynamic.zoneedit.com, \ protocol=zoneedit1 \ www.syslang.net I've been using ddclient for a long time and I upgraded to 3.7.3 when I upgraded to Fedora 9. Can someone please help me? Is there more info I can provide? Thanks st...@sy... ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399427 |
|
From: SourceForge.net <no...@so...> - 2008-11-21 05:35:11
|
Feature Requests item #2302860, was opened at 2008-11-16 17:37 Message generated for change (Settings changed) made by vask3 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2302860&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Access to other dyndns service providers Group: None >Status: Open Priority: 5 Private: No Submitted By: John Vasko (vask3) Assigned to: wimpunk (wimpunk) Summary: Support for multiple accounts Initial Comment: Issue: Add the ability to update DNS hosts under 2 separate accounts under the same Dynamic DNS provider or under different Dynamic DNS providers with 1 instance of ddclient. In other words have 2 separate logins and 1 ddclient... Currently I am looking at running 2 clients simultaneously on the same server from the following websites: no-ip.com dyndns.com I know ideally I would have all hosts under the same account... but keeping accounts separate helps maintain account nuetrality, and transfering DNS names from one account to another is no longer an issue. -John ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2302860&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2008-11-19 22:22:01
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5678111 By: rloc Everything has been fine until I did a complete system restart as per a power failure. That means that server, router & client PC went down Now I have the same problem that I cannot use the URL to access the website. I can use the IP address though. The router and ddclient both report the same IP but I get a 'Network Timeout' when I try to access the URL. ddclient reports the same external IP that the router does. Really out of ideas now... ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
|
From: SourceForge.net <no...@so...> - 2008-11-19 20:47:53
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5677721 By: rloc Okay, I'm happy ddclient is working correctly. :-) ***Yes, so am I!! I'm wondering how you try to test your http-server. Some routers have problems if you try to access an internal server using the WAN-IP. I hope this is not causing your problems. ***Not sure what you mean here. I have been testing the server from a pc connected to the same switch as the server AND from a remote pc and the results have been consistent. By this I mean that both pc's behaved the same; I could access the site either from both of them or neither of them. ***OK here is the strange part...During the course of today, I could suddenly access my website using the URL. Nothing in the configuration has changed since my last communication with you but it now works! This is similar to what has been happening before; the site is accessible and then suddenly is not. I will wait and keep you informed without modifying ANYTHING at all on the server. If you can access your site using the IP and if your site isn't accessible using the hostname there must be a problem with the configuration of your webserver, unless your own dns isn't working correctly. ***I completely accept this possibility but I don't see how Apache setup could cause this problem. I am really a beginner with this stuff so please understand that some of my questions may be frustratingly simple but I have to ask...Can you point me to what kind of configuration problem within Apache could cause this problem? I have been asking for assistance from various Apache help resources but they have not been of much use except to say that the problem is not my Apache configuration. If you're running linux, you could try something like `host georgievilla.dynalias.net` to verify if your local dns got the update. ***The result of that command is: georgievilla.dynalias.net has address of 41.245.110.221 At last, you could verify if there isn't any proxy or firewall rule blocking your request. ***There is no firewall at all on the webserver yet. Once I have the site completely stable I will ***probably install pfSense and / or Snort for this purpose. ***Maybe off the subject but please explain: ***I mentioned before that I am running Firefox with an extension called 'External IP' The home page ***for this application is www.ermodev.se ***This program periodically pops up a window in Firefox with a 'new external IP address'. This ***address sometimes BUT NOT ALWAYS corresponds with the IP address detected by ddclient. I have ***also found that the IP address returned by my router ALWAYS corresponds with that returned by ***ddclient. ***Another possibly off the subject question: ***I mentioned in a previous post that my Linksys WAG200g router has a setup option to enable DDNS. ***This setting currently disabled in my router. ***If I choose to enable it, it provides me with a drop down menu which includes 'dyndns.org' ***If I select that option, I am presented with fields to fill in for: ***username ***password ***hostname ***Below those fields is a <Connect> pushbutton ***Below that is the 'Internet IP address' which is 41.245.110.221 ***Should I enable this function within the router or leave it disabled as it is now? I hope it helps, ***Well it works as I type this...Thanks for your assistance, very much appreciated. Robert wimpunk. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
|
From: SourceForge.net <no...@so...> - 2008-11-19 19:54:35
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5677475 By: wimpunk Okay, I'm happy ddclient is working correctly. :-) I'm wondering how you try to test your http-server. Some routers have problems if you try to access an internal server using the WAN-IP. I hope this is not causing your problems. If you can access your site using the IP and if your site isn't accessible using the hostname there must be a problem with the configuration of your webserver, unless your own dns isn't working correctly. If you're running linux, you could try something like `host georgievilla.dynalias.net` to verify if your local dns got the update. At last, you could verify if there isn't any proxy or firewall rule blocking your request. I hope it helps, wimpunk. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
|
From: SourceForge.net <no...@so...> - 2008-11-19 11:05:00
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5674520 By: rloc I really don't get the clue on what you try to say. Ddclient does only one thing: it checks your IP based on the "use" parameter and update dyndns. So here are my questions: Q1: check the status page of your router. what does it report. ***IP address is reported as 41.245.110.221*** Q2: looking at your output, ddclient reports 41.245.110.221 as your IP address, is this correct? ***Yes*** Q3: if you answer yes to Q2, ddclient works correctly. The last two lines of your logging are telling you that ddclient found 41.245.110.221 as your IP address and it doesn't update dyndns because ddclient has address 41.245.110.221 is its cache file. ***I understand and I agree that ddclient is now working correctly. So if you think ddclient doesn't work correctly, please try to explain why ddclient doesn't work and try to be very clear. use pastebin if you want to post some configuration or logging result. ***What I don't understand is why my site is still not accessible via it's URL but IS accessible if I browse it's IP address. I thought the binding of the URL to the changing external IP address was the function of ddclient. Given that ddclient now appears to work, do you have any suggestions as to why I can not access the site via its URL? Please understand that I am not suggesting that there are bugs or malfunctions in ddclient. In my limited understanding of DDNS and ddclient it appeared to me that the reason I can't find my page using it's URL HAD to be because ddclient wasn't working. Thanks for all your help regards Robert ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
|
From: SourceForge.net <no...@so...> - 2008-11-18 19:04:09
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5669711 By: wimpunk Please, use pastebin to post debug results. I really don't get the clue on what you try to say. Ddclient does only one thing: it checks your IP based on the "use" parameter and update dyndns. So here are my questions: Q1: check the status page of your router. what does it report. Q2: looking at your output, ddclient reports 41.245.110.221 as your IP address, is this correct? Q3: if you answer yes to Q2, ddclient works correctly. The last two lines of your logging are telling you that ddclient found 41.245.110.221 as your IP address and it doesn't update dyndns because ddclient has address 41.245.110.221 is its cache file. So if you think ddclient doesn't work correctly, please try to explain why ddclient doesn't work and try to be very clear. use pastebin if you want to post some configuration or logging result. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
1 message has been excluded from this view by a project administrator.
