ddclient-support — Support for ddclient

Re: [Ddclient-support] 'Run as' ddclient and Multiple Interfaces

[<ca...@qu...>]

Thanks.


On 11/23/2016 11:02 PM, wimpunk wrote:
> Hi,
>
> On 24/11/16 06:03, ca...@qu... wrote:
>> Maybe I'm wrong but I thought I'd read somewhere that after the ddclient
>> daemon starts, it's supposed to change from user root to ddclient.  But
>> it's not.  And I'm not finding the code in the script to do that.  Am I
>> imagining things?
> No, it doesn't change the owner.  If you want ddclient to be started as
> a different user, you have to start it manually as a different user.  In
> most cases this is done by using `su` in the init-script.
Ok I've set it up in systemd like this and it works fine:
/usr/local/lib/systemd/system/dynamic-dns.service

[Unit]
Description = spdyn.de dynamic DNS update service
After = nss-lookup.target network.target dhcpcd.service

[Service]
Type = simple
User = ddclient
ExecStart = /usr/sbin/ddclient -foreground
Restart = on-failure

# Security
PrivateTmp=yes
InaccessibleDirectories=/boot /home/backups /home/sleeper /media /mnt
/opt /root /srv /sys
ReadOnlyDirectories=/bin /etc /lib /lib64 /sbin /usr/bin /usr/sbin
CapabilityBoundingSet=~CAP_SYS_PTRACE
NoNewPrivileges=yes

[Install]
WantedBy=multi-user.target


>> Also I have ddclient set to get the IP off the interface, but depending
>> on the phase of the moon, the humidity, and how much noise is in the
>> room, the interface can come up variously as eth0, eth1, or eth2.
>> (CentOS)  Is there any way to specify multiple interfaces in the config
>> file?
> Unfortunately there is no possibility to let ddclient choose the
> interface.  You could for example try to find out the correct interface
> and add it as a parameter on startup.
This is my router in a Xen virtual machine, so it has to be automatic.

How about if I make two stanzas like this?  Will it error out, or fail
gracefully, on the missing interface?

use=if,                     if=eth0
protocol=dyndns2
server=update.spdyn.de
login=dro...@pr...
password=iTsasecret
darkheart.spdns.org

use=if,                     if=eth1
protocol=dyndns2
server=update.spdyn.de
login=dro...@pr...
password=iTsasecret
darkheart.spdns.org


I find that in RHEL renaming interfacen thus is not reliable.  It does
not react predictably.  Did in Debian, but not RHEL, and this is coming
to Debian.

Re: [Ddclient-support] 'Run as' ddclient and Multiple Interfaces

[wimpunk <wi...@us...>]

Hi,

On 24/11/16 06:03, ca...@qu... wrote:
> Maybe I'm wrong but I thought I'd read somewhere that after the ddclient
> daemon starts, it's supposed to change from user root to ddclient.  But
> it's not.  And I'm not finding the code in the script to do that.  Am I
> imagining things?
> 

No, it doesn't change the owner.  If you want ddclient to be started as
a different user, you have to start it manually as a different user.  In
most cases this is done by using `su` in the init-script.

> Also I have ddclient set to get the IP off the interface, but depending
> on the phase of the moon, the humidity, and how much noise is in the
> room, the interface can come up variously as eth0, eth1, or eth2.
> (CentOS)  Is there any way to specify multiple interfaces in the config
> file?
> 

Unfortunately there is no possibility to let ddclient choose the
interface.  You could for example try to find out the correct interface
and add it as a parameter on startup.
At the other hand, you could try to find out if there's a way to get the
same interface name after every reboot.  On debian they fix this by
generating a persistent rule to udev. On my system it contains this:

# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# USB device 0x:0x (cdc_ether)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:1e:10:1f:00:00", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

so it links the mac-address to the device name.
On SuSE you can do the link based on the pci location.  I don't know how
they save it in udev, I just know it can be done through yast2.

I hope this info can help you.

Kind regards

wimpunk.

[Ddclient-support] 'Run as' ddclient and Multiple Interfaces

