Development June 2014

development@lists.ipfire.org

7 participants
6 discussions

Introducing DDNS
by Michael Tremer 21 Jun '16

21 Jun '16

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…

6 18

DynDNS support for ddns project.
by Stefan Schantl 16 Jun '14

16 Jun '14

Hello guys, i've created a patch for the Dynamic DNS client for IPFire. (http://git.ipfire.org/?p=oddments/ddns.git;a=summary) My patch will add support for the very popular "dyndns.org" provider. However I wasn't able to test my changes, because I don't have any account there and I seems new members have to purchase to use use it. So, I need your help to test my changes and finally be able to support that provider in the next major version of IPFire. Best regards, Stefan

2 3

Re: GitHub Pull Requests?
by Stefan Ferstl 15 Jun '14

15 Jun '14

Hi Michael Thanks for the information. I created an issue in Bugzilla [1] and linked it to the PR on GitHub. Cheers, Stefan [1] https://bugzilla.ipfire.org/show_bug.cgi?id=10552 On Sat, Jun 14, 2014 at 7:55 PM, Michael Tremer <michael.tremer(a)ipfire.org> wrote: > Hi Stefan, > > thanks for your submission. > > Indeed GitHub Pull requests are not the best way for us to handle those. > GitHub is still not able to send us notifications when a new pull > request is created. We don't use it for anything else than just > mirroring our repositories to there. > > That means you can use pull requests, but always open a bug report in > our own bugtracker and reference both to each other. In that way, we can > track GitHub pull requests just as we do it with everything else like > assinging them to people who will take care of those and you can use > your own repositories on GitHub. > > If you could please do that we can start looking into the matter. > > Best, > -Michael > > On Sat, 2014-06-14 at 19:01 +0200, Stefan Ferstl wrote: >> Hi >> >> I recently had some troubles with my OpenVPN certificates on IPFire. I >> could easily fix the problem with a one-liner in OpenVPN's "verify" >> script. >> Additionally, I filed a pull request [1] on GitHub with that solution. >> Since there hasn't been any reaction at all whatsoever for more than >> one month now, I want to ask if I have to submit a patch over a >> different channel than via GitHub. >> >> >> Cheers, >> Stefan >> >> >> [1] https://github.com/ipfire/ipfire-2.x/pull/25 >> _______________________________________________ >> Development mailing list >> Development(a)lists.ipfire.org >> http://lists.ipfire.org/mailman/listinfo/development >

1 0

GitHub Pull Requests?
by Stefan Ferstl 14 Jun '14

14 Jun '14

Hi I recently had some troubles with my OpenVPN certificates on IPFire. I could easily fix the problem with a one-liner in OpenVPN's "verify" script. Additionally, I filed a pull request [1] on GitHub with that solution. Since there hasn't been any reaction at all whatsoever for more than one month now, I want to ask if I have to submit a patch over a different channel than via GitHub. Cheers, Stefan [1] https://github.com/ipfire/ipfire-2.x/pull/25

2 1

core 78 test
by Daniel Weismüller 05 Jun '14

05 Jun '14

hi today morning i installed the c78 and here are my testresults. First of all the proxy seems to work but further tests show me that there are some problems with the redirectors. - The url-filter do nothing anymore. - squidclamav seems to work partitially. If i call an eicar-testvirus site "http://www.testvirus.de/testvirus/eicar.com" i've been redirected to "http://127.0.0.1:81/clwarn.cgi?url=http://www.testvirus.de/testvirus/eicar.…" but my firefox told me that he can't get an connection. "Firefox kann keine Verbindung zu dem Server unter 127.0.0.1:81 aufbauen." I'm ready to do further test but need instructions. ;) - Daniel

1 2

More Proxy Problems.
by Arne Fitzenreiter 02 Jun '14

02 Jun '14

Hi, squid 3.4.5 has serious problems with the redirektor responses from the accel and squidclamav. I think the squid developers have again changed important things without a noticeable note like at the lm-auth support drop. I will again remove the core78 from testing tree. Arne

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development June 2014