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=5…
Did a Cacti install on one of my clients routers and the installer did
not create the cacti database or populate it.
I edited the Cacti article on the wiki at
http://wiki.ipfire.org/en/addons/cacti/start
I think anyone crazy enough to mess with Cacti probably is ok on the
cli, so I don't know if there is any reason to mess with the cacti
installation script or not. My vote is leave it out and just make the
user run a couple of simple commands. But, then I'm stupid enough to
think a router makes a good place for a cacti install, so what do I know.
Happy to look at the installation script if you want it fixed.
Rod
--
"Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net