[<ca...@qu...>]

Maybe I'm wrong but I thought I'd read somewhere that after the ddclient
daemon starts, it's supposed to change from user root to ddclient.  But
it's not.  And I'm not finding the code in the script to do that.  Am I
imagining things?

Also I have ddclient set to get the IP off the interface, but depending
on the phase of the moon, the humidity, and how much noise is in the
room, the interface can come up variously as eth0, eth1, or eth2.
(CentOS)  Is there any way to specify multiple interfaces in the config
file?

[Ddclient-support] [wimpunk/ddclient] a78594: sample-etc_rc.d_init.d_ddclient.alpine: openrc use...

[GitHub <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/wimpunk/ddclient
  Commit: a785948800ccbfbb184ea77f124ec167030ff050
      https://github.com/wimpunk/ddclient/commit/a785948800ccbfbb184ea77f124ec167030ff050
  Author: Francesco Colista <fco...@al...>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M sample-etc_rc.d_init.d_ddclient.alpine

  Log Message:
  -----------
  sample-etc_rc.d_init.d_ddclient.alpine: openrc uses openrc-run now, runscript is obsolete


  Commit: a9240d00f5afc90feeeae0cd3a32751fbef33d8b
      https://github.com/wimpunk/ddclient/commit/a9240d00f5afc90feeeae0cd3a32751fbef33d8b
  Author: wimpunk <wi...@us...>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M sample-etc_rc.d_init.d_ddclient.alpine

  Log Message:
  -----------
  Merge pull request #46 from fcolista/master

sample-etc_rc.d_init.d_ddclient.alpine: openrc uses openrc-run now

Runscript is now absolute.  Pull request #46


Compare: https://github.com/wimpunk/ddclient/compare/a9ab60e7a16b...a9240d00f5af

[Ddclient-support] ddclient: how to log changes of IP address

[wimpunk <wi...@us...>]

This messages got posted to the mailing list a while ago but because
sender wasn't subscribed it got ignored.  I saw the sender subscribing
so here's a repost:
> 
> Hi,
> 
> I am running ddclient on my Debian server . It is connected to the network through ADSL modem that changes IP address once a day. I would like to log in the file all of IPs addresses that were used by my server.
> Is it possible with ddclient?
> 
> Thanks
> 
> Mariusz Bielawski

You can run a post-script with ddclient which saves the info in some
kind of database.  Or run a parser to go through your logging.

wimpunk.

[Ddclient-support] [wimpunk/ddclient] abb667: update sample config with functional cloudflare se...

[GitHub <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/wimpunk/ddclient
  Commit: abb6674d603d9a175093a80d651e4489d8713376
      https://github.com/wimpunk/ddclient/commit/abb6674d603d9a175093a80d651e4489d8713376
  Author: Ethan Setnik <es...@gm...>
  Date:   2016-09-08 (Thu, 08 Sep 2016)

  Changed paths:
    M sample-etc_ddclient.conf

  Log Message:
  -----------
  update sample config with functional cloudflare settings


  Commit: a9ab60e7a16bd266f61139eb3c38b1a26cee783d
      https://github.com/wimpunk/ddclient/commit/a9ab60e7a16bd266f61139eb3c38b1a26cee783d
  Author: wimpunk <wi...@us...>
  Date:   2016-09-08 (Thu, 08 Sep 2016)

  Changed paths:
    M sample-etc_ddclient.conf

  Log Message:
  -----------
  Merge pull request #44 from esetnik/cloudflare_config

Cloudflare Config fix from #44.

Specifying the `server` directive caused the Cloudflare protocol to use the wrong url when communicating with Cloudflare API v4. It works if the directive is removed.


Compare: https://github.com/wimpunk/ddclient/compare/df883fd0913c...a9ab60e7a16b

Re: [Ddclient-support] E-mail notifications

[wimpunk <wi...@us...>]

On 09/06/2016 10:28 AM, si...@ma... wrote:
> 
> Dear all.
> 
> I'm using ddclient (version 3.8.2), OS: Ubuntu 16.04.1 LTS.  And my question is about e-mail notifications.
> 
> In ddclient.conf there are two options for mail notification:
> # Mail all msgs to root.
> mail=root
> # Mail failed update msgs to root
> mail-failure=root
> 
> First one sends all notifications  (both "success" and "warning" messages) , second one only failure messages.
> 
> Unfortunately I receive a lot of warning notifications every day when my PC can't connect to server or something like this.
> But generally it doesn't affect IP updating, because daemon is configured to start update request every 300 sec and even it can't connect to the server once it will successfully connect to the server in 5-10 minutes without any issues and finally IP address will be changed. 
> 
> Now to avoid a lot of mails I just commented 
> #mail=root
> and able receive only "failure" notifications about real troubles with ddclient.
> 
> But I still want to receive messages about IP change.
> 
> Is it possible to somehow configure ddclient to receive only "success" and "failed" notifications and don't receive "warning" ones?
> 
> Thank you in advance.
> 

I'm sorry but currently there is no way to do this.  Feel free to
implement it. :-)

Kind regards,

wimpunk.

[Ddclient-support] E-mail notifications

[<si...@ma...>]

Dear all.

I'm using ddclient (version 3.8.2), OS: Ubuntu 16.04.1 LTS.  And my question is about e-mail notifications.

In ddclient.conf there are two options for mail notification:
# Mail all msgs to root.
mail=root
# Mail failed update msgs to root
mail-failure=root

First one sends all notifications  (both "success" and "warning" messages) , second one only failure messages.

Unfortunately I receive a lot of warning notifications every day when my PC can't connect to server or something like this.
But generally it doesn't affect IP updating, because daemon is configured to start update request every 300 sec and even it can't connect to the server once it will successfully connect to the server in 5-10 minutes without any issues and finally IP address will be changed. 

Now to avoid a lot of mails I just commented 
#mail=root
and able receive only "failure" notifications about real troubles with ddclient.

But I still want to receive messages about IP change.

Is it possible to somehow configure ddclient to receive only "success" and "failed" notifications and don't receive "warning" ones?

Thank you in advance.

-- 
sign .

[Ddclient-support] [wimpunk/ddclient] 1d848d: Merge pull request #1 from wimpunk/master

[GitHub <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/wimpunk/ddclient
  Commit: 1d848de60c070840c3ae0206ee880d33290977cb
      https://github.com/wimpunk/ddclient/commit/1d848de60c070840c3ae0206ee880d33290977cb
  Author: Harry-Xue <hel...@gm...>
  Date:   2016-05-24 (Tue, 24 May 2016)

  Changed paths:
    M COPYING
    M ChangeLog
    M Changelog.old
    M README.cisco
    M README.md
    M RELEASENOTE
    M ddclient
    M sample-etc_cron.d_ddclient
    M sample-etc_ddclient.conf
    M sample-etc_dhclient-exit-hooks
    M sample-etc_dhcpc_dhcpcd-eth0.exe
    M sample-etc_ppp_ip-up.local
    M sample-etc_rc.d_init.d_ddclient.lsb
    M sample-etc_rc.d_init.d_ddclient.redhat
    M sample-etc_rc.d_init.d_ddclient.ubuntu

  Log Message:
  -----------
  Merge pull request #1 from wimpunk/master

Catch up to wimpunk/ddclient


  Commit: 6c951a039543021295d9d809d7127ef06ccb1513
      https://github.com/wimpunk/ddclient/commit/6c951a039543021295d9d809d7127ef06ccb1513
  Author: Harry-Xue <hel...@gm...>
  Date:   2016-05-24 (Tue, 24 May 2016)

  Changed paths:
    M ddclient

  Log Message:
  -----------
  Add files via upload

Updated CloudFlare API from v1 to v4.


  Commit: f52195700b9db2165cda3b139093a83a2d85e548
      https://github.com/wimpunk/ddclient/commit/f52195700b9db2165cda3b139093a83a2d85e548
  Author: Harry-Xue <hel...@gm...>
  Date:   2016-05-24 (Tue, 24 May 2016)

  Changed paths:
    M ddclient

  Log Message:
  -----------
  Add files via upload

Catch up to changes in wimpunk/master.


  Commit: df883fd0913c448e28c2259cd76d69289e84ecfc
      https://github.com/wimpunk/ddclient/commit/df883fd0913c448e28c2259cd76d69289e84ecfc
  Author: wimpunk <wi...@us...>
  Date:   2016-05-25 (Wed, 25 May 2016)

  Changed paths:
    M ddclient

  Log Message:
  -----------
  Merge pull request #42 from Harry-Xue/master

Update CloudFlare from API v1 to API v4.

Patch provided by @Harry-Xue by pull-request #42


Compare: https://github.com/wimpunk/ddclient/compare/7cad3a497f46...df883fd0913c

[Ddclient-support] Multiple IP question

[wimpunk <wi...@us...>]

Hi all,

I'm just wondering, is there anyone out there who has experience with
the multiple IP feature of ddclient?  Someone posted a question on the
forum [1] about multiple IP but I can't answer it.  Is there anyone who can?

Regards,

wimpunk.

[1]
https://sourceforge.net/p/ddclient/discussion/399428/thread/dbdfac6b/#77b2

[Ddclient-support] Ddclient 3.8.3 released

[wimpunk <wi...@us...>]

Yet again it's been a while but here is new release of ddclient. As
usual,  there are some important changes and some documentation is modified.
A detailed overview can be found in ChangeLog but here's a quick overview:

    * added Alpine Linux init scritp - patch send by @Tal on github.
    * adding support for nsupdate - patch send by @droe on github
    * allow log username-password combinations - patch send by @dirdi on
github
    * adding support for cloudflare - patch send by @roberthawdon on github
    * adding support for duckdns - patch send by @gkranis

A very big thank you for everyone who created a pull request on github
and for everyone who helped to fix the little issues caused by the new
providers.

Kind regards,

wimpunk.

Re: [Ddclient-support] Testing ddlcient on a multi-interface-alias setup -- how do you make sure that only a specific interface/alias is checked?

[wimpunk <wi...@us...>]

On 05/15/15 18:15, gra...@op... wrote:
> Hi,
> 
> I've installed ddclient 3.8.2.
> 
> I currently have a static/29 block.
> 
> It's config'd with multiple aliases:
> 
> 	ip#0 -> 'eth0'
> 	ip#1 -> 'eth0:1'
> 	ip#2 -> 'eth0:2'
> 	ip#3 -> 'eth0:3'
> 	ip#4 -> 'eth0:4'
> 	ip#5 -> 'eth0:5'
> 	ip#6 -> 'eth0:6'
> 	ip#7 -> 'eth0:7'
> 
> I'm testing ddclient for eventual use with dynamic IP; for testing, I'm just checking/updating the 'main' (currently static) IP, ip#0.
> 
> Using ddlcient with remote checks
> 
> 	use=web, web=<remote server>
> 
> I can successfully update my ip @ dyndns, dnsomatic and  hurricane electric's tunnelbroker ...
> 
> ... MOST of the time.
> 
> Every once in awhile, the remote IP is set to one of the OTHER ips #1-7, i.e. @ an alias, eth0:1-7, rather than at the 'main' IP.
> 
> Apart from the fact it's a STATIC ip, and shouldn't change (for now), it's clearly checking the wrong interface/IP.  Not sure at all WHY this is happening.  Missing config/syntax?
> 
> What's the correct ddlcient syntax to ensure that ONLY a specific interface alias is used?
> 

I've never used the multi-interface with ddclient but it sounds a bit
strange to me to use ddclient if you have a fixed address range.
Anyway, it sounds wrong to use the 'use=web' if you want to do an update
based on your interface.  I would use use=if, if=eth0:7 if I want to
update according to the value of eth0:7.

Kind regards,

wimpunk.

[Ddclient-support] Testing ddlcient on a multi-interface-alias setup -- how do you make sure that only a specific interface/alias is checked?

[<gra...@op...>]

Hi,

I've installed ddclient 3.8.2.

I currently have a static/29 block.

It's config'd with multiple aliases:

	ip#0 -> 'eth0'
	ip#1 -> 'eth0:1'
	ip#2 -> 'eth0:2'
	ip#3 -> 'eth0:3'
	ip#4 -> 'eth0:4'
	ip#5 -> 'eth0:5'
	ip#6 -> 'eth0:6'
	ip#7 -> 'eth0:7'

I'm testing ddclient for eventual use with dynamic IP; for testing, I'm just checking/updating the 'main' (currently static) IP, ip#0.

Using ddlcient with remote checks

	use=web, web=<remote server>

I can successfully update my ip @ dyndns, dnsomatic and  hurricane electric's tunnelbroker ...

... MOST of the time.

Every once in awhile, the remote IP is set to one of the OTHER ips #1-7, i.e. @ an alias, eth0:1-7, rather than at the 'main' IP.

Apart from the fact it's a STATIC ip, and shouldn't change (for now), it's clearly checking the wrong interface/IP.  Not sure at all WHY this is happening.  Missing config/syntax?

What's the correct ddlcient syntax to ensure that ONLY a specific interface alias is used?

[Ddclient-support] Next release

[Momcilo M. <med...@gm...>]

Hi friends!

I see that there is a lot of development activity on ddclient, and I was
wandering why there hasn't been a release in about two years?

Keep up the great work!

Kind regards,
Momo.

Re: [Ddclient-support] ddclient improvement suggestion.

[Daniel R. <da...@ro...>]

wimpunk <wi...@us...> 2015-01-06:
> On 01/01/15 20:54, Paul N. Pace wrote:
> > I can only imagine the joyous times involved in uncovering such a bug.
> > 
> > On Thu, Jan 1, 2015 at 11:47 AM, balthasar_s <
> > bic...@ch...> wrote:
> > 
> >> ddclient won't update the IP until a minimal interval since last update.
> >> Very good. But the way it's implemented now can lead to problems in
> >> specific circumstances.
> >>
> 
> I think it could be useful to give a warning if the update time is
> earlier than than the current one when reading the cache.  If your
> system runs in a this kind of problem you suggest, you have bigger
> issues than only a not-updated dynamic address.

That may be, but if you depend on ddclient for remote access to
the system in order to fix the bigger problems, then giving a
warning is not very helpful.

Are there any issues with giving a warning *and* doing the update
for negative intervals?

-- 
Daniel Roethlisberger
http://daniel.roe.ch/

Re: [Ddclient-support] ddclient improvement suggestion.

[wimpunk <wi...@us...>]

On 01/01/15 20:54, Paul N. Pace wrote:
> I can only imagine the joyous times involved in uncovering such a bug.
> 
> On Thu, Jan 1, 2015 at 11:47 AM, balthasar_s <
> bic...@ch...> wrote:
> 
>> ddclient won't update the IP until a minimal interval since last update.
>> Very good. But the way it's implemented now can lead to problems in
>> specific circumstances.
>>

I think it could be useful to give a warning if the update time is
earlier than than the current one when reading the cache.  If your
system runs in a this kind of problem you suggest, you have bigger
issues than only a not-updated dynamic address.

Re: [Ddclient-support] ddclient improvement suggestion.

[Paul N. P. <pau...@gm...>]

I can only imagine the joyous times involved in uncovering such a bug.

On Thu, Jan 1, 2015 at 11:47 AM, balthasar_s <
bic...@ch...> wrote:

> ddclient won't update the IP until a minimal interval since last update.
> Very good. But the way it's implemented now can lead to problems in
> specific circumstances.
>
> For example. It's 2015. But the system clock is erroneously set to
> 2020 (because of problems with NTP or something else). Then ddclient
> runs and remembers in the cache that the last run was in 2020. After
> the system clock is (automatically) set back to 2015, ddclient becomes
> non-functional. It will refuse to update the IP because the 5 minute
> (or whatever else) interval since 2020 has not passed yet. Until 2020
> ddclient won't update anything unless the cache is removed.
> This is problematic because when you notice that you have to fix it
> and remove the cache it's too late because the IP changed, was not
> updated and you don't have access to your computer.
>
> This can be easily improved. Instead of checking the time distance
> into the future check the time distance in both directions. To do so
> replace one line in the interval_expired function.
>
>
> Change this:
>
> sub interval_expired {
>     my ($host, $time, $interval) = @_;
>
>     return 1 if !exists $cache{$host};
>     return 1 if !exists $cache{$host}{$time}      || !$cache{$host}{$time};
>     return 1 if !exists $config{$host}{$interval} ||
> !$config{$host}{$interval};
>
>     return $now > ($cache{$host}{$time} + $config{$host}{$interval});
> }
>
> to this:
>
> sub interval_expired {
>     my ($host, $time, $interval) = @_;
>
>     return 1 if !exists $cache{$host};
>     return 1 if !exists $cache{$host}{$time}      || !$cache{$host}{$time};
>     return 1 if !exists $config{$host}{$interval} ||
> !$config{$host}{$interval};
>
>     return ($now > ($cache{$host}{$time} + $config{$host}{$interval}))
> || ($now < ($cache{$host}{$time} - $config{$host}{$interval}));
> }
>
>
> that's all.
>
>
> Balthasar Szczepański
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Ddclient-support mailing list
> Ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddclient-support
>

[Ddclient-support] ddclient improvement suggestion.

[balthasar_s <bic...@ch...>]

ddclient won't update the IP until a minimal interval since last update.
Very good. But the way it's implemented now can lead to problems in
specific circumstances.

For example. It's 2015. But the system clock is erroneously set to
2020 (because of problems with NTP or something else). Then ddclient
runs and remembers in the cache that the last run was in 2020. After
the system clock is (automatically) set back to 2015, ddclient becomes
non-functional. It will refuse to update the IP because the 5 minute
(or whatever else) interval since 2020 has not passed yet. Until 2020
ddclient won't update anything unless the cache is removed.
This is problematic because when you notice that you have to fix it
and remove the cache it's too late because the IP changed, was not
updated and you don't have access to your computer.

This can be easily improved. Instead of checking the time distance
into the future check the time distance in both directions. To do so
replace one line in the interval_expired function.


Change this:

sub interval_expired {
    my ($host, $time, $interval) = @_;

    return 1 if !exists $cache{$host};
    return 1 if !exists $cache{$host}{$time}      || !$cache{$host}{$time};
    return 1 if !exists $config{$host}{$interval} || !$config{$host}{$interval};

    return $now > ($cache{$host}{$time} + $config{$host}{$interval});
}

to this:

sub interval_expired {
    my ($host, $time, $interval) = @_;

    return 1 if !exists $cache{$host};
    return 1 if !exists $cache{$host}{$time}      || !$cache{$host}{$time};
    return 1 if !exists $config{$host}{$interval} || !$config{$host}{$interval};

    return ($now > ($cache{$host}{$time} + $config{$host}{$interval}))
|| ($now < ($cache{$host}{$time} - $config{$host}{$interval}));
}


that's all.


Balthasar Szczepański

Re: [Ddclient-support] ddclient and nsupdate support

[wimpunk <wi...@us...>]

Hi,

I'm replying to the list to keep everyone up to date. Hope you don't mind.

On Mon, Oct 20, 2014 at 11:11 AM, Jérémie Courrèges-Anglas
<jer...@tr...> wrote:
> Hi,
>
> I am using the nsupdate support that was recently added to ddclient;
> works like a charm. So far I have only backported the functionality to
> the Debian unstable package so that I can use it in a not-so-hackish
> way. I have contacted the Debian maintainer of the ddclient package,
> mentioning that I was volunteering to do the work needed to have
> nsupdate support in Debian Jessie.

As far as I know, the debian maintainer follows the list so he should
get this message to.

>
> If you still wonder the purpose of this mail, here it is: there is no
> ddclient-3.8.3 release available, despite the bugfixes and new features! :)
>

I'm planning a new release pretty soon so if any patch has to be added
extra, feel free to send it, most preferrable through github.

> I don't know what the Debian maintainer will say, but maybe updating to
> a newer release is an option.
>

I hope so. :-)

