ddclient-support Mailing List for ddclient (Page 17)
Brought to you by:
supersandro2000,
wimpunk
Menu
▾
▴
ddclient-support — Support for ddclient
This list is closed, nobody may subscribe to it.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2007 |
Jan
(2) |
Feb
(38) |
Mar
(13) |
Apr
(10) |
May
(30) |
Jun
(18) |
Jul
(17) |
Aug
(4) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
(2) |
Oct
(3) |
Nov
(1) |
Dec
|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
(9) |
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
(4) |
Jun
(9) |
Jul
(7) |
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(1) |
| 2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
(10) |
May
(9) |
Jun
(6) |
Jul
(7) |
Aug
(3) |
Sep
(4) |
Oct
(7) |
Nov
|
Dec
|
| 2015 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(1) |
Nov
(4) |
Dec
|
| 2017 |
Jan
|
Feb
(4) |
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
(8) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2018 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
(4) |
Jun
(1) |
Jul
(1) |
Aug
(3) |
Sep
(2) |
Oct
(3) |
Nov
|
Dec
(8) |
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(10) |
Sep
(10) |
Oct
(5) |
Nov
|
Dec
(2) |
| 2020 |
Jan
(3) |
Feb
(1) |
Mar
(3) |
Apr
(2) |
May
(47) |
Jun
(99) |
Jul
(14) |
Aug
(2) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ian T. <ia...@ti...> - 2007-08-05 13:36:52
|
Thank-you Ian On 05/08/07, wimpunk <wi...@us...> wrote: > > On 8/3/07, Ian <its...@gm...> wrote: > > I got this yesterday. I haven't had trouble like this before, but I'm > new > > to Debian so something has escaped me. > > > > root@weasles-ripped-flesh # uname -a > > Linux weasles-ripped-flesh 2.6.19 #7 SMP PREEMPT Sun Dec 17 22:01:07 CET > > 2006 i686 GNU/Linux > > > <snip> > > > > Here are the contents of my /etc/ddclient.conf. I've changed the > refresh > > from 300 to 600 seconds, but that seems not to have had an effect. I'm > > restricted to a dial up connecton here. Can someone please point out > how my > > configuration is causing me trouble? > > > > root@weasles-ripped-flesh:/var/mail# cat /etc/ddclient.conf > > The most recent version of ddclient has its configuration in > /etc/ddclient/ddclient.conf. Are you sure you're looking at the > correct one? > Try running ddclient -daemon=0 -debug -verbose -noquiet and check the > output. If you don't find a solution, post your config on > http://ddclient.pastebin.co.uk and create an another post on pastebin > with the results of the previous command. Don't forget to post the > urls to the list. > > Kind regards, > > wimpunk. > -- > I would love to change the world, but they wont give me the source code. > |
|
From: Ian <its...@gm...> - 2007-08-03 17:37:29
|
I got this yesterday. I haven't had trouble like this before, but I'm new to Debian so something has escaped me. root@weasles-ripped-flesh # uname -a Linux weasles-ripped-flesh 2.6.19 #7 SMP PREEMPT Sun Dec 17 22:01:07 CET 2006 i686 GNU/Linux ============ Dear Valued Customer: The hostname, ####.####-####.net, in account ######, has been blocked for abuse. This action has been taken due to the receipt of multiple updates originating from the same IP address. Updates which result in no change to the host are abusive. Please take a moment to review our Update Abuse Policy here: http://www.dyndns.com/support/abuse.html It is vital that you correct the problem which is resulting in these repeated and unnecessary updates. Once you have corrected this problem, you may request that the host be unblocked at the following URL: https://www.dyndns.com/+dyndns/#####.####-###.net<https://www.dyndns.com/+dyndns/clocker.kicks-ass.net> Please contact su...@dy... if you have questions, queries, or comments regarding this issue. Sincerely, The DynDNS Team ======== When I check #ps aux |less for more than one version of ddclient running, I see only one like this: root 22782 0.0 1.2 9176 6636 ttyp0 S 12:03 0:00 ddclient - sleeping for 280 seconds ======== Here are the contents of my /etc/ddclient.conf. I've changed the refresh from 300 to 600 seconds, but that seems not to have had an effect. I'm restricted to a dial up connecton here. Can someone please point out how my configuration is causing me trouble? root@weasles-ripped-flesh:/var/mail# cat /etc/ddclient.conf <snip> ###################################################################### daemon=600 # check every 300 seconds syslog=yes # log update msgs to syslog mail=root # mail all msgs to root mail-failure=root # mail failed update msgs to root pid=/var/run/ddclient.pid # record PID in file. ssl=yes # use ssl-support. Works with # ssl-library # #use=watchguard-soho, fw=192.168.111.1:80 # via Watchguard's SOHO FW #use=netopia-r910, fw=192.168.111.1:80 # via Netopia R910 FW #use=smc-barricade, fw=192.168.123.254:80 # via SMC's Barricade FW #use=netgear-rt3xx, fw=192.168.0.1:80 # via Netgear's internet FW #use=linksys, fw=192.168.1.1:80 # via Linksys's internet FW #use=maxgate-ugate3x00, fw=192.168.0.1:80 # via MaxGate's UGATE-3x00 FW #use=elsa-lancom-dsl10, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router #use=elsa-lancom-dsl10-ch01, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router #use=elsa-lancom-dsl10-ch02, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router #use=alcatel-stp, fw=10.0.0.138:80 # via Alcatel Speed Touch Pro #use=xsense-aero, fw=192.168.1.1:80 # via Xsense Aero Router #use=allnet-1298, fw=192.168.1.1:80 # via AllNet 1298 DSL Router #use=3com-oc-remote812, fw=192.168.0.254:80 # via 3com OfficeConnect Remote 812 #use=e-tech, fw=192.168.1.1:80 # via E-tech Router #use=cayman-3220h, fw=192.168.0.1:1080 # via Cayman 3220-H DSL Router # #fw-login=admin, fw-password=XXXXXX # FW login and password # ## To obtain an IP address from FW status page (using fw-login, fw-password) #use=fw, fw=192.168.1.254/status.htm, fw-skip='IP Address' # found after IP Address # ## To obtain an IP address from Web status page (using the proxy if defined) #use=web, web=checkip.dyndns.org/, web-skip='IP Address' # found after IP Address # #use=ip, ip=127.0.0.1 # via static IP's #use=if, if=eth0 # via interfaces #use=web # via web use=web # via web # #protocol=dyndns2 # default protocol protocol=dyndns2 # default protocol #proxy=fasthttp.sympatico.ca:80 # default proxy #server=members.dyndns.org # default server server=members.dyndns.org # default server #server=members.dyndns.org:8245 # default server (bypassing proxies) #login=your-login # default login login=###### # default login #password=test # default password password=####### # default password #mx=mx.for.your.host # default MX #backupmx=yes|no # host is primary MX? #wildcard=yes|no # add wildcard CNAME? ## ## dyndns.org dynamic addresses ## ## (supports variables: wildcard,mx,backupmx) ## # server=members.dyndns.org, \ # protocol=dyndns2 \ # your-dynamic-host.dyndns.org server=members.dyndns.org, \ protocol=dyndns2 \ my_virtual_host_name.net ## ## dyndns.org static addresses ## ## (supports variables: wildcard,mx,backupmx) ## # static=yes, \ # server=members.dyndns.org, \ # protocol=dyndns2 \ # your-static-host.dyndns.org ## ## ## dyndns.org custom addresses ## ## (supports variables: wildcard,mx,backupmx) ## # custom=yes, \ # server=members.dyndns.org, \ # protocol=dyndns2 \ # your-domain.top-level,your-other-domain.top-level <snip> <snip> I don't know how to prove the problem is occuring except by the blocking by DynDNS and that isn't satisfactory. Continuing to abuse the privilage of the service for the sake of testing seems lame. Any ideas how I might otherwise do my testing would be appreciated. ======= My mail is still full of messages from ddclient and I've tried restarting it. The mail looks like the following; root@weasles-ripped-flesh:/var/mail# mail Mail version 8.1.2 01/15/2001. Type ? for help. "/var/mail/root": 33 messages 4 new 33 unread U 1 root@Knoppix Thu Aug 2 22:33 23/709 status report from ddclient@weasles-ripped-flesh U 2 root@Knoppix Thu Aug 2 22:43 23/709 status report from ddclient@weasles-ripped-flesh U 3 root@Knoppix Thu Aug 2 22:45 21/492 status report from ddclient@weasles-ripped-flesh U 4 root@Knoppix Thu Aug 2 22:45 21/492 status report from ddclient@weasles-ripped-flesh U 5 root@Knoppix Fri Aug 3 09:23 21/568 status report from ddclient@weasles-ripped-flesh U 6 root@Knoppix Fri Aug 3 09:57 21/624 status report from ddclient@weasles-ripped-flesh U 7 root@Knoppix Fri Aug 3 09:58 23/709 status report from ddclient@weasles-ripped-flesh U 8 root@Knoppix Fri Aug 3 10:03 23/709 status report from ddclient@weasles-ripped-flesh U 9 root@Knoppix Fri Aug 3 10:08 23/709 status report from ddclient@weasles-ripped-flesh U 10 root@Knoppix Fri Aug 3 10:13 23/709 status report from ddclient@weasles-ripped-flesh U 11 root@Knoppix Fri Aug 3 10:18 23/709 status report from ddclient@weasles-ripped-flesh U 12 root@Knoppix Fri Aug 3 10:23 23/709 status report from ddclient@weasles-ripped-flesh U 13 root@Knoppix Fri Aug 3 10:28 23/709 status report from ddclient@weasles-ripped-flesh U 14 root@Knoppix Fri Aug 3 10:33 23/709 status report from ddclient@weasles-ripped-flesh U 15 root@Knoppix Fri Aug 3 10:38 23/709 status report from ddclient@weasles-ripped-flesh U 16 root@Knoppix Fri Aug 3 10:43 23/709 status report from ddclient@weasles-ripped-flesh U 17 root@Knoppix Fri Aug 3 10:48 23/709 status report from ddclient@weasles-ripped-flesh U 18 root@Knoppix Fri Aug 3 10:53 23/709 status report from ddclient@weasles-ripped-flesh U 19 root@Knoppix Fri Aug 3 10:58 23/709 status report from ddclient@weasles-ripped-flesh U 20 root@Knoppix Fri Aug 3 11:03 21/624 status report from ddclient@weasles-ripped-flesh U 21 root@Knoppix Fri Aug 3 11:07 23/709 status report from ddclient@weasles-ripped-flesh U 22 root@Knoppix Fri Aug 3 11:12 23/709 status report from ddclient@weasles-ripped-flesh U 23 root@Knoppix Fri Aug 3 11:27 21/492 status report from ddclient@weasles-ripped-flesh U 24 root@Knoppix Fri Aug 3 11:27 21/492 status report from ddclient@weasles-ripped-flesh U 25 root@Knoppix Fri Aug 3 11:42 21/568 status report from ddclient@weasles-ripped-flesh U 26 root@Knoppix Fri Aug 3 11:43 21/624 status report from ddclient@weasles-ripped-flesh U 27 root@Knoppix Fri Aug 3 11:44 23/710 status report from ddclient@weasles-ripped-flesh U 28 root@Knoppix Fri Aug 3 11:49 23/710 status report from ddclient@weasles-ripped-flesh U 29 root@Knoppix Fri Aug 3 11:54 23/710 status report from ddclient@weasles-ripped-flesh >N 30 root@Knoppix Fri Aug 3 11:59 22/700 status report from ddclient@weasles-ripped-flesh N 31 root@Knoppix Fri Aug 3 12:03 20/482 status report from ddclient@weasles-ripped-flesh N 32 root@Knoppix Fri Aug 3 12:03 20/614 status report from ddclient@weasles-ripped-flesh & 1 Message 1: >From root@Knoppix Thu Aug 2 22:33:16 2007 Date: Thu, 2 Aug 2007 22:33:16 -0400 (EDT) From: root@Knoppix (root) To: root@Knoppix Subject: status report from ddclient@weasles-ripped-flesh WARNING: skipping update of clocker.kicks-ass.net from 205.200.47.254 to 205.200.47.84. WARNING: last updated Thu Aug 2 09:55:54 2007 but last attempt on Thu Aug 2 22:31:54 2007 failed. WARNING: Wait at least 5 minutes between update attempts. regards, ddclient@weasles-ripped-flesh (version 3.7.0) Message 5: >From root@Knoppix Fri Aug 3 09:23:03 2007 Date: Fri, 3 Aug 2007 09:23:03 -0400 (EDT) From: root@Knoppix (root) To: root@Knoppix Subject: status report from ddclient@weasles-ripped-flesh Message 6: >From root@Knoppix Fri Aug 3 09:57:44 2007 Date: Fri, 3 Aug 2007 09:57:44 -0400 (EDT) From: root@Knoppix (root) To: root@Knoppix Subject: status report from ddclient@weasles-ripped-flesh FAILED: updating clocker.kicks-ass.net: abuse: The hostname specified is blocked for abuse; fill in the form at http://support.dyndns.org/abuse.phpto be unblocked regards, ddclient@weasles-ripped-flesh (version 3.7.0) WARNING: cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.org Message 32: >From root@Knoppix Fri Aug 3 12:03:48 2007 Date: Fri, 3 Aug 2007 12:03:47 -0400 (EDT) From: root@Knoppix (root) To: root@Knoppix Subject: status report from ddclient@weasles-ripped-flesh FAILED: updating clocker.kicks-ass.net: abuse: The hostname specified is blocked for abuse; fill in the form at http://support.dyndns.org/abuse.phpto be unblocked regards, ddclient@weasles-ripped-flesh (version 3.7.0) ============= Thanks very much for wading through all this. Ian |
|
From: Wim V. <wi...@gm...> - 2007-07-27 08:44:11
|
Oops, mail should go to the mailing list. ---------- Forwarded message ---------- From: wimpunk <wi...@us...> Date: Jul 27, 2007 10:43 AM Subject: Re: [Ddclient-support] ddclient in Astaro Security Gateway To: Ingo Schwarze <isc...@as...> Hi, On 7/26/07, Ingo Schwarze <isc...@as...> wrote: > Hi, > > Astaro management just decided that, in the future, ddclient will be > shipped as the dynamic DNS update client in the Astaro Security Gateway. > See http://www.astaro.com/ for more information about this product > family. The decision was made based on a recommendation by dyndns.com. > > For that reason, i just implemented ddclient support in the Astaro > Security Gateway. If QA testing goes well, ddclient 3.7.2 will ship > with the Astaro Security Gateway 7.100 later this year. Very probably, > i shall be maintaining ddclient/ASG integration in the future, too. > Of course, i shall feed back any observations to your project. > Thanks for using us project. I'm hoping to release 3.7.3 pretty soon. It has a few nice patches so maybe you could ship that one. > While checking available dynamic DNS providers, i came across the > following points in ddclient --help: > > (1) The service provided by za.net appears to be at www.dyndns.za.net, > not at www.dydns.za.net. The string "www.dydns.za.net" appears > twice in the file "ddclient". > > (2) As far as i understand, za.net no more uses concont, but they > rather use gnudip now. > I'll take a closer look to this. > (3) ddclient --help says: > The 'dnspark' protocol is used by DNS service offered by > www.dnspark.com. Configuration variables applicable to > the 'easydns' protocol are... > That should probably be 'dnspark' in the last line. > > (4) ddclient --help says: > protocol=hammernode1 ## > server=fqdn.of.service ## defaults to members.dyndns.org > That should probably read 'dup.hn.org' in the comment? Could you send us a patch for these typo's? It's easier to apply for me. > > (5) According to my tests, www.hn.org and dup.hn.org can no more > be reached: > $ dig dup.hn.org > ; <<>> DiG 9.3.4 <<>> dup.hn.org > ;; global options: printcmd > ;; connection timed out; no servers could be reached As previous discussed with the ubuntu maintainer: it's still there for historical reasons. > > (6) ddclient --help says: > The 'namecheap' protocol is used by DNS service offered by > www.namecheap.com. Configuration variables applicable to > the 'easydns' protocol are: > Once more, that should probably read 'namecheap', not 'easydns'? > Ooops, this seems already fixed in SVN, ddclient rev. 61. The ubuntu maintainer has send us a few typo patches. :-) > > Besides, a few times, i found the following in the logs: > Use of uninitialized value in string ne at /usr/sbin/ddclient line 1966. > I shall investigate more closely when i find time. That would be nice. > > In any case, thanks for working on ddclient! > > Yours, > Ingo > > -- > Ingo Schwarze <isc...@as...> | Software Engineer | Framework Team > Astaro AG | www.astaro.com | 76227 Karlsruhe | Germany > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Ddclient-support mailing list > Ddc...@li... > https://lists.sourceforge.net/lists/listinfo/ddclient-support > -- I would love to change the world, but they wont give me the source code. -- I would love to change the world, but they wont give me the source code. |
|
From: Ingo S. <isc...@as...> - 2007-07-26 16:08:59
|
Hi, Astaro management just decided that, in the future, ddclient will be shipped as the dynamic DNS update client in the Astaro Security Gateway. See http://www.astaro.com/ for more information about this product family. The decision was made based on a recommendation by dyndns.com. For that reason, i just implemented ddclient support in the Astaro Security Gateway. If QA testing goes well, ddclient 3.7.2 will ship with the Astaro Security Gateway 7.100 later this year. Very probably, i shall be maintaining ddclient/ASG integration in the future, too. Of course, i shall feed back any observations to your project. While checking available dynamic DNS providers, i came across the following points in ddclient --help: (1) The service provided by za.net appears to be at www.dyndns.za.net, not at www.dydns.za.net. The string "www.dydns.za.net" appears twice in the file "ddclient". (2) As far as i understand, za.net no more uses concont, but they rather use gnudip now. (3) ddclient --help says: The 'dnspark' protocol is used by DNS service offered by www.dnspark.com. Configuration variables applicable to the 'easydns' protocol are... That should probably be 'dnspark' in the last line. (4) ddclient --help says: protocol=hammernode1 ## server=fqdn.of.service ## defaults to members.dyndns.org That should probably read 'dup.hn.org' in the comment? (5) According to my tests, www.hn.org and dup.hn.org can no more be reached: $ dig dup.hn.org ; <<>> DiG 9.3.4 <<>> dup.hn.org ;; global options: printcmd ;; connection timed out; no servers could be reached (6) ddclient --help says: The 'namecheap' protocol is used by DNS service offered by www.namecheap.com. Configuration variables applicable to the 'easydns' protocol are: Once more, that should probably read 'namecheap', not 'easydns'? Ooops, this seems already fixed in SVN, ddclient rev. 61. Besides, a few times, i found the following in the logs: Use of uninitialized value in string ne at /usr/sbin/ddclient line 1966. I shall investigate more closely when i find time. In any case, thanks for working on ddclient! Yours, Ingo -- Ingo Schwarze <isc...@as...> | Software Engineer | Framework Team Astaro AG | www.astaro.com | 76227 Karlsruhe | Germany |
|
From: SourceForge.net <no...@so...> - 2007-07-18 13:55:39
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4419810 By: wimpunk Try to configure your mail and or syslog correctly. You wrote before that the system is working when using the commandline. Configure ddclient for using syslog and/or mail and try it from the commandline. Add the verbose option to make sure ddclient will tell you at least something. ______________________________________________________________________ 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-07-18 13:00:55
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4419699 By: alessiocesar Thanks for your reply... I tried both the packaged version of ddclient (ddclient-3.7.1-1.el5.rf.noarch.rpm) and the one from the ddclient website (ddclient-3.7.2.tar)...Same result... Funny thing is that I do ps -ef | grep "ddclient" continuosly and I see it going like this: [root@Linux DL]# ps -ef | grep "ddclient" root 3923 1 0 00:04 ? 00:00:05 ddclient - sleeping for 60 seconds .... [root@Linux DL]# ps -ef | grep "ddclient" root 3923 1 0 00:04 ? 00:00:05 ddclient - sleeping for 20 seconds ... root 3923 1 0 00:04 ? 00:00:05 ddclient - sleeping for 10 seconds [root@Linux DL]# ps -ef | grep "ddclient" root 3923 1 0 00:04 ? 00:00:05 ddclient - connecting to checkip.dyndns.org port 80 then again root 3923 1 0 00:04 ? 00:00:05 ddclient - sleeping for 60 seconds all this w/o seeing anything in /var/log/messages Someone please put me out of my misery? Thanks, AC ______________________________________________________________________ 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-07-18 08:32:46
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4419346 By: wimpunk I forgot to answer your wildcard question. It refers to an available feature at dyndns. Check https://www.dyndns.com/services/dns/dyndns/features.html point 2: Ability to create wildcards such as *.yourhost.dyndns.org that points to yourhost.dyndns.org ______________________________________________________________________ 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-07-18 08:17:44
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4419320 By: wimpunk First, which version of ddclient are you using? Is it a packaged version of ddclient or did you get it from the ddclient website? Check your log or mail, there must be a clue somewhere. ______________________________________________________________________ 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-07-17 21:37:58
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4418796 By: alessiocesar Guys, I need some help here please. I run RedHat Enterprise Linux 5 and installed ddclient by following the instructions... I can start it manually: root@Linux ddclient]# service ddclient restart Shutting down ddclient: [ OK ] Starting ddclient: [ OK ] I see it running, counting down to 0 sec: [root@Linux ddclient]# ps -ef | grep "ddclient" root 3700 1 0 17:20 pts/1 00:00:00 ddclient - sleeping for 270 seconds root 3704 2579 0 17:21 pts/1 00:00:00 grep ddclient but when it reaches 0 nothing happens... If I run ddclient -verbose -daemon=0 it does the trick... [root@Linux ddclient]# chkconfig ddclient --list ddclient 0:off 1:off 2:on 3:on 4:on 5:on 6:off I also did this as it was never created by the system: [root@Linux ~]# touch /etc/ddclient/ddclient.cache You have new mail in /var/spool/mail/root [root@Linux ~]# chmod 660 /etc/ddclient/ddclient.cache It seems that it never writes to this cache file.. /etc/ddclient/ddclient.conf is: # Basic configuration file for ddclient # # /etc/ddclient.conf daemon=300 pid=/var/run/ddclient.pid use=web, web=checkip.dyndns.com/, web-skip='IP Address' login=mylogin password=mypasswd protocol=dyndns2 server=members.dyndns.org wildcard=YES Also what is the wildcard doing here really? Please help! Thanks, AC ______________________________________________________________________ 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-07-16 16:28:37
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4415156 By: mlnutt An error on my part: ddclient doesn't, as I state, use the server's LAN IP for the update. What is happening is that the router returns a page indicating the IP of the machine that is managing the router. An error on ddclient's part: The $reply variable isn't validated for the content of the $skip variable. This string should be matched and if not found in $reply then no IP string should be parsed from $reply. ______________________________________________________________________ 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-07-16 16:04:58
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4415132 By: mlnutt A good router *should* lock out other machines if it is currently being administered; that, makes total sense. Only in this way can an administer be assured that the configuration they are viewing is the one being used. The code for logging out (at least for my router NetGear wgt624) is simple to implement. In get_ip(), after the geturl() call to obtain the IP is made I request my router's logout page '/LGO_logout.htm' if ($url) { $reply = geturl('', $url, opt('fw-login'), opt('fw-password')) || ''; geturl('', 'http://' . opt('fw') . '/LGO_logout.htm', opt('fw-login'), opt('fw-password')); } } It would be easy to add another field to the %builtinfw array of structures to accommodate logging out. e.g., 'netgear-wgt624' => { 'name' => 'Netgear WGT624', 'url' => '/RST_st_dhcp.htm', 'skip' => 'IP Address</B></td><TD NOWRAP width="50%">', 'logout' => '/LGO_logout.htm', }, and then the above call to logout could be reworked to if ($reply && $logout) geturl('', 'http://' . opt('fw') . $logout, opt('fw-login'), opt('fw-password')); where, of course, $logout has been instantiated to the corresponding 'logout' field for the user selected %builtinfw. Now, as to my second point. If ddclient fails for some reason to obtain the IP from the router (or any other method) the default behavior is to use the LAN IP of the server itself. This behavior is wrong and should not be performed. ddclient should not attempt to perform an update in this case. The server' LAN IP is not the server's internet IP; if it is you probably don't need ddclient. The option of allowing the user to select multiple IP grabbing strategies is to ensure that all possible options for obtaining the internet IP are exhausted before failing. This is not a complex task. Method 1 fails, try method 2, etc. After all, the point of ddclient is to update the internet IP so that your server is accessible to the outside world reliably. Let's say that "http://checkip.dyndns.org/" is for some reason off-line, if we can check our IP from "http://ipdetect.dnspark.com/" shouldn't we do so? I don't know about you but I want my server to be on-line as much as possible. Ideally, I'd like to first try and get the IP from my router. If this fails, then secondarily get the IP from a web source. And thirdly if both those attempts fail then to perform an external command such as 'host mydomainname.com' to get the IP. If all these methods fail then do nothing but issue an alert and try again later. Perhaps try a bit sooner than the specified update checking interval because we want the server on-line as soon as possible. None of this is complex or difficult to implement. ______________________________________________________________________ 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-07-16 10:25:59
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4414620 By: wimpunk I don't have such a router so either some has to send me one or send me the code how to handle it. Personally I even should not buy such a router, it sounds like a lot of problems. Your problem could probably be fixed if you look at the result of what the router replies when there's already someone logged in. I guess your configuration isn't correct for such a situation. Your suggestion on what you think you needs seems to complex for me. I really suggest you buy a good router which handles everything like it has to. Kind regards, 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=467339 |
|
From: SourceForge.net <no...@so...> - 2007-07-15 16:22:11
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4413718 By: mlnutt I too would like a router logout feature. I've hard coded one into the ddclient script specifically for my router so that my server doesn't lock out router administration from other machines. What I noticed in testing this is that if the router is being administered by another machine and thus the server employing ddclient can not yank the IP then ddclient defers to the server (LAN) IP and uses it for the update. That is to say, if ddclient can't get the IP from the router it uses the server machine IP (i.e., 192.168.0.2). This is surely wrong. What I believe is needed is the ability to specify a secondary (and perhaps ternary) means for obtaining the IP should the primary scheme fail. For instance, if I can't get my IP from my router then I'd like to fetch it from a web check but never, never, never, from the host machine. The default behavior should be for ddclient to fail if the explicitly specified method(s) are unable to obtain the 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=467339 |
|
From: SourceForge.net <no...@so...> - 2007-07-10 21:36:17
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4406587 By: kmos This needs login and password to get this output.. URL 192.168.1.1/status.html HTTP/1.1 200 OK Server: Unknown/0.0 UPnP/1.0 Conexant-EmWeb/R6_1_0 Connection: close Content-Type: text/html Expires: Thu, 01 Jan 1970 00:00:00 GMT Cache-Control: no-cache Pragma: no-cache WAN Status PPPoE Connection: Connection established Connected time so far: 03:15:56s WAN IP Address: 84.18.249.86 WAN Subnet Mask: 255.255.255.255 IP Address Type: PPP Default Gateway: 0.0.0.0 Primary DNS: 212.13.35.189 Secondary DNS: 212.13.35.33 LAN Status Local IP Address: 192.168.1.1 LAN Subnet Mask: 255.255.255.0 Act as Local DHCP Server: Yes MAC Address: 00:0F:E2:1B:E6:BB Software Status Up-Time: 03:17:44s Current Time: Version: DR814QV200R010P01 Compile Time: Jul 21 2006 14:27:56 Vendor: Huawei <http://aolynk.huawei-3com.com/> Copyright (c) 2003-2006 Huawei Technologies Co., Ltd. All rights Reserved ______________________________________________________________________ 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-07-03 21:19:51
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4394960 By: wimpunk Note for others out there: this is only true for the current ubuntu package. Contact kmos for more info. ______________________________________________________________________ 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-07-03 21:17:32
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4394957 By: kmos 2- It will read the /etc/ddclient.conf by default. ______________________________________________________________________ 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-07-03 12:53:09
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4394008 By: wimpunk 2. ubuntu related. The package maintainer doesn't want to move the config to the correct location /etc/ddclient/ddclient.conf. Ask him about how it works 3. no ______________________________________________________________________ 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-07-03 12:35:41
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4393986 By: hinsen3 i found the output in /var/log/syslog ;) what about question 2 and 3? ______________________________________________________________________ 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-07-03 12:16:59
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4393947 By: hinsen3 hi. 1. i started ddclient with /usr/sbin/ddclient daemon 600 -syslog -verbose -debug but i still dont see any log information in /var/log/messages. Why? (syslogd is running on my ubuntu) 2. Do i have to execute /usr/sbin/ddclient with -file /etc/ddclient.conf or is this a default value? 3. Is there a difference between calling ddclient with parameter -syslog OR calling ddclient without the parameter but /etc/ddclient.conf contains syslog=yes ? thanks... ______________________________________________________________________ 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: wimpunk <wi...@us...> - 2007-06-30 22:00:12
|
This way I would like to announce the availability of the mailinglist on gmane. You can find it as the gmane.network.dns.ddclient newsgroup. wimpunk. |
|
From: SourceForge.net <no...@so...> - 2007-06-30 17:10:20
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4389601 By: wimpunk It would be nicer if you could post your patch to the patches section... ______________________________________________________________________ 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-06-19 14:54:37
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4369711 By: s-sakamoto Paste: 'webcaster' => { 'name' => 'Web Caster V110', 'url' => '/cgi-bin/paractl.cgi?st_state', 'skip' => 'WAN.*?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=467339 |
|
From: SourceForge.net <no...@so...> - 2007-06-19 14:52:55
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4369705 By: s-sakamoto Paste: 'aterm' => { 'name' => 'Aterm DR606CV', 'url' => '/info_main.html', 'skip' => 'WAN', }, ______________________________________________________________________ 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-06-19 08:37:01
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4369183 By: wimpunk Thank you for the feedback. 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...> - 2007-06-19 07:52:00
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4369121 By: filwud hi just info for anyone wanting to use this on trustix, i use 3.05 b i used the sample redhat rc.d script but trustix init.d is in /etc not /etc/rc.d so changed . /etc/rc.d/init.d/functions to . /etc/init.d/functions config is this, i used the netgear modem already in the client. and zoneedit. i also had to install the perl IO::Socket::SSL module use=netgear-dg834g, fw=192.168.0.1:80 fw-login=#####, fw-password=##### # FW login and password ## ## ZoneEdit (zoneedit.com) ## server=www.zoneedit.com, \ protocol=zoneedit1, \ login=#####, \ password=##### \ www.????.co.uk,????.co.uk also had to make the /var/cache/ddclient directory as mentioned before running well and updated my zoneedit dns 4 times in the last 3 days with no problems SUCCESS: updating ????.co.uk: IP address set to 81.77.xxx.132 (201: No records need updating.) SUCCESS: updating www.????.co.uk: IP address set to 81.77.xxx.132 (201: No records need updating.) hope this helps anyone struggling with trustix. great tool thanks filwud ______________________________________________________________________ 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 |
7 messages has been excluded from this view by a project administrator.
