Hello,
this is a post to update you all about the recent developments regarding the support for the various upcoming dynamic DNS providers.
Rationale
Some of the major dynamic DNS providers stopped their free services or made them unusable so that people started searching for alternatives. In IPFire 2, a script called setddns.pl [1] is responsible for updating the dynamic DNS records. This script has grown over the last couple of months and if you have looked into it you will have noticed that it has become from ugly to almost un-maintainable. The decision that we don't want to take this mess with us into the next generation of IPFire was already made many years ago.
DDNS
A project called ddns was started which is a pure Python client that is much more flexible, cleanly rewritten and easily extensible. It is cross-platform, cross-distribution and does not need any third-party python modules.
The basics already written years ago, Stefan Schantl and I worked on making this ready for IPFire 2 and added all the providers that are currently supported by setddns.pl and ez-ipupdate.
The source for the new DDNS tool can be found over here:
http://git.ipfire.org/?p=ddns.git;a=summary
or on GitHub
https://github.com/ipfire/ddns
were you can send us pull requests for supporting new providers and so on.
Bug reports go to the usual place:
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
There is no fixed release schedule for this, but we are pretty sure that this won't take long until DDNS arrives in IPFire 2. That means that we won't take any patches for the setddns.pl script that add support for new providers any more.
We appreciate any contribution and as always hope to get some feedback back from the community!
Best, -Michael
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e...
Because of this same issue, I created a ddns system a few years ago. I also didn't like the possibility of DNS tracking the commercial dyndns companies would be capable of. I simply got a new domain and set it up.
It is a combination of bash and perl. I have never written an article on it or anything but I have some documentation. I'll be happy to write some better documentation and comment the code a little so it can be used when creating this new one.
Can't say much about it as it is fairly simple once I got the concepts down. I chose to set it up more securely by using ssh keys for the connection between the client and the dns server. Currently it is implemented on all my IPFire routers as a simple cron job that runs every hour.
Let me know if it might be helpful and/or if you need any help with writing the new one.
Rod
On 06/25/2014 05:21 AM, Michael Tremer wrote:
Hello,
this is a post to update you all about the recent developments regarding the support for the various upcoming dynamic DNS providers.
Rationale
Some of the major dynamic DNS providers stopped their free services or made them unusable so that people started searching for alternatives. In IPFire 2, a script called setddns.pl [1] is responsible for updating the dynamic DNS records. This script has grown over the last couple of months and if you have looked into it you will have noticed that it has become from ugly to almost un-maintainable. The decision that we don't want to take this mess with us into the next generation of IPFire was already made many years ago.
DDNS
A project called ddns was started which is a pure Python client that is much more flexible, cleanly rewritten and easily extensible. It is cross-platform, cross-distribution and does not need any third-party python modules.
The basics already written years ago, Stefan Schantl and I worked on making this ready for IPFire 2 and added all the providers that are currently supported by setddns.pl and ez-ipupdate.
The source for the new DDNS tool can be found over here:
http://git.ipfire.org/?p=ddns.git;a=summary
or on GitHub
https://github.com/ipfire/ddns
were you can send us pull requests for supporting new providers and so on.
Bug reports go to the usual place:
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
There is no fixed release schedule for this, but we are pretty sure that this won't take long until DDNS arrives in IPFire 2. That means that we won't take any patches for the setddns.pl script that add support for new providers any more.
We appreciate any contribution and as always hope to get some feedback back from the community!
Best, -Michael
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e...
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hi Michael & Stefan,
thanks for your Work! Looking forward to the first test with the new feature :)
Best, Thomas
Am 25.06.2014 12:21, schrieb Michael Tremer:
Hello,
this is a post to update you all about the recent developments regarding the support for the various upcoming dynamic DNS providers.
Rationale
Some of the major dynamic DNS providers stopped their free services or made them unusable so that people started searching for alternatives. In IPFire 2, a script called setddns.pl [1] is responsible for updating the dynamic DNS records. This script has grown over the last couple of months and if you have looked into it you will have noticed that it has become from ugly to almost un-maintainable. The decision that we don't want to take this mess with us into the next generation of IPFire was already made many years ago.
DDNS
A project called ddns was started which is a pure Python client that is much more flexible, cleanly rewritten and easily extensible. It is cross-platform, cross-distribution and does not need any third-party python modules.
The basics already written years ago, Stefan Schantl and I worked on making this ready for IPFire 2 and added all the providers that are currently supported by setddns.pl and ez-ipupdate.
The source for the new DDNS tool can be found over here:
http://git.ipfire.org/?p=ddns.git;a=summary
or on GitHub
https://github.com/ipfire/ddns
were you can send us pull requests for supporting new providers and so on.
Bug reports go to the usual place:
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
There is no fixed release schedule for this, but we are pretty sure that this won't take long until DDNS arrives in IPFire 2. That means that we won't take any patches for the setddns.pl script that add support for new providers any more.
We appreciate any contribution and as always hope to get some feedback back from the community!
Best, -Michael
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e...
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hi @ all,
please change spdns url in line 1456 /usr/lib/python2.7/site-packages/ddns/providers.py script.
https://github.com/ipfire/ddns/blob/master/src/ddns/providers.py
from old update setting:
url = "https://update.spdns.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
to the new update setting:
url = "https://update.spdyn.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
big thx, 5p9
Would you want to send a patch for this?
On Tue, 2016-06-07 at 15:22 +0200, 5p9 wrote:
Hi @ all,
please change spdns url in line 1456 /usr/lib/python2.7/site-packages/ddns/providers.py script.
https://github.com/ipfire/ddns/blob/master/src/ddns/providers.py
from old update setting:
url = "https://update.spdns.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
to the new update setting:
url = "https://update.spdyn.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
big thx, 5p9
Hi,
sorry, i dont have a git-system in the moment to send a patch for this modification :(
BR, Thomas
Am 07.06.2016 um 16:24 schrieb Michael Tremer:
Would you want to send a patch for this?
On Tue, 2016-06-07 at 15:22 +0200, 5p9 wrote:
Hi @ all,
please change spdns url in line 1456 /usr/lib/python2.7/site-packages/ddns/providers.py script.
https://github.com/ipfire/ddns/blob/master/src/ddns/providers.py
from old update setting:
url = "https://update.spdns.de/nic/update" @property def username(self): return self.get("username") or self.hostname @property def password(self): return self.get("password") or self.token
to the new update setting:
url = "https://update.spdyn.de/nic/update" @property def username(self): return self.get("username") or self.hostname @property def password(self): return self.get("password") or self.token
big thx, 5p9
Please test this:
http://lists.ipfire.org/pipermail/ddns/2016-June/000024.html
On Tue, 2016-06-07 at 16:28 +0200, 5p9 wrote:
Hi,
sorry, i dont have a git-system in the moment to send a patch for this modification :(
BR, Thomas
Am 07.06.2016 um 16:24 schrieb Michael Tremer:
Would you want to send a patch for this?
On Tue, 2016-06-07 at 15:22 +0200, 5p9 wrote:
Hi @ all,
please change spdns url in line 1456 /usr/lib/python2.7/site-packages/ddns/providers.py script.
https://github.com/ipfire/ddns/blob/master/src/ddns/providers.py
from old update setting:
url = "https://update.spdns.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
to the new update setting:
url = "https://update.spdyn.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
big thx, 5p9
Hi,
i change it manually in the py and run perfect, thx for your update ;)
Thomas
Am 07.06.2016 um 16:35 schrieb Michael Tremer:
Please test this:
http://lists.ipfire.org/pipermail/ddns/2016-June/000024.html
On Tue, 2016-06-07 at 16:28 +0200, 5p9 wrote:
Hi,
sorry, i dont have a git-system in the moment to send a patch for this modification :(
BR, Thomas
Am 07.06.2016 um 16:24 schrieb Michael Tremer:
Would you want to send a patch for this?
On Tue, 2016-06-07 at 15:22 +0200, 5p9 wrote:
Hi @ all,
please change spdns url in line 1456 /usr/lib/python2.7/site-packages/ddns/providers.py script.
https://github.com/ipfire/ddns/blob/master/src/ddns/providers.py
from old update setting:
url = "https://update.spdns.de/nic/update" @property def username(self): return self.get("username") or self.hostname @property def password(self): return self.get("password") or self.token
to the new update setting:
url = "https://update.spdyn.de/nic/update" @property def username(self): return self.get("username") or self.hostname @property def password(self): return self.get("password") or self.token
big thx, 5p9
Stefan, please review this too and merge if ok.
Tested-by: Thomas Berthel 5p9@ipfire.org
-Michael
On Tue, 2016-06-07 at 16:38 +0200, 5p9 wrote:
Hi,
i change it manually in the py and run perfect, thx for your update ;)
Thomas
Am 07.06.2016 um 16:35 schrieb Michael Tremer:
Please test this:
http://lists.ipfire.org/pipermail/ddns/2016-June/000024.html
On Tue, 2016-06-07 at 16:28 +0200, 5p9 wrote:
Hi,
sorry, i dont have a git-system in the moment to send a patch for this modification :(
BR, Thomas
Am 07.06.2016 um 16:24 schrieb Michael Tremer:
Would you want to send a patch for this?
On Tue, 2016-06-07 at 15:22 +0200, 5p9 wrote:
Hi @ all,
please change spdns url in line 1456 /usr/lib/python2.7/site-packages/ddns/providers.py script.
https://github.com/ipfire/ddns/blob/master/src/ddns/providers.py
from old update setting:
url = "https://update.spdns.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
to the new update setting:
url = "https://update.spdyn.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
big thx, 5p9
@Stefan: Please merge this and any remaining patches and tag a release.
This did not make it to go into Core Update 103 now and I do not think that it is necessary to delay those changes any longer.
-Michael
On Tue, 2016-06-07 at 15:39 +0100, Michael Tremer wrote:
Stefan, please review this too and merge if ok.
Tested-by: Thomas Berthel 5p9@ipfire.org
-Michael
On Tue, 2016-06-07 at 16:38 +0200, 5p9 wrote:
Hi,
i change it manually in the py and run perfect, thx for your update ;)
Thomas
Am 07.06.2016 um 16:35 schrieb Michael Tremer:
Please test this:
http://lists.ipfire.org/pipermail/ddns/2016-June/000024.html
On Tue, 2016-06-07 at 16:28 +0200, 5p9 wrote:
Hi,
sorry, i dont have a git-system in the moment to send a patch for this modification :(
BR, Thomas
Am 07.06.2016 um 16:24 schrieb Michael Tremer:
Would you want to send a patch for this?
On Tue, 2016-06-07 at 15:22 +0200, 5p9 wrote:
Hi @ all,
please change spdns url in line 1456 /usr/lib/python2.7/site-packages/ddns/providers.py script.
https://github.com/ipfire/ddns/blob/master/src/ddns/providers.py
from old update setting:
url = "https://update.spdns.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
to the new update setting:
url = "https://update.spdyn.de/nic/update"
@property def username(self): return self.get("username") or self.hostname
@property def password(self): return self.get("password") or self.token
big thx, 5p9
ddns mailing list ddns@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/ddns
Hello Michael,
patch has been merged and I also tagged a new release (ddns-010).
I also updated the dynDNS client in IPFire 2 to the new release and added it to core update 104 so it will be shipped.
Best regards,
-Stefan
@Stefan: Please merge this and any remaining patches and tag a release.
This did not make it to go into Core Update 103 now and I do not think that it is necessary to delay those changes any longer.
-Michael
On Tue, 2016-06-07 at 15:39 +0100, Michael Tremer wrote:
Stefan, please review this too and merge if ok.
Tested-by: Thomas Berthel 5p9@ipfire.org
-Michael
On Tue, 2016-06-07 at 16:38 +0200, 5p9 wrote:
Hi,
i change it manually in the py and run perfect, thx for your update ;)
Thomas
Am 07.06.2016 um 16:35 schrieb Michael Tremer:
Please test this:
http://lists.ipfire.org/pipermail/ddns/2016-June/000024.html
On Tue, 2016-06-07 at 16:28 +0200, 5p9 wrote:
Hi,
sorry, i dont have a git-system in the moment to send a patch for this modification :(
BR, Thomas
Am 07.06.2016 um 16:24 schrieb Michael Tremer:
Would you want to send a patch for this?
On Tue, 2016-06-07 at 15:22 +0200, 5p9 wrote: > > > > > Hi @ all, > > please change spdns url in line 1456 > /usr/lib/python2.7/site-packages/ddns/providers.py > script. > > https://github.com/ipfire/ddns/blob/master/src/ddns/provi > ders.py > > > > from old update setting: > > url = "https://update.spdns.de/nic/update" > > @property > def username(self): > return self.get("username") or > self.hostname > > @property > def password(self): > return self.get("password") or self.token > > to the new update setting: > > url = "https://update.spdyn.de/nic/update" > > @property > def username(self): > return self.get("username") or > self.hostname > > @property > def password(self): > return self.get("password") or self.token > > big thx, 5p9
ddns mailing list ddns@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/ddns
Hello Michael,
I've coded some lines to support the ddns provider "enom.com" which has been requested on our bugtracker (#10588, #10567).
Basic tests with some invalid data ( because I don't have an account there) have been performed and the errors have been triggered the correct exceptions.
* While implementing the new ddns provider, I've moved the "parse_xml" function from the Namecheap provider to the DDNSProvider main class to allow reuse of the code and gain access to this function for additional providers which will be included in the future.
* I also found some missing lines which accidently have been dropped while fixing merge conflicts.
You can find all changes here:
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=21d0fcb8335d97934...
Please have a look on them and merge them to upstream.
A big thanks in advance,
-Stefan
Hello,
this is a post to update you all about the recent developments regarding the support for the various upcoming dynamic DNS providers.
Rationale
Some of the major dynamic DNS providers stopped their free services or made them unusable so that people started searching for alternatives. In IPFire 2, a script called setddns.pl [1] is responsible for updating the dynamic DNS records. This script has grown over the last couple of months and if you have looked into it you will have noticed that it has become from ugly to almost un-maintainable. The decision that we don't want to take this mess with us into the next generation of IPFire was already made many years ago.
DDNS
A project called ddns was started which is a pure Python client that is much more flexible, cleanly rewritten and easily extensible. It is cross-platform, cross-distribution and does not need any third-party python modules.
The basics already written years ago, Stefan Schantl and I worked on making this ready for IPFire 2 and added all the providers that are currently supported by setddns.pl and ez-ipupdate.
The source for the new DDNS tool can be found over here:
http://git.ipfire.org/?p=ddns.git;a=summary
or on GitHub
https://github.com/ipfire/ddns
were you can send us pull requests for supporting new providers and so on.
Bug reports go to the usual place:
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
There is no fixed release schedule for this, but we are pretty sure that this won't take long until DDNS arrives in IPFire 2. That means that we won't take any patches for the setddns.pl script that add support for new providers any more.
We appreciate any contribution and as always hope to get some feedback back from the community!
Best, -Michael
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e...
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hello,
On Mon, 2014-06-30 at 20:53 +0200, Stefan Schantl wrote:
Hello Michael,
I've coded some lines to support the ddns provider "enom.com" which has been requested on our bugtracker (#10588, #10567).
Basic tests with some invalid data ( because I don't have an account there) have been performed and the errors have been triggered the correct exceptions.
Great, but you really need to test your code. If it is a free provider go and register an account. If not, search for someone who has already got an account and get them testing this for you.
- While implementing the new ddns provider, I've moved the "parse_xml"
function from the Namecheap provider to the DDNSProvider main class to allow reuse of the code and gain access to this function for additional providers which will be included in the future.
I really don't see why we would need that in the global class. You could probably move that to a third class you pull in which then provides only this function. A class can inherit from multiple classes at the same time.
- I also found some missing lines which accidently have been dropped
while fixing merge conflicts.
I would need an extra commit with only that.
You can find all changes here:
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=21d0fcb8335d97934...
Please have a look on them and merge them to upstream.
Done that. See my remarks above.
-Michael
A big thanks in advance,
-Stefan
Hello,
this is a post to update you all about the recent developments regarding the support for the various upcoming dynamic DNS providers.
Rationale
Some of the major dynamic DNS providers stopped their free services or made them unusable so that people started searching for alternatives. In IPFire 2, a script called setddns.pl [1] is responsible for updating the dynamic DNS records. This script has grown over the last couple of months and if you have looked into it you will have noticed that it has become from ugly to almost un-maintainable. The decision that we don't want to take this mess with us into the next generation of IPFire was already made many years ago.
DDNS
A project called ddns was started which is a pure Python client that is much more flexible, cleanly rewritten and easily extensible. It is cross-platform, cross-distribution and does not need any third-party python modules.
The basics already written years ago, Stefan Schantl and I worked on making this ready for IPFire 2 and added all the providers that are currently supported by setddns.pl and ez-ipupdate.
The source for the new DDNS tool can be found over here:
http://git.ipfire.org/?p=ddns.git;a=summary
or on GitHub
https://github.com/ipfire/ddns
were you can send us pull requests for supporting new providers and so on.
Bug reports go to the usual place:
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
There is no fixed release schedule for this, but we are pretty sure that this won't take long until DDNS arrives in IPFire 2. That means that we won't take any patches for the setddns.pl script that add support for new providers any more.
We appreciate any contribution and as always hope to get some feedback back from the community!
Best, -Michael
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e...
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hi, can someone write me a short email howto test ddns? Checking out the ddns.git, and doing a ./make.sh build and extracting the build ddns package on my ipfire?
Ben
2014-06-30 21:05 GMT+02:00 Michael Tremer michael.tremer@ipfire.org:
Hello,
On Mon, 2014-06-30 at 20:53 +0200, Stefan Schantl wrote:
Hello Michael,
I've coded some lines to support the ddns provider "enom.com" which has been requested on our bugtracker (#10588, #10567).
Basic tests with some invalid data ( because I don't have an account there) have been performed and the errors have been triggered the correct exceptions.
Great, but you really need to test your code. If it is a free provider go and register an account. If not, search for someone who has already got an account and get them testing this for you.
- While implementing the new ddns provider, I've moved the "parse_xml"
function from the Namecheap provider to the DDNSProvider main class to allow reuse of the code and gain access to this function for additional providers which will be included in the future.
I really don't see why we would need that in the global class. You could probably move that to a third class you pull in which then provides only this function. A class can inherit from multiple classes at the same time.
- I also found some missing lines which accidently have been dropped
while fixing merge conflicts.
I would need an extra commit with only that.
You can find all changes here:
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=21d0fcb8335d97934...
Please have a look on them and merge them to upstream.
Done that. See my remarks above.
-Michael
A big thanks in advance,
-Stefan
Hello,
this is a post to update you all about the recent developments
regarding
the support for the various upcoming dynamic DNS providers.
Rationale
Some of the major dynamic DNS providers stopped their free services or made them unusable so that people started searching for alternatives.
In
IPFire 2, a script called setddns.pl [1] is responsible for updating
the
dynamic DNS records. This script has grown over the last couple of months and if you have looked into it you will have noticed that it has become from ugly to almost un-maintainable. The decision that we don't want to take this mess with us into the next generation of IPFire was already made many years ago.
DDNS
A project called ddns was started which is a pure Python client that is much more flexible, cleanly rewritten and easily extensible. It is cross-platform, cross-distribution and does not need any third-party python modules.
The basics already written years ago, Stefan Schantl and I worked on making this ready for IPFire 2 and added all the providers that are currently supported by setddns.pl and ez-ipupdate.
The source for the new DDNS tool can be found over here:
http://git.ipfire.org/?p=ddns.git;a=summary
or on GitHub
https://github.com/ipfire/ddns
were you can send us pull requests for supporting new providers and so on.
Bug reports go to the usual place:
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
There is no fixed release schedule for this, but we are pretty sure
that
this won't take long until DDNS arrives in IPFire 2. That means that we won't take any patches for the setddns.pl script that add support for new providers any more.
We appreciate any contribution and as always hope to get some feedback back from the community!
Best, -Michael
[1]
http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e...
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
On Thu, 2014-07-03 at 12:39 +0200, Benjamin Schweikert wrote:
Hi,
can someone write me a short email howto test ddns? Checking out the ddns.git, and doing a ./make.sh build and extracting the build ddns package on my ipfire?
We plan to ship this with Core Update 80 and will hopefully upload a first test build into the testing branch soon.
If you cannot stand the wait, you will find everything what is needed in the next branch.
Best, -Michael
Ben
2014-06-30 21:05 GMT+02:00 Michael Tremer michael.tremer@ipfire.org: Hello,
On Mon, 2014-06-30 at 20:53 +0200, Stefan Schantl wrote: > Hello Michael, > > I've coded some lines to support the ddns provider "enom.com" which has > been requested on our bugtracker (#10588, #10567). > > Basic tests with some invalid data ( because I don't have an account > there) have been performed and the errors have been triggered the > correct exceptions. Great, but you really need to test your code. If it is a free provider go and register an account. If not, search for someone who has already got an account and get them testing this for you. > * While implementing the new ddns provider, I've moved the "parse_xml" > function from the Namecheap provider to the DDNSProvider main class to > allow reuse of the code and gain access to this function for additional > providers which will be included in the future. I really don't see why we would need that in the global class. You could probably move that to a third class you pull in which then provides only this function. A class can inherit from multiple classes at the same time. > * I also found some missing lines which accidently have been dropped > while fixing merge conflicts. I would need an extra commit with only that. > You can find all changes here: > > http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=21d0fcb8335d979344a97e33cc36aa88d0fd67cb > > Please have a look on them and merge them to upstream. Done that. See my remarks above. -Michael > A big thanks in advance, > > -Stefan > > Hello, > > > > this is a post to update you all about the recent developments regarding > > the support for the various upcoming dynamic DNS providers. > > > > > > Rationale > > > > Some of the major dynamic DNS providers stopped their free services or > > made them unusable so that people started searching for alternatives. In > > IPFire 2, a script called setddns.pl [1] is responsible for updating the > > dynamic DNS records. This script has grown over the last couple of > > months and if you have looked into it you will have noticed that it has > > become from ugly to almost un-maintainable. The decision that we don't > > want to take this mess with us into the next generation of IPFire was > > already made many years ago. > > > > > > DDNS > > > > A project called ddns was started which is a pure Python client that is > > much more flexible, cleanly rewritten and easily extensible. It is > > cross-platform, cross-distribution and does not need any third-party > > python modules. > > > > The basics already written years ago, Stefan Schantl and I worked on > > making this ready for IPFire 2 and added all the providers that are > > currently supported by setddns.pl and ez-ipupdate. > > > > The source for the new DDNS tool can be found over here: > > > > http://git.ipfire.org/?p=ddns.git;a=summary > > > > or on GitHub > > > > https://github.com/ipfire/ddns > > > > were you can send us pull requests for supporting new providers and so > > on. > > > > Bug reports go to the usual place: > > > > https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater > > > > There is no fixed release schedule for this, but we are pretty sure that > > this won't take long until DDNS arrives in IPFire 2. That means that we > > won't take any patches for the setddns.pl script that add support for > > new providers any more. > > > > We appreciate any contribution and as always hope to get some feedback > > back from the community! > > > > Best, > > -Michael > > > > [1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e77fce5c024a3f17ba4c892a94abfe95845e8c6;hb=HEAD > > > > _______________________________________________ > > Development mailing list > > Development@lists.ipfire.org > > http://lists.ipfire.org/mailman/listinfo/development > > _______________________________________________ > Development mailing list > Development@lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Micha, the next branch build fails at the moment because ddns need intltool what is not build at ddns buildtime.
Arne
On 2014-07-09 20:31, Michael Tremer wrote:
On Thu, 2014-07-03 at 12:39 +0200, Benjamin Schweikert wrote:
Hi,
can someone write me a short email howto test ddns? Checking out the ddns.git, and doing a ./make.sh build and extracting the build ddns package on my ipfire?
We plan to ship this with Core Update 80 and will hopefully upload a first test build into the testing branch soon.
If you cannot stand the wait, you will find everything what is needed in the next branch.
Best, -Michael
Ben
2014-06-30 21:05 GMT+02:00 Michael Tremer michael.tremer@ipfire.org: Hello,
On Mon, 2014-06-30 at 20:53 +0200, Stefan Schantl wrote: > Hello Michael, > > I've coded some lines to support the ddns provider "enom.com" which has > been requested on our bugtracker (#10588, #10567). > > Basic tests with some invalid data ( because I don't have an account > there) have been performed and the errors have been triggered the > correct exceptions. Great, but you really need to test your code. If it is a free provider go and register an account. If not, search for someone who has already got an account and get them testing this for you. > * While implementing the new ddns provider, I've moved the "parse_xml" > function from the Namecheap provider to the DDNSProvider main class to > allow reuse of the code and gain access to this function for additional > providers which will be included in the future. I really don't see why we would need that in the global class. You could probably move that to a third class you pull in which then provides only this function. A class can inherit from multiple classes at the same time. > * I also found some missing lines which accidently have been dropped > while fixing merge conflicts. I would need an extra commit with only that. > You can find all changes here: > >
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=21d0fcb8335d97934... > > Please have a look on them and merge them to upstream.
Done that. See my remarks above. -Michael > A big thanks in advance, > > -Stefan > > Hello, > > > > this is a post to update you all about the recent developments regarding > > the support for the various upcoming dynamic DNS providers. > > > > > > Rationale > > > > Some of the major dynamic DNS providers stopped their free services or > > made them unusable so that people started searching for alternatives. In > > IPFire 2, a script called setddns.pl [1] is responsible for updating the > > dynamic DNS records. This script has grown over the last couple of > > months and if you have looked into it you will have noticed that it has > > become from ugly to almost un-maintainable. The decision that we don't > > want to take this mess with us into the next generation of IPFire was > > already made many years ago. > > > > > > DDNS > > > > A project called ddns was started which is a pure Python client that is > > much more flexible, cleanly rewritten and easily extensible. It is > > cross-platform, cross-distribution and does not need any third-party > > python modules. > > > > The basics already written years ago, Stefan Schantl and I worked on > > making this ready for IPFire 2 and added all the providers that are > > currently supported by setddns.pl and ez-ipupdate. > > > > The source for the new DDNS tool can be found over here: > > > > http://git.ipfire.org/?p=ddns.git;a=summary > > > > or on GitHub > > > > https://github.com/ipfire/ddns > > > > were you can send us pull requests for supporting new providers and so > > on. > > > > Bug reports go to the usual place: > > > >
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater > > > > There is no fixed release schedule for this, but we are pretty sure that > > this won't take long until DDNS arrives in IPFire 2. That means that we > > won't take any patches for the setddns.pl script that add support for > > new providers any more. > > > > We appreciate any contribution and as always hope to get some feedback > > back from the community! > > > > Best, > > -Michael > > > > [1]
http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e... > > > > _______________________________________________ > > Development mailing list > > Development@lists.ipfire.org > > http://lists.ipfire.org/mailman/listinfo/development > > _______________________________________________ > Development mailing list > Development@lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/development
_______________________________________________ Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hi Arne,
thanks. I was going to do a full rebuild this afternoon and should have noticed this error. Thanks for your hint on it.
-Michael
On Thu, 2014-07-10 at 15:34 +0200, Arne Fitzenreiter wrote:
Micha, the next branch build fails at the moment because ddns need intltool what is not build at ddns buildtime.
Arne
On 2014-07-09 20:31, Michael Tremer wrote:
On Thu, 2014-07-03 at 12:39 +0200, Benjamin Schweikert wrote:
Hi,
can someone write me a short email howto test ddns? Checking out the ddns.git, and doing a ./make.sh build and extracting the build ddns package on my ipfire?
We plan to ship this with Core Update 80 and will hopefully upload a first test build into the testing branch soon.
If you cannot stand the wait, you will find everything what is needed in the next branch.
Best, -Michael
Ben
2014-06-30 21:05 GMT+02:00 Michael Tremer michael.tremer@ipfire.org: Hello,
On Mon, 2014-06-30 at 20:53 +0200, Stefan Schantl wrote: > Hello Michael, > > I've coded some lines to support the ddns provider "enom.com" which has > been requested on our bugtracker (#10588, #10567). > > Basic tests with some invalid data ( because I don't have an account > there) have been performed and the errors have been triggered the > correct exceptions. Great, but you really need to test your code. If it is a free provider go and register an account. If not, search for someone who has already got an account and get them testing this for you. > * While implementing the new ddns provider, I've moved the "parse_xml" > function from the Namecheap provider to the DDNSProvider main class to > allow reuse of the code and gain access to this function for additional > providers which will be included in the future. I really don't see why we would need that in the global class. You could probably move that to a third class you pull in which then provides only this function. A class can inherit from multiple classes at the same time. > * I also found some missing lines which accidently have been dropped > while fixing merge conflicts. I would need an extra commit with only that. > You can find all changes here: > >
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=21d0fcb8335d97934... > > Please have a look on them and merge them to upstream.
Done that. See my remarks above. -Michael > A big thanks in advance, > > -Stefan > > Hello, > > > > this is a post to update you all about the recent developments regarding > > the support for the various upcoming dynamic DNS providers. > > > > > > Rationale > > > > Some of the major dynamic DNS providers stopped their free services or > > made them unusable so that people started searching for alternatives. In > > IPFire 2, a script called setddns.pl [1] is responsible for updating the > > dynamic DNS records. This script has grown over the last couple of > > months and if you have looked into it you will have noticed that it has > > become from ugly to almost un-maintainable. The decision that we don't > > want to take this mess with us into the next generation of IPFire was > > already made many years ago. > > > > > > DDNS > > > > A project called ddns was started which is a pure Python client that is > > much more flexible, cleanly rewritten and easily extensible. It is > > cross-platform, cross-distribution and does not need any third-party > > python modules. > > > > The basics already written years ago, Stefan Schantl and I worked on > > making this ready for IPFire 2 and added all the providers that are > > currently supported by setddns.pl and ez-ipupdate. > > > > The source for the new DDNS tool can be found over here: > > > > http://git.ipfire.org/?p=ddns.git;a=summary > > > > or on GitHub > > > > https://github.com/ipfire/ddns > > > > were you can send us pull requests for supporting new providers and so > > on. > > > > Bug reports go to the usual place: > > > >
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater > > > > There is no fixed release schedule for this, but we are pretty sure that > > this won't take long until DDNS arrives in IPFire 2. That means that we > > won't take any patches for the setddns.pl script that add support for > > new providers any more. > > > > We appreciate any contribution and as always hope to get some feedback > > back from the community! > > > > Best, > > -Michael > > > > [1]
http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e... > > > > _______________________________________________ > > Development mailing list > > Development@lists.ipfire.org > > http://lists.ipfire.org/mailman/listinfo/development > > _______________________________________________ > Development mailing list > Development@lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/development
_______________________________________________ Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hello Michael,
thanks for your feedback, I've reworked my changes and divided into several commits now.
Hello,
On Mon, 2014-06-30 at 20:53 +0200, Stefan Schantl wrote:
Hello Michael,
I've coded some lines to support the ddns provider "enom.com" which has been requested on our bugtracker (#10588, #10567).
Basic tests with some invalid data ( because I don't have an account there) have been performed and the errors have been triggered the correct exceptions.
Great, but you really need to test your code. If it is a free provider go and register an account. If not, search for someone who has already got an account and get them testing this for you.
Thanks for the hint, I will try to get a tester for this non free provider.
The code for adding it can be obtained from here:
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=3521652326429d80c...
- While implementing the new ddns provider, I've moved the "parse_xml"
function from the Namecheap provider to the DDNSProvider main class to allow reuse of the code and gain access to this function for additional providers which will be included in the future.
I really don't see why we would need that in the global class. You could probably move that to a third class you pull in which then provides only this function. A class can inherit from multiple classes at the same time.
I've moved the affected code parts now into it's own class as you suggested.
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=78c9780b8f7e6342b...
- I also found some missing lines which accidently have been dropped
while fixing merge conflicts.
I would need an extra commit with only that.
Done.
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=a204b1072c8e45c1c...
Best,
-Stefan
You can find all changes here:
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=21d0fcb8335d97934...
Please have a look on them and merge them to upstream.
Done that. See my remarks above.
-Michael
A big thanks in advance,
-Stefan
Hello,
this is a post to update you all about the recent developments regarding the support for the various upcoming dynamic DNS providers.
Rationale
Some of the major dynamic DNS providers stopped their free services or made them unusable so that people started searching for alternatives. In IPFire 2, a script called setddns.pl [1] is responsible for updating the dynamic DNS records. This script has grown over the last couple of months and if you have looked into it you will have noticed that it has become from ugly to almost un-maintainable. The decision that we don't want to take this mess with us into the next generation of IPFire was already made many years ago.
DDNS
A project called ddns was started which is a pure Python client that is much more flexible, cleanly rewritten and easily extensible. It is cross-platform, cross-distribution and does not need any third-party python modules.
The basics already written years ago, Stefan Schantl and I worked on making this ready for IPFire 2 and added all the providers that are currently supported by setddns.pl and ez-ipupdate.
The source for the new DDNS tool can be found over here:
http://git.ipfire.org/?p=ddns.git;a=summary
or on GitHub
https://github.com/ipfire/ddns
were you can send us pull requests for supporting new providers and so on.
Bug reports go to the usual place:
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
There is no fixed release schedule for this, but we are pretty sure that this won't take long until DDNS arrives in IPFire 2. That means that we won't take any patches for the setddns.pl script that add support for new providers any more.
We appreciate any contribution and as always hope to get some feedback back from the community!
Best, -Michael
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e...
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Thanks, merged.
On Wed, 2014-07-09 at 19:37 +0200, Stefan Schantl wrote:
Hello Michael,
thanks for your feedback, I've reworked my changes and divided into several commits now.
Hello,
On Mon, 2014-06-30 at 20:53 +0200, Stefan Schantl wrote:
Hello Michael,
I've coded some lines to support the ddns provider "enom.com" which has been requested on our bugtracker (#10588, #10567).
Basic tests with some invalid data ( because I don't have an account there) have been performed and the errors have been triggered the correct exceptions.
Great, but you really need to test your code. If it is a free provider go and register an account. If not, search for someone who has already got an account and get them testing this for you.
Thanks for the hint, I will try to get a tester for this non free provider.
The code for adding it can be obtained from here:
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=3521652326429d80c...
- While implementing the new ddns provider, I've moved the "parse_xml"
function from the Namecheap provider to the DDNSProvider main class to allow reuse of the code and gain access to this function for additional providers which will be included in the future.
I really don't see why we would need that in the global class. You could probably move that to a third class you pull in which then provides only this function. A class can inherit from multiple classes at the same time.
I've moved the affected code parts now into it's own class as you suggested.
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=78c9780b8f7e6342b...
- I also found some missing lines which accidently have been dropped
while fixing merge conflicts.
I would need an extra commit with only that.
Done.
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=a204b1072c8e45c1c...
Best,
-Stefan
You can find all changes here:
http://git.ipfire.org/?p=people/stevee/ddns.git;a=commit;h=21d0fcb8335d97934...
Please have a look on them and merge them to upstream.
Done that. See my remarks above.
-Michael
A big thanks in advance,
-Stefan
Hello,
this is a post to update you all about the recent developments regarding the support for the various upcoming dynamic DNS providers.
Rationale
Some of the major dynamic DNS providers stopped their free services or made them unusable so that people started searching for alternatives. In IPFire 2, a script called setddns.pl [1] is responsible for updating the dynamic DNS records. This script has grown over the last couple of months and if you have looked into it you will have noticed that it has become from ugly to almost un-maintainable. The decision that we don't want to take this mess with us into the next generation of IPFire was already made many years ago.
DDNS
A project called ddns was started which is a pure Python client that is much more flexible, cleanly rewritten and easily extensible. It is cross-platform, cross-distribution and does not need any third-party python modules.
The basics already written years ago, Stefan Schantl and I worked on making this ready for IPFire 2 and added all the providers that are currently supported by setddns.pl and ez-ipupdate.
The source for the new DDNS tool can be found over here:
http://git.ipfire.org/?p=ddns.git;a=summary
or on GitHub
https://github.com/ipfire/ddns
were you can send us pull requests for supporting new providers and so on.
Bug reports go to the usual place:
https://bugzilla.ipfire.org/describecomponents.cgi?product=DDNS%20Updater
There is no fixed release schedule for this, but we are pretty sure that this won't take long until DDNS arrives in IPFire 2. That means that we won't take any patches for the setddns.pl script that add support for new providers any more.
We appreciate any contribution and as always hope to get some feedback back from the community!
Best, -Michael
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/scripts/setddns.pl;h=5e...
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development