> Regards,
>

Regards,

wimpunk.

Re: [Ddclient-support] unable to find the ip address

[Ian B. <an...@fa...>]

Hi,

Thanks for comments.
Basically up and running using a web ip provider icanhazip.com. Thus it runs fine. Comments below.
Beats me why it ceased to get the ip from (probably) ppp0. Something has changed somewhere.
Ian

On Fri, Oct 17, 2014 at 07:58:27AM +0200, wimpunk wrote:
> Hi,
> 
> On 16/10/14 14:19, Ian Balchin wrote:
> > Hi
> >
> > Whatever I do I cannot get the ip address.
> >
> > use=if, if=etho (returns local net ip address and will not connect to update)
> > use=if, if=ppp0 (reports <undefined>)
> 
> This setting means that ddclient will try to fetch the IP from the 
> interface with that name on the device it is running.
> 
> >
> > If I log into the adsl router it does show the correct ip address so it is there.
> 
> If you want to get the address from a router, you will probably need a 
> router configuration, not a interface configuration.
My router not listed, and all attempts had failed so discarded that solution.
It's a dlink and tried with variations of the examples given to no avail.
> 
> >
> > It used to work, then we had issues with the machine which revolved around permissions.
> > Could this be a permissions issue somehow?
> 
> 
> You would get a permission denied somewhere if it was a permission problem.
right, and there is no such message

