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…
Hi,
i have a problem with the nagios-plugin compilation,
it hangs up by checking icmpv6 ping syntax.
i try to compile nagios without ipv6 and sends a patch. I remember that
IPFire-2.x comes without ipv6 support by default ?!
best regards
Sascha
Hi there,
i have updated some Packages:
alsa to 1.0.28
cups to 1.7.5
allready waiting:
mysql to 5.6.19
please test it, the LFS files you can checkout from my private
Repository: https://bitbucket.org/tikira/ipfire-2.x
best regards
Sascha
Hi all,
since the update to OpenVPN version 2.3 on IPFire the client log message "DEPRECATED OPTION: --tls-remote, please update your configuration" appears. so the clientside directive "--tls-remote" will be removed from OpenVPN in one of the comming versions --> https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage . For future updates of OpenVPN on IPFire (2.4+) it will be important to modify existing client.ovpn´s and replace the "--tls-remote name" with the new "--verify-x509-name name type" directive.
Since OpenVPN client/server version 2.3.2 the new verify option can be used in client configs whereby "type" includes the possibilty of 3 different kinds of verification --> "subject", "name" and "name-prefix" . This leads to a question which one of the "types" should be used for future versions on IPFire.
At this time IPFire handles "--tls-remote" automatically and it can´t be configured over the WUI, this is handy cause the user doesn´t need to bother around with all that kind of settings, but should this remain in that way also for the new verification method ?
Also, to use "--verify-x509-name" the clients needs to have a version >= 2.3.2 otherwise the connection won´t come up so there is no backwards compatibility with the new directive and version =< 2.3.1 .
May some people out there have some ideas, informations, ...., for this topic ?
Anyway a discussion about that might be interesting.
Greetings,
Erik