ddclient-forum Mailing List for ddclient (Page 8)
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...> - 2009-03-13 17:19:06
|
Patches item #2686326, was opened at 2009-03-13 13:18 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=2686326&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: Kyle Powell (z-row) Assigned to: Nobody/Anonymous (nobody) Summary: A few more minor patches Initial Comment: patch2: I've noticed a common help topic is user accounts being blocked for abuse when ddclient is unable to write to the cache file [1][2]. The patch causes ddclient to attempt to create the cache file if it doesn't exist and fail with a fatal() if it cannot create the file. [1] https://sourceforge.net/forum/forum.php?thread_id=1799118&forum_id=399427 [2] https://sourceforge.net/forum/forum.php?thread_id=1994414&forum_id=399428 patch3: Add info on what provides IO::Socket::SSL for Fedora (not usually necessary since the Fedora ddclient package has the proper requirements). patch4: A minor typo I saw ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2686326&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-03-13 16:59:24
|
Patches item #2686318, was opened at 2009-03-13 12:58 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=2686318&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: Kyle Powell (z-row) Assigned to: Nobody/Anonymous (nobody) Summary: Implement DynDNS Feature Request[1] Initial Comment: [1] https://sourceforge.net/forum/forum.php?thread_id=1668195&forum_id=467339 This patch will check the mtime of the configuration file if a host using the dyndns2 protocol needs to be updated but its last update attempt failed. If the mtime of the config file is older that the atime of the failure, the update is not sent. The user must modify the config file (and hopefully fix whatever caused the failure) before an update will be sent. The check is subordinate to the min-error-interval check. [root@foo ~]# ddclient -verbose INFO: setting IP address to 192.168.69.173 for testing.dyndns.org UPDATE: updating testing.dyndns.org CONNECT: members.dyndns.org CONNECTED: using SSL SENDING: GET /nic/update?system=statdns&hostname=testing.dyndns.org&myip=192.168.69.173 HTTP/1.0 SENDING: Host: members.dyndns.org SENDING: Authorization: Basic dGVzdG1lOnBhc3N3b3Jk SENDING: User-Agent: ddclient/3.8.0 SENDING: Connection: close SENDING: RECEIVE: HTTP/1.1 200 OK RECEIVE: Date: Fri, 13 Mar 2009 16:44:55 GMT RECEIVE: Server: Apache RECEIVE: Content-Type: text/plain RECEIVE: Connection: close RECEIVE: RECEIVE: badauth FAILED: updating testing.dyndns.org: badauth: Bad authorization (username or password) [root@foo ~]# ddclient -verbose WARNING: file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = '' WARNING: skipping update of testing.dyndns.org from <nothing> to 192.168.69.173. WARNING: last updated <never> but last attempt on Fri Mar 13 12:45:55 2009 failed. WARNING: Wait at least 5 minutes between update attempts. [root@foo ~]# sleep 300 You have new mail in /var/spool/mail/root [root@foo ~]# ddclient -verbose WARNING: skipping update of testing.dyndns.org from <nothing> to 192.168.69.173. WARNING: last update attempt on Fri Mar 13 12:45:55 2009 failed. WARNING: /etc/ddclient/ddclient.conf last updated Fri Mar 13 12:45:42 2009. WARNING: please make necessary configuration changes to correct the last failure. [root@foo ~]# vi /etc/ddclient/ddclient.conf [root@foo ~]# ddclient -verbose INFO: setting IP address to 192.168.69.173 for testing.dyndns.org UPDATE: updating testing.dyndns.org CONNECT: members.dyndns.org CONNECTED: using SSL SENDING: GET /nic/update?system=statdns&hostname=testing.dyndns.org&myip=192.168.69.173 HTTP/1.0 SENDING: Host: members.dyndns.org SENDING: Authorization: Basic dGVzdDpwYXNzd29yZA== SENDING: User-Agent: ddclient/3.8.0 SENDING: Connection: close ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2686318&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-03-10 01:08:35
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6719272 By: krisrj Actually, this goes better in the patches tracker. This doesn't look easy to copy. A diff is attached to the tracker entry. ______________________________________________________________________ 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=399429 |
|
From: SourceForge.net <no...@so...> - 2009-03-10 01:05:57
|
Patches item #2677045, was opened at 2009-03-09 17:05 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=2677045&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: new router Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kris Jordan (krisrj) Assigned to: Nobody/Anonymous (nobody) Summary: Support for Westell 7500 Initial Comment: Patch file against 3.8.0 provided. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2677045&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-03-10 01:01:10
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6719195 By: krisrj --- ddclient-3.8.0 2009-01-27 11:14:02.000000000 -0800 +++ ddclient 2009-03-09 17:49:28.000000000 -0700 @@ -205,6 +205,11 @@ 'url' => '/advstat.htm', 'skip' => 'IP.+?Address', }, + 'westell-7500' => { + 'name' => 'Westell A90-750015-07 Wireless DSL Router', + 'url' => '/htmlV/sys_router_stat.asp', + 'skip' => 'IP.+?Address', + }, '2wire' => { 'name' => '2Wire 1701HG Gateway', 'url' => '/xslt?PAGE=B01', ______________________________________________________________________ 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=399429 |
|
From: SourceForge.net <no...@so...> - 2009-02-27 07:44:56
|
Bugs item #1984083, was opened at 2008-06-04 03:25 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=1984083&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: Fixed Priority: 5 Private: No Submitted By: Ron Isaacson (ron_isaacson) Assigned to: wimpunk (wimpunk) Summary: geturl doesn't follow redirects Initial Comment: Recently, www.zoneedit.com started issuing redirects to dynamic.zoneedit.com: % curl 'http://www.zoneedit.com/auth/dynamic.html?host=XXX.com&dnsto=X.X.X.X' <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="http://dynamic.zoneedit.com/auth/dynamic.html?host=XXX.com&dnsto=X.X.X.X">here</a>.</p> </body></html> Unfortunately, geturl doesn't implement a full-featured HTTP client, so it's not able to follow the redirect. Instead, it fails to update, but without a meaningful error message, and leaves the cache in an invalid state after a failed attempt. (See output below.) geturl should probably be changed to use LWP::UserAgent. It seems the current implementation is meant to avoid external dependencies, but switching to LWP::UserAgent would make it standards-compliant, and the whole function would probably only be about 5 lines! If you don't want to do that, please at least ensure that unexpected responses produce meaningful errors and no cache corruption. Thank you! === With no cache file: === % /usr/sbin/ddclient -daemon=0 -noquiet -debug DEBUG: get_ip: using if, eth0 reports X.X.X.X DEBUG: DEBUG: nic_zoneedit1_update ------------------- DEBUG: proxy = DEBUG: url = http://www.zoneedit.com/auth/dynamic.html?host=XXX.com&dnsto=X.X.X.X DEBUG: server = www.zoneedit.com No further messages to indicate that the response from the webserver was not as expected. === With the cache file produced after the above: === % /usr/sbin/ddclient -daemon=0 -noquiet -debug WARNING: file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = '' DEBUG: get_ip: using if, eth0 reports X.X.X.X Use of uninitialized value in string ne at /usr/sbin/ddclient line 1968. WARNING: skipping update of XXX.com from <nothing> to X.X.X.X. WARNING: last updated <never> but last attempt on Tue Jun 3 22:44:46 2008 failed. WARNING: Wait at least 5 minutes between update attempts. After 5 minutes, repeats as above. === The cache file === % cat ddclient.cache ## ddclient-3.7.3 ## last updated at Tue Jun 3 22:44:46 2008 (1212547486) atime=1212547486,host=XXX.com,ip=,mtime=0,status=noconnect,warned-min-error-interval=0,warned-min-interval=0,wtime=0 XXX.com ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2009-02-27 07:44 Message: Ddclient has been written to use as less libraries as necessary. This issue has been fixed by correcting the zoneedit settings. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-06-08 12:01 Message: Logged In: YES user_id=722282 Originator: NO Your config worked correct because the server config was correct. So it could be use full to add the server to ddclient.conf when they change the server url. As I wrote before, it is a good idea to catch the redirect. But the ddclient developers has to get the time to work on it and currently it's looking like every one is missing some hours a day. ---------------------------------------------------------------------- Comment By: Ron Isaacson (ron_isaacson) Date: 2008-06-08 02:14 Message: Logged In: YES user_id=2107106 Originator: YES Been using the same config for years... oh well. Anyway, possibly even more important than handling the redirect is giving a detailed error if the response is unexpected. If the failure message contained the complete contents of the web server's response, it would be much easier to track down any problems. As is, it's impossible to figure out what ddclient is doing. Thanks! ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-06-05 06:51 Message: Logged In: YES user_id=722282 Originator: NO Actually, you misconfigured ddclient if you run a recent version and you get in this error. You don't need the server= stuff if you're just using the default zoneedit settings. Besides this it is a useful thought to implement the redirect. It would probably been done not using the LWP::UserAgent because of avoiding external dependencies. We already had enough trouble when people were trying to use the ssl-support. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=1984083&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-27 07:43:13
|
Bugs item #2230313, was opened at 2008-11-06 17:04 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2230313&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: Accepted Priority: 6 Private: No Submitted By: j c (lostsole) Assigned to: wimpunk (wimpunk) Summary: multiple hosts update at namecheap Initial Comment: I am having having trouble getting ddclient to update multiple hosts at namecheap. ddclient works great with one host, but when i add a second host to be updated ddclient only updates the second host in the list. thank you very very much # Configuration file for ddclient generated by debconf # # /etc/ddclient.conf daemon=600 syslog=yes pid=/var/run/ddclient.pid use=web, web=checkip.dyndns.org, web-skip='IP Address' protocol=namecheap server=dynamicdns.park-your-domain.com login=mydomain1.com password='xxxxxxxxxxxxxxxxxxxxxxxxxxx' www protocol=namecheap server=dynamicdns.park-your-domain.com login=mydomain2.com password='xxxxxxxxxxxxxxxxxxxxxxxxxxx' www here is the output from ddclient -daemon=0 -debug -verbose -noquiet === opt ==== opt{cache} : <undefined> opt{cmd} : <undefined> opt{cmd-skip} : <undefined> opt{daemon} : 0 opt{debug} : 1 opt{exec} : <undefined> opt{facility} : <undefined> opt{file} : <undefined> opt{force} : <undefined> opt{fw} : <undefined> opt{fw-login} : <undefined> opt{fw-password} : <undefined> opt{fw-skip} : <undefined> opt{geturl} : <undefined> opt{help} : <undefined> opt{host} : <undefined> opt{if} : <undefined> opt{if-skip} : <undefined> opt{ip} : <undefined> opt{login} : <undefined> opt{mail} : <undefined> opt{mail-failure} : <undefined> opt{max-interval} : 2592000 opt{min-error-interval} : 300 opt{min-interval} : 30 opt{options} : <undefined> opt{password} : <undefined> opt{pid} : <undefined> opt{priority} : <undefined> opt{protocol} : <undefined> opt{proxy} : <undefined> opt{query} : <undefined> opt{quiet} : 0 opt{retry} : <undefined> opt{server} : <undefined> opt{ssl} : <undefined> opt{syslog} : <undefined> opt{test} : <undefined> opt{timeout} : <undefined> opt{use} : <undefined> opt{verbose} : 1 opt{web} : <undefined> opt{web-skip} : <undefined> === globals ==== globals{daemon} : 60 globals{debug} : 1 globals{login} : mydomain2.com globals{password} : xxxxxxxxxxxxxxxxxxxxxxxxxxxx globals{pid} : /var/run/ddclient.pid globals{protocol} : namecheap globals{quiet} : 0 globals{server} : dynamicdns.park-your-domain.com globals{syslog} : 1 globals{use} : web globals{verbose} : 1 globals{web} : checkip.dyndns.org globals{web-skip} : IP Address === config ==== config{www}{atime} : 1225960486 config{www}{cacheable} : ARRAY(0x83f2300) config{www}{host} : www config{www}{ip} : xxxxxxxxxxxxxx config{www}{login} : mydomain2.com config{www}{max-interval} : 2592000 config{www}{min-error-interval} : 300 config{www}{min-interval} : 300 config{www}{mtime} : 1225960486 config{www}{password} : xxxxxxxxxxxxxxxxxxxxxxxxxxxx config{www}{protocol} : namecheap config{www}{server} : dynamicdns.park-your-domain.com config{www}{status} : good config{www}{warned-min-error-interval} : 0 config{www}{warned-min-interval} : 0 config{www}{wtime} : 30 === cache ==== cache{70.59.198.99}{atime} : 1225315554 cache{70.59.198.99}{host} : xxxxxxxxx cache{70.59.198.99}{mtime} : 0 cache{70.59.198.99}{status} : failed cache{70.59.198.99}{warned-min-error-interval} : 0 cache{70.59.198.99}{warned-min-interval} : 0 cache{70.59.198.99}{wtime} : 30 cache{@}{atime} : 1225315688 cache{@}{host} : @ cache{@}{mtime} : 0 cache{@}{status} : failed cache{@}{warned-min-error-interval} : 1225315791 cache{@}{warned-min-interval} : 0 cache{@}{wtime} : 30 cache{hermitshouse.com}{atime} : 1225314995 cache{hermitshouse.com}{host} : my cache{hermitshouse.com}{mtime} : 0 cache{hermitshouse.com}{status} : failed cache{hermitshouse.com}{warned-min-error-interval} : 0 cache{hermitshouse.com}{warned-min-interval} : 0 cache{hermitshouse.com}{wtime} : 30 cache{neon}{atime} : 1225314324 cache{neon}{host} : neon cache{neon}{ip} : xxxxxxxxxxxxxxx cache{neon}{mtime} : 1225074730 cache{neon}{status} : failed cache{neon}{warned-min-error-interval} : 0 cache{neon}{warned-min-interval} : 0 cache{neon}{wtime} : 30 cache{sub}{atime} : 1225316586 cache{sub}{host} : sub cache{sub}{ip} : xxxxxxxxxxxxxxx cache{sub}{mtime} : 1225316586 cache{sub}{status} : good cache{sub}{warned-min-error-interval} : 0 cache{sub}{warned-min-interval} : 0 cache{sub}{wtime} : 30 cache{www}{atime} : 1225960486 cache{www}{host} : www cache{www}{ip} : xxxxxxxxxxxxx cache{www}{mtime} : 1225960486 cache{www}{status} : good cache{www}{warned-min-error-interval} : 0 cache{www}{warned-min-interval} : 0 cache{www}{wtime} : 30 DEBUG: proxy = DEBUG: url = checkip.dyndns.org DEBUG: server = checkip.dyndns.org CONNECT: checkip.dyndns.org CONNECTED: using HTTP SENDING: GET / HTTP/1.0 SENDING: Host: checkip.dyndns.org SENDING: User-Agent: ddclient/3.7.3 SENDING: Connection: close SENDING: RECEIVE: HTTP/1.1 200 OK RECEIVE: Content-Type: text/html RECEIVE: Server: DynDNS-CheckIP/1.0 RECEIVE: Connection: close RECEIVE: Cache-Control: no-cache RECEIVE: Pragma: no-cache RECEIVE: Content-Length: 105 RECEIVE: RECEIVE: <html><head><title>Current IP Check</title></head><body>Current IP Address: xxxxxxxxxxxx</body></html> DEBUG: get_ip: using web, checkip.dyndns.org reports xxxxxxxxxxxxx DEBUG: DEBUG: nic_namecheap1_update ------------------- INFO: setting IP address to xxxxxxxxxxxxx for www UPDATE: updating www DEBUG: proxy = DEBUG: url = http://dynamicdns.park-your-domain.com/update?host=www&domain=mydomain2.com&password=xxxxxxxxxxxxxxxxxxxxxx&ip=xxxxxxxxxxxxxxxx DEBUG: server = dynamicdns.park-your-domain.com CONNECT: dynamicdns.park-your-domain.com CONNECTED: using HTTP SENDING: GET /update?host=www&domain=mydomain2.com&password=xxxxxxxxxxxxxxxxxxx&ip=xxxxxxxxxxx HTTP/1.0 SENDING: Host: dynamicdns.park-your-domain.com SENDING: User-Agent: ddclient/3.7.3 SENDING: Connection: close SENDING: RECEIVE: HTTP/1.1 200 OK RECEIVE: Connection: close RECEIVE: Date: Thu, 06 Nov 2008 08:44:38 GMT RECEIVE: Server: Microsoft-IIS/6.0 RECEIVE: X-Powered-By: ASP.NET RECEIVE: Content-Length: 235 RECEIVE: Content-Type: text/html RECEIVE: Cache-control: private RECEIVE: RECEIVE: <?xml version="1.0"?><interface-response><Command>SETDNSHOST</Command><Language>eng</Language><IP>xxxxxxxxxxxx</IP><ErrCount>0</ErrCount><ResponseCount>0</ResponseCount><Done>true</Done><debug><![CDATA[]]></debug></interface-response> SUCCESS: updating www: good: IP address set to xxxxxxxxxxxx ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2009-02-27 07:43 Message: Check the forum about namecheap problems. As far as I remember this issue should be fixed with the latest version of ddclient. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2230313&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-27 07:40:35
|
Bugs item #2619494, was opened at 2009-02-20 10:59 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619494&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: current version >Status: Closed >Resolution: Wont Fix Priority: 5 Private: No Submitted By: Marco Rodrigues (kmos) Assigned to: wimpunk (wimpunk) Summary: my router has 2 stage login (SMC7904BRA2) Initial Comment: my router (a SMC7904bra2) requires a login request be made before it will release the IP address. eg: wget http://192.168.2.1/cgi-bin/login.exe --post-data=pws=smcadmin -O- &> /dev/null wget http://192.168.2.1/status_main.stm -O- -q | grep 'var wan_ip' this (after the grep) produces a line like var wan_ip="118.90.18.201"; note the password is sent in a HTTP POST to a url different to that which returns the ip address in this case there are no cookies involved, the router just trusts the ip address it got the login from for the next few minutes (it's possible that other routers may use cookies for this?) without being preceeded by the first request the second only produces the login page. there is no username only a password field called 'pws' there is provision to turn off the timeout of the login, but after the router is rebooted another login is needed, and that's typically when ddclient is most-needed too :( I tried the use=smc-barricade option but it didn't work for me. Looking at the source (I can almost read perl) all the firewall options seem to do single-stage web requests. This bug was reported in Debian. ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2009-02-27 07:40 Message: This issue can only be fixed if the router gets sended to me or maybe by searching the forum for other related issues. As far as I remember someone got this fixed by changing the settings of the router. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2009-02-20 11:04 Message: Marco, is this really your bug or did you forwarded it from somewhere? If not, please post a link to the original bugreport. ---------------------------------------------------------------------- Comment By: Marco Rodrigues (kmos) Date: 2009-02-20 11:04 Message: Bug report at http://bugs.debian.org/488107 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619494&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-27 07:31:15
|
Bugs item #2619505, was opened at 2009-02-20 11:04 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619505&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: current version >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Marco Rodrigues (kmos) Assigned to: Nobody/Anonymous (nobody) Summary: update interval 5min causes ban at dyndns Initial Comment: DESCRIPTION Setting update interval to "5m" causes dydns provider to ban the host. SUGGESTION Please iplement safeguard so that too low update intervals are: 1) either not accepted (print error message) 2) automatically scale the interval up to the safe limit and print warning. In dyndns.org case that'd be 7 minutes. This bug was reported in Debian - http://bugs.debian.org/489997 ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2009-02-27 07:31 Message: Sorry but I can't find any details on the site of dyndns about this restriction. As far as I see there are two restrictions: * if you use checkip.dyndns.org, the minimum interval is 10 minutes * only update dyndns if you have something to update. The cache directory has to be writable to prevent ddclient do this. I've added extra comments to the sample file (r109) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619505&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-27 07:22:18
|
Bugs item #2619554, was opened at 2009-02-20 11:20 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619554&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: Marco Rodrigues (kmos) Assigned to: wimpunk (wimpunk) Summary: ddclient spawns several competing daemons Initial Comment: This bug was originally reported in Ubuntu - https://bugs.edge.launchpad.net/ubuntu/+source/ddclient/+bug/152875 I have a DSL line that gets disconnected every 24 hours, then upon a reconnect gets a new IP address. When I set both of the following settings in /etc/default/ddclient to true... ---- # Set to "true" if ddclient should be run every time a new ppp connection is # established. This might be useful, if you are using dial-on-demand run_ipup="true" # Set to "true" if ddclient should run in daemon mode run_daemon="true" ---- ...then ddclient will over time spawn several, competing ddclient daemon processes (when I noticed the issue I had 3 of them) that will almost constantly execute update requests on the dyndns server. This got me temporarily banned from dyndns.org, until I set run_ipup to false and kept the run_daemon option as true, which will work fine. My ddclient is configured to get its IP address from the interface ppp0. It's an wishlist bug as you can see in the comments. Only to prevent two options from running, to not cause problems. ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2009-02-27 07:22 Message: Won't fix, it's debian related. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2009-02-20 18:02 Message: it's a debian feature. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619554&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-20 18:02:28
|
Bugs item #2619554, was opened at 2009-02-20 11:20 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619554&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: Marco Rodrigues (kmos) Assigned to: wimpunk (wimpunk) Summary: ddclient spawns several competing daemons Initial Comment: This bug was originally reported in Ubuntu - https://bugs.edge.launchpad.net/ubuntu/+source/ddclient/+bug/152875 I have a DSL line that gets disconnected every 24 hours, then upon a reconnect gets a new IP address. When I set both of the following settings in /etc/default/ddclient to true... ---- # Set to "true" if ddclient should be run every time a new ppp connection is # established. This might be useful, if you are using dial-on-demand run_ipup="true" # Set to "true" if ddclient should run in daemon mode run_daemon="true" ---- ...then ddclient will over time spawn several, competing ddclient daemon processes (when I noticed the issue I had 3 of them) that will almost constantly execute update requests on the dyndns server. This got me temporarily banned from dyndns.org, until I set run_ipup to false and kept the run_daemon option as true, which will work fine. My ddclient is configured to get its IP address from the interface ppp0. It's an wishlist bug as you can see in the comments. Only to prevent two options from running, to not cause problems. ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2009-02-20 18:02 Message: it's a debian feature. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619554&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-20 11:20:28
|
Bugs item #2619554, was opened at 2009-02-20 11:20 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=2619554&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: Marco Rodrigues (kmos) Assigned to: wimpunk (wimpunk) Summary: ddclient spawns several competing daemons Initial Comment: This bug was originally reported in Ubuntu - https://bugs.edge.launchpad.net/ubuntu/+source/ddclient/+bug/152875 I have a DSL line that gets disconnected every 24 hours, then upon a reconnect gets a new IP address. When I set both of the following settings in /etc/default/ddclient to true... ---- # Set to "true" if ddclient should be run every time a new ppp connection is # established. This might be useful, if you are using dial-on-demand run_ipup="true" # Set to "true" if ddclient should run in daemon mode run_daemon="true" ---- ...then ddclient will over time spawn several, competing ddclient daemon processes (when I noticed the issue I had 3 of them) that will almost constantly execute update requests on the dyndns server. This got me temporarily banned from dyndns.org, until I set run_ipup to false and kept the run_daemon option as true, which will work fine. My ddclient is configured to get its IP address from the interface ppp0. It's an wishlist bug as you can see in the comments. Only to prevent two options from running, to not cause problems. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619554&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-20 11:05:08
|
Bugs item #2619494, was opened at 2009-02-20 10:59 Message generated for change (Comment added) made by kmos You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619494&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: current version Status: Open Resolution: None Priority: 5 Private: No Submitted By: Marco Rodrigues (kmos) Assigned to: wimpunk (wimpunk) Summary: my router has 2 stage login (SMC7904BRA2) Initial Comment: my router (a SMC7904bra2) requires a login request be made before it will release the IP address. eg: wget http://192.168.2.1/cgi-bin/login.exe --post-data=pws=smcadmin -O- &> /dev/null wget http://192.168.2.1/status_main.stm -O- -q | grep 'var wan_ip' this (after the grep) produces a line like var wan_ip="118.90.18.201"; note the password is sent in a HTTP POST to a url different to that which returns the ip address in this case there are no cookies involved, the router just trusts the ip address it got the login from for the next few minutes (it's possible that other routers may use cookies for this?) without being preceeded by the first request the second only produces the login page. there is no username only a password field called 'pws' there is provision to turn off the timeout of the login, but after the router is rebooted another login is needed, and that's typically when ddclient is most-needed too :( I tried the use=smc-barricade option but it didn't work for me. Looking at the source (I can almost read perl) all the firewall options seem to do single-stage web requests. This bug was reported in Debian. ---------------------------------------------------------------------- >Comment By: Marco Rodrigues (kmos) Date: 2009-02-20 11:04 Message: Bug report at http://bugs.debian.org/488107 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619494&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-20 11:04:57
|
Bugs item #2619494, was opened at 2009-02-20 10:59 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619494&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: current version Status: Open Resolution: None Priority: 5 Private: No Submitted By: Marco Rodrigues (kmos) Assigned to: wimpunk (wimpunk) Summary: my router has 2 stage login (SMC7904BRA2) Initial Comment: my router (a SMC7904bra2) requires a login request be made before it will release the IP address. eg: wget http://192.168.2.1/cgi-bin/login.exe --post-data=pws=smcadmin -O- &> /dev/null wget http://192.168.2.1/status_main.stm -O- -q | grep 'var wan_ip' this (after the grep) produces a line like var wan_ip="118.90.18.201"; note the password is sent in a HTTP POST to a url different to that which returns the ip address in this case there are no cookies involved, the router just trusts the ip address it got the login from for the next few minutes (it's possible that other routers may use cookies for this?) without being preceeded by the first request the second only produces the login page. there is no username only a password field called 'pws' there is provision to turn off the timeout of the login, but after the router is rebooted another login is needed, and that's typically when ddclient is most-needed too :( I tried the use=smc-barricade option but it didn't work for me. Looking at the source (I can almost read perl) all the firewall options seem to do single-stage web requests. This bug was reported in Debian. ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2009-02-20 11:04 Message: Marco, is this really your bug or did you forwarded it from somewhere? If not, please post a link to the original bugreport. ---------------------------------------------------------------------- Comment By: Marco Rodrigues (kmos) Date: 2009-02-20 11:04 Message: Bug report at http://bugs.debian.org/488107 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619494&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-20 11:04:28
|
Bugs item #2619505, was opened at 2009-02-20 11:04 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=2619505&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: current version Status: Open Resolution: None Priority: 5 Private: No Submitted By: Marco Rodrigues (kmos) Assigned to: Nobody/Anonymous (nobody) Summary: update interval 5min causes ban at dyndns Initial Comment: DESCRIPTION Setting update interval to "5m" causes dydns provider to ban the host. SUGGESTION Please iplement safeguard so that too low update intervals are: 1) either not accepted (print error message) 2) automatically scale the interval up to the safe limit and print warning. In dyndns.org case that'd be 7 minutes. This bug was reported in Debian - http://bugs.debian.org/489997 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619505&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-20 10:59:35
|
Bugs item #2619494, was opened at 2009-02-20 10:59 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=2619494&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: current version Status: Open Resolution: None Priority: 5 Private: No Submitted By: Marco Rodrigues (kmos) Assigned to: wimpunk (wimpunk) Summary: my router has 2 stage login (SMC7904BRA2) Initial Comment: my router (a SMC7904bra2) requires a login request be made before it will release the IP address. eg: wget http://192.168.2.1/cgi-bin/login.exe --post-data=pws=smcadmin -O- &> /dev/null wget http://192.168.2.1/status_main.stm -O- -q | grep 'var wan_ip' this (after the grep) produces a line like var wan_ip="118.90.18.201"; note the password is sent in a HTTP POST to a url different to that which returns the ip address in this case there are no cookies involved, the router just trusts the ip address it got the login from for the next few minutes (it's possible that other routers may use cookies for this?) without being preceeded by the first request the second only produces the login page. there is no username only a password field called 'pws' there is provision to turn off the timeout of the login, but after the router is rebooted another login is needed, and that's typically when ddclient is most-needed too :( I tried the use=smc-barricade option but it didn't work for me. Looking at the source (I can almost read perl) all the firewall options seem to do single-stage web requests. This bug was reported in Debian. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2619494&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-13 17:13:46
|
Patches item #2113616, was opened at 2008-09-16 01:11 Message generated for change (Comment added) made by jfurtner You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2113616&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: new services Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jamie Furtner (jfurtner) Assigned to: Nobody/Anonymous (nobody) Summary: EditDNS service Initial Comment: This patch implements DynDNS service for EditDNS (www.editdns.net). No external libraries are required. The EditDNS server does not support SSL so the patch currently disables SSL before making its request and then restores it afterwords. As far as I could tell SSL is global and not specific to services. ---------------------------------------------------------------------- >Comment By: Jamie Furtner (jfurtner) Date: 2009-02-13 10:13 Message: File Added: ddclient-editdns.patch ---------------------------------------------------------------------- Comment By: Jamie Furtner (jfurtner) Date: 2008-09-16 11:05 Message: Updated version of the diff File Added: ddclient-editdns.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2113616&group_id=116817 |
|
From: SourceForge.net <no...@so...> - 2009-02-02 16:59:45
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6328408 By: xeke I figured it out over the weekend. It was just tough getting the right URL because you never get to see it in the browser. Lots of "View Page Source" was required to decipher all the frames. Thanks for the reply, though. ______________________________________________________________________ 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...> - 2009-02-02 16:42:03
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6328292 By: wimpunk Try to find the page on the router which gives you the WAN IP address. Post the html-code on pastebin (http://ddclient.pastebin.ca/) and put a link to your post 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...> - 2009-02-02 13:53:27
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6327052 By: wimpunk As I wrote before: I'll take a closer look to the patch and maybe I will apply it. I would do more effort if they would offer free accounts. And maybe we would really hurry up if they would pay for it. ______________________________________________________________________ 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...> - 2009-02-02 13:40:31
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6326973 By: thericker Can you implement eNom into ddclient properly? Their system has over 11 million domains. ______________________________________________________________________ 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...> - 2009-01-31 11:13:36
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6309617 By: wimpunk I'll take a closer look to the patch and maybe I will apply it. After taking a quick look, I'm not really happy with the way the patch introduces the T_DOMAIN. ______________________________________________________________________ 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...> - 2009-01-31 09:54:10
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6309119 By: thericker Can this patch get added into the next release? ______________________________________________________________________ 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...> - 2009-01-30 19:46:12
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6302369 By: tolboom got it :-) Downloaded the patch from https://sourceforge.net/tracker/index.php?func=detail&aid=1556605&group_id=11681 7&atid=676130 Installed the program "patch" --> sudo apt-get install patch Then run the program patch to update your ddclient > patch < "downloaded file" You might get the question which file you want to patch --> /usr/sbin/ddclient Final step is to update you ddclient.conf file: # Configuration file for ddclient # /etc/ddclient.conf login=YourDomain protocol=enom password=YourPassword use=web domain=YourDomain server=dynamic.name-services.com. protocol=enom www To force the running and get proof for a working update type: > sudo ddclient -force -verbose|more Good luck ______________________________________________________________________ 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...> - 2009-01-30 16:38:58
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6300967 By: tolboom Hello, There is a patch to get ddclient working with eNom: https://sourceforge.net/tracker/index.php?func=detail&aid=1556605&group_id=11681 7&atid=676130 Can somebody tell me how I can install this 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=399428 |
1 message has been excluded from this view by a project administrator.