> 
> >
> > Otherwise the ddclient.conf file seems correct and normal.
> >
> >   daemon=20m
> >   syslog=yes
> >   cache=/tmp/ddclient.cache
> >   pid=/var/run/ddclient.pid
> >   protocol=dyndns2
> >   use=if, if=eth0
> >   server=update.activedns.co.za
> >
> 
> If this is normal for you, then it will get the ip from your interface 
> eth0 end use that to update.  I hope you also have your credentials and 
> correct hostname in the file.
yes they are there and correct

> Running ddclient as `ddclient -daemon=0 -debug -verbose -noquiet` will 
> probably give you more info on what is going wrong.
that is a very helpful tool, I think I picked that up from the ddclient site on sourceforge?

> 
> Regards,
> 
> wimpunk.
> 
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Ddclient-support mailing list
> Ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddclient-support

Re: [Ddclient-support] new provider support

[wimpunk <wi...@us...>]

Hi,

On 16/10/14 19:15, H2L29 wrote:
> bump (subscribed to the list)
>
> 2014-10-16 18:13 GMT+02:00 H2L29 <sam...@gm...>:
>
>> hello
>>
>> thanks for your app
>>
>> can you add this provider?
>> http://www.freenom.com/en/freenom-api.html
>> i'd like use it for a .tk domain
>>
>> good luck
>>

