ddclient-forum Mailing List for ddclient (Page 19)
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...> - 2007-11-28 10:17:56
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4647277 By: jordipujol when working with a Live OS, ddclient cache files are not saved, and when restarting the machine, ddclient allways updates the Dns service. An alternative to cache is the DNS lookup, don't use cache only perform a DNS lookup. If the address obtained from the DNS answer is wrong, do the update. I suggest a new option "--dnslookup" to change this behaviour. Here is a patch to implement this option, I want to include the option "dnslookup=yes" in the ddclient.conf file, but I don't have reached the right coding. --- /home/jpujol/Documents/ddclient-dnslookup/data-3.7.3-4/usr/sbin/ddclient 200 7-10-20 22:55:15.000000000 +0200 +++ /usr/sbin/ddclient 2007-11-28 10:34:16.093155061 +0100 @@ -332,6 +332,7 @@ 'retry' => setv(T_BOOL, 0, 0, 0, 0, undef), 'force' => setv(T_BOOL, 0, 0, 0, 0, undef), 'ssl' => setv(T_BOOL, 0, 0, 0, 0, undef), + 'dnslookup' => setv(T_BOOL, 0, 0, 0, 0, undef), 'syslog' => setv(T_BOOL, 0, 0, 1, 0, undef), 'facility' => setv(T_STRING,0, 0, 1, 'daemon', undef), @@ -531,6 +532,7 @@ [ "retry", "!", "-{no}retry : retry failed updates." ], [ "force", "!", "-{no}force : force an update even if the update may be unnecessary" ], [ "timeout", "=i", "-timeout max : wait at most 'max' seconds for the host to respond" ], + [ "dnslookup", "!", "-{no}dnslookup : dont'use cache, verify service setup with a dns lookup" ], [ "syslog", "!", "-{no}syslog : log messages to syslog" ], [ "facility", "=s", "-facility {type} : log messages to syslog to facility {type}" ], @@ -1980,6 +1982,12 @@ info("forcing update of %s.", $host); $update = 1; + } elsif ($opt{'dnslookup'}) { + info("lookup for the DNS records of %s.", $host); + my $address = inet_ntoa(inet_aton($host)); + if ($address ne $ip) { + $update = 1; + } } elsif (!exists($cache{$host})) { info("forcing updating %s because no cached entry exists.", $host); $update = 1; ______________________________________________________________________ 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=467339 |
|
From: SourceForge.net <no...@so...> - 2007-11-26 09:25:48
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4642146 By: wimpunk I like the idea of your update but could you please put your patch in the patches section? The forum modifies the format of your patch... In your original post you're referring to something on freshmeat. Could you add a link to it? Do you have any link to a *good* explination how to configure bind to be able to use your patch? ______________________________________________________________________ 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...> - 2007-11-25 23:21:05
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4641681 By: csrc oops, try this patch instead: =========={ cut here }=========== --- original/ddclient 2007-11-25 16:02:30.000000000 -0700 +++ patched/ddclient 2007-11-25 16:16:46.000000000 -0700 @@ -13,7 +13,7 @@ use Sys::Hostname; use IO::Socket; -my $version = "3.6.3"; +my $version = "3.6.3.ns"; my $programd = $0; $programd =~ s%^.*/%%; my $program = $programd; @@ -247,6 +247,10 @@ 'mx' => setv(T_OFQDN, 0, 1, 1, '', undef), 'mxpri' => setv(T_NUMBER, 0, 0, 1, 5, undef), }, + 'nsupdate-common-defaults' => { + 'ttl' => setv(T_NUMBER, 0, 1, 0, 0, undef), + 'zone' => setv(T_STRING, 1, 1, 1, '', undef), + }, ); my %services = ( 'dyndns1' => { @@ -319,6 +323,17 @@ $variables{'service-common-defaults'}, ), }, + 'nsupdate' => { + 'updateable' => undef, + 'update' => \&nic_nsupdate_update, + 'examples' => \&nic_nsupdate_examples, + 'variables' => merge( + { 'login' => setv(T_LOGIN, 1, 0, 1, 'nsupdate', undef),}, + { 'ttl' => setv(T_NUMBER, 0, 1, 0, 600, undef),}, + $variables{'nsupdate-common-defaults'}, + $variables{'service-common-defaults'}, + ), + }, ); $variables{'merged'} = merge($variables{'global-defaults'}, $variables{'service-common-defaults'}, @@ -2659,3 +2674,112 @@ } } ###################################################################### + +###################################################################### +## nic_nsupdate_updateable +###################################################################### +sub nic_nsupdate_updateable { + return 0; +} +###################################################################### +## nic_nsupdate_examples +###################################################################### +sub nic_nsupdate_examples { + return <<EoEXAMPLE; +o 'nsupdate' + +The 'nsupdate' protocol is used to submit Dynamic DNS Update requests as +defined in RFC2136 to a name server. This allows resource records to be +added or removed from a zone without manually editing the zone file. + +The bind9 server from Internet Systems Consortium, Inc. ("ISC") is an +example of such a server and client. + +Configuration variables specific to the 'nsupdate' protocol are: + +ttl=600 ## ttl - Time To Live of record + ## defaults to 600 seconds +zone=dynamic.example.com ## forward zone that is to be updated + +Configuration variables applicable to the 'nsupdate' protocol are: + +login=nsupdate ## this option is not used and is defaulted + ## to nsupdate + +server= ## name or IP address of the Dynamic Name Server +protocol=nsupdate ## sub-updater flag for ddclient +pasword= ## path and name of the key file to use for secure + ## name updates +<hostname> ## hostname of record to update; the zone name will be + ## appended where approriate + +Example of a fully populated ${program}.conf entry: + +## +## nsupdate (isc.org) +## +server=127.0.0.1, \\ +protocol=nsupdate, \\ +zone=dynamic.example.com, \\ +password=/etc/${program}/Kmy-dynamic-key.+157+12345.private, \\ +ttl=42300, \\ +my-dynamic-hostname + +EoEXAMPLE +} +###################################################################### +## nic_nsupdate_update +###################################################################### +sub nic_nsupdate_update { + debug("\nnic_nsupdate_update -------------------"); + + ## group hosts with identical attributes together + ## my %groups = group_hosts_by([ @_ ], [ qw(login password server wildcard mx backupmx) ]); + + ## each host is in a group by itself + my %groups = map { $_ => [ $_ ] } @_; + + + ## update each set of hosts that had similar configurations + foreach my $sig (keys %groups) { + my @hosts = @{$groups{$sig}}; + my $hosts = join(',', @hosts); + my $h = $hosts[0]; + my $dnsserver = $config{$h}{'server'}; + my $dnsttl = $config{$h}{'ttl'}; + my $dnszone = $config{$h}{'zone'}; + info("setting IP address to %s for %s", $ip, $hosts); + verbose("UPDATE:","updating %s", $hosts); + + my $url; + $url = "server $dnsserver\n"; + $url .= "zone $dnszone\n"; + $url .= "update delete $hosts.$dnszone\n"; + $url .= "update add $hosts.$dnszone $dnsttl A $ip\n"; + $url .= "send\n"; + + my $command; + + if (opt('debug')) { + $command = "/usr/bin/nsupdate -d -k $config{$h}{'password'} "; + } else { + $command = "/usr/bin/nsupdate -k $config{$h}{'password'} "; + } + verbose("UPDATE:","Bind Command is :%s", $command); + verbose("UPDATE:","Bind Arguments is :%s", $url); + + my $status = pipecmd($command,$url); + + + + if ($status eq 1) { + $config{$h}{'ip'} = $ip; + $config{$h}{'mtime'} = $now; + success("updating %s: %s: IP address set to %s", $h, $status, $ip); + } else { + failed("updating %s", $h ); + } + + } +} +###################################################################### ______________________________________________________________________ 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...> - 2007-11-25 22:54:17
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4641652 By: csrc Hello All, Here is a patch to ddclient 3.6.3 to enable via nsupdate. I took and extended the original idea from the freshmeat list. Help information is included in the patch to ddclient. Thanks for poviding a great and extendable base program! =============={ Cut Here }======================= --- ddclient.ori 2007-11-25 12:06:19.000000000 -0700 +++ ddclient 2007-11-25 15:49:10.000000000 -0700 @@ -13,7 +13,7 @@ use Sys::Hostname; use IO::Socket; -my $version = "3.6.3"; +my $version = "3.6.3.ns"; my $programd = $0; $programd =~ s%^.*/%%; my $program = $programd; @@ -247,6 +247,10 @@ 'mx' => setv(T_OFQDN, 0, 1, 1, '', undef), 'mxpri' => setv(T_NUMBER, 0, 0, 1, 5, undef), }, + 'nsupdate-common-defaults' => { + 'ttl' => setv(T_NUMBER, 0, 1, 0, 0, undef), + 'zone' => setv(T_STRING, 1, 1, 1, '', undef), + }, ); my %services = ( 'dyndns1' => { @@ -319,6 +323,17 @@ $variables{'service-common-defaults'}, ), }, + 'nsupdate' => { + 'updateable' => undef, + 'update' => \&nic_nsupdate_update, + 'examples' => \&nic_nsupdate_examples, + 'variables' => merge( + { 'login' => setv(T_LOGIN, 1, 0, 1, 'nsupdate', undef),}, + { 'ttl' => setv(T_NUMBER, 0, 1, 0, 600, undef),}, + $variables{'nsupdate-common-defaults'}, + $variables{'service-common-defaults'}, + ), + }, ); $variables{'merged'} = merge($variables{'global-defaults'}, $variables{'service-common-defaults'}, @@ -2659,3 +2674,112 @@ } } ###################################################################### + +###################################################################### +## nic_nsupdate_updateable +###################################################################### +sub nic_nsupdate_updateable { + return 0; +} +###################################################################### +## nic_nsupdate_examples +###################################################################### +sub nic_nsupdate_examples { + return <<EoEXAMPLE; +o 'nsupdate' + +The 'nsupdate' protocol is used to submit Dynamic DNS Update requests as +defined in RFC2136 to a name server. This allows resource records to be +added or removed from a zone without manually editing the zone file. + +The bind9 server from Internet Systems Consortium, Inc. ("ISC") is an +example of such a server and client. + +Configuration variables specific to the 'nsupdate' protocol are: + +ttl=600 ## ttl - Time To Live of record + ## defaults to 600 seconds +zone=dynamic.example.com ## forward zone that is to be updated + +Configuration variables applicable to the 'nsupdate' protocol are: + +login=nsupdate ## this option is not used and is defaulted + ## to nsupdate + +server= ## name or IP address of the Dynamic Name Server +protocol=nsupdate ## sub-updater flag for ddclient +pasword= ## path and name of the key file to use for secure + ## name updates +<hostname> ## hostname of record to update; the zone name will be + ## appended where approriate + +Example of a fully populated ${program}.conf entry: + +## +## nsupdate (isc.org) +## +server=127.0.0.1, \\ +protocol=nsupdate, \\ +zone=dynamic.example.com, \\ +password=/etc/${program}/Kmy-dynamic-key.+157+12345.private, \\ +ttl=42300, \\ +my-dynamic-hostname + +EoEXAMPLE +} +###################################################################### +## nic_nsupdate_update +###################################################################### +sub nic_nsupdate_update { + debug("\nnic_nsupdate_update -------------------"); + + ## group hosts with identical attributes together + ## my %groups = group_hosts_by([ @_ ], [ qw(login password server wildcard mx backupmx) ]); + + ## each host is in a group by itself + my %groups = map { $_ => [ $_ ] } @_; + + + ## update each set of hosts that had similar configurations + foreach my $sig (keys %groups) { + my @hosts = @{$groups{$sig}}; + my $hosts = join(',', @hosts); + my $h = $hosts[0]; + my $dnsserver = $config{$h}{'server'}; + my $dnsttl = $config{$h}{'ttl'}; + my $dnszone = $config{$h}{'zone'}; + info("setting IP address to %s for %s", $ip, $hosts); + verbose("UPDATE:","updating %s", $hosts); + + my $url; + $url = "server $dnsserver\n"; + $url .= "zone $dnszone\n"; + $url .= "update delete $hosts.$dnszone\n"; + $url .= "update add $hosts.$dnszone $dnsttl A $ip\n"; + $url .= "send\n"; + + my $command; + + if (opt('debug')) { + $command = "/usr/bin/nsupdate -d -k $config{$h}{'password'} "; + } else { + $command = "/usr/bin/nsupdate -k $config{$h}{'password'} "; + } + verbose("UPDATE:","Bind Command is :%s", $command); + verbose("UPDATE:","Bind Arguments is :%s", $url); + + my $status = pipecmd($command,$url); + + + + if ($status eq 1) { + $config{$h}{'ip'} = $ip; + $config{$h}{'mtime'} = $now; + success("updating %s: %s: IP address set to %s", $h, $status, $ip); + } else { + failed("updating %s", $h ); + } + + } +} +###################################################################### ______________________________________________________________________ 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...> - 2007-11-23 04:24:04
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4638447 By: jd2066 It does appear a max-interval value of 365d is accepted. ______________________________________________________________________ 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...> - 2007-11-22 08:53:30
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4637159 By: wimpunk Taking a look at the code, it seems like there's no way to disable it. Maybe I could try to add something useful but meanwhile you could try to increase the setting to something like "max-interval=300d". I'm not very sure if the d-syntax will work but you could try it and post any result 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=399428 |
|
From: SourceForge.net <no...@so...> - 2007-11-21 23:15:07
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4636691 By: jd2066 Hi, I would like to disable the force update on the 25th day so feature as I don't need it with a NameCheap domain. Justin ______________________________________________________________________ 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...> - 2007-11-16 08:29:09
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4626686 By: wimpunk you need a "use" option. It specifies where ddclient has to get the ip from. Check ddclient.sf.net or ddclient --help or the ddclient.conf example. ______________________________________________________________________ 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...> - 2007-11-16 00:53:30
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4626307 By: dimension128 hehe that was a really stupid move. My login name is changed 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...> - 2007-10-31 07:51:59
|
Feature Requests item #1822965, was opened at 2007-10-30 18:56 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=1822965&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: Vlad Skarzhevskyy (vlads) Assigned to: Nobody/Anonymous (nobody) Summary: IP change E-mail notification format Initial Comment: When ddclient perform some actions you will get e-mail "status report from ddclient@...org" Example: WARNING: forcing update of jtidy.homelinux.net from 90.226.153.146 to 90.226.153.146; 15 days since last update on Mon Oct 15 02:48:29 2007. As you see the IP address is not actually changed! I think it will be very informative to have different subject or e-mail text when IP actual changes. e.g. first line in message: --- IMPORTANT: IP changed from 90.26.53.31 to 90.26.53.146 25 days since last IP changes. --- ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2007-10-31 07:51 Message: Logged In: YES user_id=722282 Originator: NO I like the idea but currently there are no developers to implement this... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=1822965&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2007-10-30 18:56:02
|
Feature Requests item #1822965, was opened at 2007-10-30 14:56 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=1822965&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: Vlad Skarzhevskyy (vlads) Assigned to: Nobody/Anonymous (nobody) Summary: IP change E-mail notification format Initial Comment: When ddclient perform some actions you will get e-mail "status report from ddclient@...org" Example: WARNING: forcing update of jtidy.homelinux.net from 90.226.153.146 to 90.226.153.146; 15 days since last update on Mon Oct 15 02:48:29 2007. As you see the IP address is not actually changed! I think it will be very informative to have different subject or e-mail text when IP actual changes. e.g. first line in message: --- IMPORTANT: IP changed from 90.26.53.31 to 90.26.53.146 25 days since last IP changes. --- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=1822965&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2007-10-30 11:46:09
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4596051 By: wimpunk If https://sourceforge.net/forum/message.php?msg_id=4595915 is correct it's related to a bug in SSL: ______________________________________________________________________ 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...> - 2007-10-30 11:42:20
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4596044 By: wimpunk Thank you very much for the feedback. I appreciate the work you did for this issue. ______________________________________________________________________ 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...> - 2007-10-30 10:09:14
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4595915 By: ndarlow This was actually a bug in IO::Socket::SSL-1.11 which is fixed in IO::Socket::SSL-1.12. The former version of IO::Socket::SSL treated a timeout value of 0 as a timeout condition. The latter treats it as not a timeout. ______________________________________________________________________ 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...> - 2007-10-29 21:11:01
|
Bugs item #1085110, was opened at 2004-12-14 13:35 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=1085110&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: Other Group: current version >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: J. Randall Owens (karmannjro) Assigned to: darin (ddfisher) Summary: -timeout ignored Initial Comment: It looks like, althought the builtin documentation and variables describe a -timeout= option, when IO::Socket::INET->new is called in geturl at line 1546, it isn't given as an argument to it. I won't bother with a patch for this one, it just needs a ", Timeout => opt('timeout')" stuck in those arguments somewhere. ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2007-10-29 21:10 Message: Logged In: YES user_id=722282 Originator: NO It rather looks like my brain got stuck somewhere. The problem I was referring to wasn't related to the initial timeout. It referred to the initial timeout value fixed on svn revision 81. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2007-10-29 20:26 Message: Logged In: YES user_id=722282 Originator: NO It looks like the problem is back. It happens when using ssl. Do you have the patch you applied somewhere? I found a message about it in the ChangeLog but could't find the patch... wimpunk. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2007-05-21 15:23 Message: Logged In: YES user_id=722282 Originator: NO Has been patched almost a year ago by ddfisher (tnx again) ---------------------------------------------------------------------- Comment By: darin (ddfisher) Date: 2006-06-06 07:30 Message: Logged In: YES user_id=1534437 added the timeout to the IO::Socket call to help with the initial connection. timeout is already being used when reading from the current connection ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2005-01-02 13:05 Message: Logged In: YES user_id=722282 you're always welcome to write the patch. wimpunk. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=1085110&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2007-10-29 20:26:30
|
Bugs item #1085110, was opened at 2004-12-14 13:35 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=1085110&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: Other Group: current version >Status: Open Resolution: None Priority: 5 Private: No Submitted By: J. Randall Owens (karmannjro) Assigned to: darin (ddfisher) Summary: -timeout ignored Initial Comment: It looks like, althought the builtin documentation and variables describe a -timeout= option, when IO::Socket::INET->new is called in geturl at line 1546, it isn't given as an argument to it. I won't bother with a patch for this one, it just needs a ", Timeout => opt('timeout')" stuck in those arguments somewhere. ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2007-10-29 20:26 Message: Logged In: YES user_id=722282 Originator: NO It looks like the problem is back. It happens when using ssl. Do you have the patch you applied somewhere? I found a message about it in the ChangeLog but could't find the patch... wimpunk. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2007-05-21 15:23 Message: Logged In: YES user_id=722282 Originator: NO Has been patched almost a year ago by ddfisher (tnx again) ---------------------------------------------------------------------- Comment By: darin (ddfisher) Date: 2006-06-06 07:30 Message: Logged In: YES user_id=1534437 added the timeout to the IO::Socket call to help with the initial connection. timeout is already being used when reading from the current connection ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2005-01-02 13:05 Message: Logged In: YES user_id=722282 you're always welcome to write the patch. wimpunk. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=1085110&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2007-10-29 20:05:56
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4594428 By: ndarlow I added timeout=120 to ddclient.conf long before that message was posted. That was why I suggested that a default timeout value is added to the ddclient 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=399428 |
|
From: SourceForge.net <no...@so...> - 2007-10-28 22:40:28
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4592923 By: wimpunk Your question doesn't belong on the open-discussion forum, you're just asking for help. I suppose (it's not clear from your wrinting) you use "use=web". You could try to force ddclient using a specific interface by forcing the route to checkip.dyndns.org. Check the manual from your router or your operating system how to do this. ______________________________________________________________________ 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...> - 2007-10-28 15:44:35
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4592512 By: hypoj I run ddclient on a Fedora box with multiple internet connections and found that ddclient keeps updating the DNS server with changing IP addresses. Perhaps each time it checks the IP address it finds a different IP from a different internet connection. Is there a way to tell ddclient to check the IP address via a predefined WAN interface to avoid this problem? Thanks, Tri ______________________________________________________________________ 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...> - 2007-10-27 10:42:20
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4591283 By: wimpunk I think your message is related to this one: https://sourceforge.net/forum/message.php?msg_id=4590232 Maybe you could try the solution mentioned there? ______________________________________________________________________ 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...> - 2007-10-27 08:14:17
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4591187 By: ndarlow Hi, I am running ddclient-3.7.3, on FreeBSD-6.2, with IO::Socket::SSL-1.11 (both installed from FreeBSD ports). I have been using ddclient-3.7.1 successfully with SSL until I updated to ddclient-3.7.3. After the update, I get a SSL timeout and termination of the update process on connecting to the first server. I use ddclient to update against dyndns.com and opendns.com (for opendns a patch was necessary until they recently changed their URI to be fully NIC2 compliant). Has anyone else observed timeouts when using SSL? I am able to update successfully if I supply the timeout option in ddclient.conf but I wish to determine why, and when, the need for this arose. Regards, Neil Darlow ______________________________________________________________________ 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...> - 2007-10-26 17:18:38
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4590232 By: phobosk Hi, I just want to tell my experience using SSL with ddclient on ubuntu (it may happen on every distro i think). If ddclient cannot update your records when "ssl=yes" please be sure to include the "timeout=120" option in the configuration file of ddclient. For more info please read this thread: https://bugs.launchpad.net/ubuntu/+source/ddclient/+bug/116066 ______________________________________________________________________ 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...> - 2007-10-26 07:45:24
|
Bugs item #1820127, was opened at 2007-10-25 16:42 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=1820127&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: Other Group: None >Status: Open Resolution: None Priority: 5 Private: No Submitted By: Neil Darlow (ndarlow) Assigned to: wimpunk (wimpunk) Summary: timeout option needs default value Initial Comment: I just updated to ddclient-3.7.3 and immediately had problems with timeout errors when performing updates with SSL. Looking at the timeout option initialisation code I see that a minimum value of 120s is specified but there is no default value. May I suggest that interval('120s') is put in the default field of the timeout option. ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2007-10-26 07:45 Message: Logged In: YES user_id=722282 Originator: NO I've done some extra investigation about what changed. The last modification concerning the timeout was this one: - added timeout option to the IO::Socket call for timing out the initial connection, bug: #1085110 It can be found in the changelog of 3.7.0 Since most users first check the forum, please let's take this discussion to the forum. Maybe there are more people out there who could help us tracking this bug down. ---------------------------------------------------------------------- Comment By: Neil Darlow (ndarlow) Date: 2007-10-25 17:28 Message: Logged In: YES user_id=39443 Originator: YES I am using ddclient on FreeBSD. Before 3.7.3 I never needed to use timeout but now I must specify it or I receive timeout errors reliably. I am not alone in seeing this. I have asked another person to confirm my findings and he reports the same problem exactly. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2007-10-25 17:00 Message: Logged In: YES user_id=722282 Originator: NO Works for me. When timeout isn't specified, it uses your system defaults is better than specifying a specific timeout from ddclient. Timeout should only be used in rare situations. And please first discuss your problem before posting it a as bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=1820127&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2007-10-26 06:39:12
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4589354 By: wimpunk First, I don't know why you think there's no static IP anymore. it's been rearranged, that's true but you can still choose this TTL: "4Hrs. Static record with the benefit of DNS cache". That's the one you need for a static host. Btw you need to click on "edit ttl" to be able to change this. Second, the feature you want is already there. Check max-interval. By default the value is set to match the dyndns recommendation. ______________________________________________________________________ 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=467339 |
|
From: SourceForge.net <no...@so...> - 2007-10-25 22:44:00
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4588677 By: teqno79 Would be nice with a feature that do a forced update every 28th day to keep the dyndns accounts alive cuz now when dyndns have changed their services you can't use static ip's anymore just dynamic. ______________________________________________________________________ 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=467339 |
1 message has been excluded from this view by a project administrator.