Sorry but I'm afraid no one in here will have the time to add that 
provider to ddclient.  We do our best to maintain ddclient and try to 
support it but most doesn't have any sparetime left to add a service. If 
you try it yourself and supply a patch, then maybe we will add it to 
ddclient.  This could be some help:
http://sourceforge.net/p/ddclient/wiki/protocols/#your-favorite-provider-here

Regards,

wimpunk.

Re: [Ddclient-support] unable to find the ip address

[wimpunk <wi...@us...>]

Hi,

On 16/10/14 14:19, Ian Balchin wrote:
> Hi
>
> Whatever I do I cannot get the ip address.
>
> use=if, if=etho (returns local net ip address and will not connect to update)
> use=if, if=ppp0 (reports <undefined>)

This setting means that ddclient will try to fetch the IP from the 
interface with that name on the device it is running.

>
> If I log into the adsl router it does show the correct ip address so it is there.

If you want to get the address from a router, you will probably need a 
router configuration, not a interface configuration.

>
> It used to work, then we had issues with the machine which revolved around permissions.
> Could this be a permissions issue somehow?


You would get a permission denied somewhere if it was a permission problem.

>
> Otherwise the ddclient.conf file seems correct and normal.
>
>   daemon=20m
>   syslog=yes
>   cache=/tmp/ddclient.cache
>   pid=/var/run/ddclient.pid
>   protocol=dyndns2
>   use=if, if=eth0
>   server=update.activedns.co.za
>

If this is normal for you, then it will get the ip from your interface 
eth0 end use that to update.  I hope you also have your credentials and 
correct hostname in the file.
Running ddclient as `ddclient -daemon=0 -debug -verbose -noquiet` will 
probably give you more info on what is going wrong.

Regards,

wimpunk.

Re: [Ddclient-support] new provider support

[H2L29 <sam...@gm...>]

bump (subscribed to the list)

2014-10-16 18:13 GMT+02:00 H2L29 <sam...@gm...>:

> hello
>
> thanks for your app
>
> can you add this provider?
> http://www.freenom.com/en/freenom-api.html
> i'd like use it for a .tk domain
>
> good luck
>
> --
>



--

[Ddclient-support] unable to find the ip address

[Ian B. <an...@fa...>]

Hi

Whatever I do I cannot get the ip address.

use=if, if=etho (returns local net ip address and will not connect to update)
use=if, if=ppp0 (reports <undefined>)

If I log into the adsl router it does show the correct ip address so it is there.

It used to work, then we had issues with the machine which revolved around permissions.
Could this be a permissions issue somehow?

Otherwise the ddclient.conf file seems correct and normal.

 daemon=20m
 syslog=yes
 cache=/tmp/ddclient.cache
 pid=/var/run/ddclient.pid
 protocol=dyndns2
 use=if, if=eth0
 server=update.activedns.co.za


Ian

[Ddclient-support] zoneedit migration to easydns servers

[Joel A. <jo...@ge...>]

Forced one domain to update for testing and it appears to actually work but
ddclient doesn't seem to understand the responses.

INFO:     setting IP address to ***.***.***.*** for ***.***
UPDATE:   updating ***.***
CONNECT:  dynamic.zoneedit.com
CONNECTED:  using SSL
SENDING:  GET /auth/dynamic.html?host=***.***&dnsto=***.***.***.*** HTTP/1.0
SENDING:   Host: dynamic.zoneedit.com
SENDING:   Authorization: Basic ***
SENDING:   User-Agent: ddclient/3.8.1
SENDING:   Connection: close
SENDING:
RECEIVE:  HTTP/1.1 200 OK
RECEIVE:  Date: Sun, 05 Oct 2014 17:33:40 GMT
RECEIVE:  Server: Apache/2.2.22 (Debian)
RECEIVE:  X-Powered-By: PHP/5.4.4-14+deb7u14
RECEIVE:  Set-Cookie: easydns_language=en_US; expires=Mon, 05-Oct-2015
17:33:40 GMT; path=/
RECEIVE:  Set-Cookie: PHPSESSID=***; path=/
RECEIVE:  Expires: Thu, 19 Nov 1981 08:52:00 GMT
RECEIVE:  Cache-Control: no-store, no-cache, must-revalidate, post-check=0,
pre-check=0
RECEIVE:  Pragma: no-cache
RECEIVE:  Vary: Accept-Encoding
RECEIVE:  Content-Length: 140
RECEIVE:  Connection: close
RECEIVE:  Content-Type: text/html
RECEIVE:
RECEIVE:  <HTML><BODY><FONT FACE="sans-serif" SIZE="-1">OK<br />
RECEIVE:  <hr noshade size="1">
RECEIVE:  ***.*** updated to ***.***.***.***<br />
RECEIVE:  </FONT></BODY></HTML>
FAILED:   updating ***.***: no response from dynamic.zoneedit.com

Similarly, forcing to re-run again after it did update already:

...
RECEIVE:  <HTML><BODY><FONT FACE="sans-serif" SIZE="-1">OK<br />
RECEIVE:  <hr noshade size="1">
RECEIVE:  no update required for ***.*** to ***.***.***.***<br />
RECEIVE:  </FONT></BODY></HTML>
FAILED:   updating ***.***: no response from dynamic.zoneedit.com

Thanks,

-Joel