Development July 2013

development@lists.ipfire.org

6 participants
6 discussions

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: pyload
by Daniel Weismüller 25 Jul '13

25 Jul '13

Oh ok. So we need someone other who may do the necessary changes. Is here a volunteer who could made this for us? ;) - Daniel Am Mittwoch, den 24.07.2013, 19:45 +0200 schrieb Thomas Ebert: > Hi Daniel, > > sorry i don't think so. > > Regards Thomas > > Am 24.07.2013 15:14, schrieb Daniel Weismüller: > > Hi Thomas > > do you think you're able to implement the new suggestions from Michael? > > > > - Daniel > > > > > > Am Donnerstag, den 04.07.2013, 12:51 +0200 schrieb Michael Tremer: > >> Hi Thomas, > >> > >> two things about this: > >> > >> a) The rootfile is (again) completely messed up. The build system will > >> complain at the end that it could not compare it to what has been > >> generated in the build. > >> > >> b) The initscript does not seem very well done. Despite that some > >> information has not been properly filled out in the header and in the > >> lines that will be prompted on the terminal at boot up, the start and > >> stop process of pyload does not look very good. > >> > >> If there is no such daemon, then please write a helper daemon that can > >> be properly killed. > >> > >> -Michael > >> > >> On Wed, 2013-07-03 at 15:30 +0200, Thomas Ebert wrote: > >>> Hi Daniel, > >>> > >>> i've updated the init.d script and changed the default download folder > >>> to /var/pyload/Downloads. > >>> I've deleted the old branch pyload in my reposistory and created a new > >>> one with the same name. > >>> > >>> Regards > >>> Thomas > >>> > >>> Am 2013-07-02 20:12, schrieb Thomas Ebert: > >>>> Hi Daniel, > >>>> > >>>> i don't think that it's a big case to implement that things. > >>>> > >>>> I'll add these suggestions and make a new upload to my repository. > >>>> > >>>> Regards > >>>> Thomas > >>>> > >>>> Am 2013-07-02 14:57, schrieb Daniel Weismüller: > >>>>> Thomas, > >>>>> > >>>>> do you think you're able to implement the suggestions from Michael? > >>>>> > >>>>> - Daniel > >>>>> > >>>>> > >>>>> > >>>>> Am Montag, den 17.06.2013, 11:04 +0200 schrieb Daniel Weismüller: > >>>>>> Hi > >>>>>> > >>>>>> Are there some news about pyload? > >>>>>> What about the suggestions? Did someone try to implement them? > >>>>>> > >>>>>> - Daniel > >>>>>> > >>>>>> > >>>>>> Am Dienstag, den 04.06.2013, 17:07 +0200 schrieb Michael Tremer: > >>>>>>> Hi, > >>>>>>> > >>>>>>> yeah, I would also suggest that the data directories are moved to > >>>>>> some > >>>>>>> subdirectory of /var, because a full root device will kill the > >>>>>> firewall > >>>>>>> box eventually. > >>>>>>> > >>>>>>> I also checkout out the source and that looks pretty much okay. > >>>>>> Some > >>>>>>> files which don't necessarily need to be in the packages like all > >>>>>> the > >>>>>>> *.so links, but still. > >>>>>>> > >>>>>>> Please replace the initscript by something proper. You will find > >>>>>> a > >>>>>>> template at src/initscripts/init.d/template. Except that, things > >>>>>> look > >>>>>>> good. > >>>>>>> > >>>>>>> -Michael > >>>>>>> > >>>>>>> On Fri, 2013-05-31 at 09:14 +0800, Fajar Ramadhan wrote: > >>>>>>>> Hi there, > >>>>>>>> > >>>>>>>> I have same problem just like ummeegge - /srv is too small > >>>>>> (which is > >>>>>>>> only 2 Gb here) to properly hold all downloaded files. So I > >>>>>> change its > >>>>>>>> download directory to /var/pyload and everything just works > >>>>>> fine for > >>>>>>>> me. > >>>>>>>> > >>>>>>>> One thing to remember : after you change pyload configurations, > >>>>>> you > >>>>>>>> should do manual pyload restart from web interface Administrate > >>>>>> -> > >>>>>>>> Restart pyLoad. pyLoad configurations wont change if you do > >>>>>> restart > >>>>>>>> using init script. > >>>>>>>> > >>>>>>>> I've tested some plugins such as download scheduler and youtube > >>>>>> (I > >>>>>>>> love youtube plugin since its able to download HD videos > >>>>>>>> automagically) and its work like a charm. Now I have > >>>>>> transmission and > >>>>>>>> pyLoad running in my box, great! :) > >>>>>>>> > >>>>>>>> Regards, > >>>>>>>> > >>>>>>>> - Fajar R. > >>>>>>>> > >>>>>>>>> Subject: Re: pyload > >>>>>>>>> From: ummeegge(a)ipfire.org > >>>>>>>>> Date: Thu, 30 May 2013 17:52:19 +0200 > >>>>>>>>> To: development(a)lists.ipfire.org > >>>>>>>>> > >>>>>>>>> Hi Stefan, > >>>>>>>>> so for the first the compiled binary (unrar) can be found in > >>>>>> here > >>>>>>>> http://people.ipfire.org/~ummeegge/unrarsrc/ > >>>>>>>>> i have installed now pyload and all the dependencies and for > >>>>>> the > >>>>>>>> first it looks very good. I could access the pyload > >>>>>> webinterface with > >>>>>>>> http://<IP-IPFire>:8086 and all menues are available. The start > >>>>>> of > >>>>>>>> different downloads over the "Add" button gives me also the > >>>>>>>> possibility to create new folders in the Download section (have > >>>>>> tested > >>>>>>>> it now only with "Queue" not with "Collector", under the tab > >>>>>> "Home" > >>>>>>>> the overview of active downloads are displayed, also the > >>>>>> "Queue" tab > >>>>>>>> with his small function icons worked good for me. > >>>>>>>>> The Logs section works also good and give a nice informative > >>>>>>>> overview. > >>>>>>>>> The administration tabs (Logout, Administrate, Info) on the > >>>>>> right > >>>>>>>> top of the WUI do their work. > >>>>>>>>> I have had some problems by changing the config´s, the > >>>>>> default > >>>>>>>> download directory is located under /srv which wasn´t the best > >>>>>> place > >>>>>>>> for me cause mostly disc space is under /var or /mnt/harddisk > >>>>>> so i > >>>>>>>> tried to change it over the WUI but the changes doesn´t take > >>>>>> affect, > >>>>>>>> also the WUI seems to work buggy after this changes. I need to > >>>>>> make > >>>>>>>> a /etc/init.d/pyload stop/start (the init script from pyload > >>>>>> seems not > >>>>>>>> to work with restart) after this all went good again and the > >>>>>> new > >>>>>>>> download folder was accepted. So it seems like configuration > >>>>>> changes > >>>>>>>> needs to have an pyload restart, that the changes takes affect > >>>>>> ? > >>>>>>>>> I think there is no reconnect.sh script available or may i > >>>>>> have > >>>>>>>> overseen it... > >>>>>>>>> The first impression of pyload is good but some further tests > >>>>>> might > >>>>>>>> be important i think. > >>>>>>>>> Thanks for your good work and greetings > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Erik > >>>>>>>>> > >>>>>>>>> Am 30.05.2013 um 10:32 schrieb Erik K.: > >>>>>>>>> > >>>>>>>>>>> Hi Stefan and Daniel, > >>>>>>>>>>> @Stefan i think unrar is not available in Pakfire, but i > >>>>>> compile > >>>>>>>> it at this time. If the build process is finished, i upload it > >>>>>> to my > >>>>>>>> home directory. I will go then also for some tests. > >>>>>>>>>>> Feedback will come soon. > >>>>>>>>>>> > >>>>>>>>>>> Greetings > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> Erik > >>>>>>>>>>> > >>>>>>>>>>> Am 29.05.2013 um 21:53 schrieb Stefan Schantl: > >>>>>>>>>>> > >>>>>>>>>>>> Hello Daniel, > >>>>>>>>>>>> > >>>>>>>>>>>> thanks for testing the packages, are they also affected > >>>>>> by the > >>>>>>>> "/etc/init.d/" bug ? > >>>>>>>>>>>> All mailing list followers, please join the team and test > >>>>>> the > >>>>>>>> pyload package and it's dependencies. > >>>>>>>>>>>> The installation of the packages is pretty easy: > >>>>>>>>>>>> > >>>>>>>>>>>> * Install sqlite, pycurl and unrar by using pakfire. > >>>>>> "pakfire > >>>>>>>> install sqlite pycurl unrar" or do it over the WUI. > >>>>>>>>>>>> * Download pyload and the dependecies from here: > >>>>>>>> http://people.ipfire.org/~stevee/testing/ > >>>>>>>>>>>> * Put them on your IPFire into the "/opt/pakfire/tmp" > >>>>>> directory. > >>>>>>>>>>>> * Unextract the downloaded files with tar - "tar -xvf > >>>>>>>> file.ipfire" and install it with "./install.sh" > >>>>>>>>>>>> * Be sure to install the pyload package at the end - > >>>>>> pyload > >>>>>>>> automatically will be started. > >>>>>>>>>>>> The GUI, as Daniel already documented will be available > >>>>>> at > >>>>>>>> "http://<ip-of-your-ipfire>:8086", the default credentials are > >>>>>>>> "pyload" with the password "secret". > >>>>>>>>>>>> Please report any problems or errors, to get rid of them > >>>>>> and to > >>>>>>>> speed up the final merge into the main distribution. > >>>>>>>>>>>> A big thanks, > >>>>>>>>>>>> > >>>>>>>>>>>> - Stefan > >>>>>>>>>>>> > >>>>>>>>>>>>> Yesterday I've tested the pyload packages from Stevee. > >>>>>>>>>>>>> http://people.ipfire.org/~stevee/testing/ > >>>>>>>>>>>>> > >>>>>>>>>>>>> Installationorder: leptonica, tesseract-ocr, > >>>>>> python-pyOpenSSL, > >>>>>>>>>>>>> python-Jinja2, python-Beaker, python-thrift, > >>>>>> python-simplejson, > >>>>>>>>>>>>> python-pycrypto, python-pytesser, python-PIL, > >>>>>>>> python-BeautifulSoup, > >>>>>>>>>>>>> spidermonkey, sqlite, pycurl, unrar, pyload > >>>>>>>>>>>>> > >>>>>>>>>>>>> sqlite and pycurl you find in the pakfire. > >>>>>>>>>>>>> > >>>>>>>>>>>>> After I've installed everything the pyload webinterface > >>>>>> was > >>>>>>>> reachable on > >>>>>>>>>>>>> ipfire:8086. > >>>>>>>>>>>>> > >>>>>>>>>>>>> username: pyload > >>>>>>>>>>>>> password: secret > >>>>>>>>>>>>> > >>>>>>>>>>>>> At first pyload seems to work fine. Also automatic unrar > >>>>>> and > >>>>>>>> unzip of > >>>>>>>>>>>>> compressed files work fine. > >>>>>>>>>>>>> > >>>>>>>>>>>>> The only thing is that every one minute there is the > >>>>>> following > >>>>>>>> entry in > >>>>>>>>>>>>> the logfile. > >>>>>>>>>>>>> > >>>>>>>>>>>>> 149 28.05.2013 08:49:34 ERROR Error executing hooks: > >>>>>> 'NoneType' > >>>>>>>> object > >>>>>>>>>>>>> has no attribute '__getitem__' > >>>>>>>>>>>>> 150 28.05.2013 08:50:34 ERROR Error executing hooks: > >>>>>> 'NoneType' > >>>>>>>> object > >>>>>>>>>>>>> has no attribute '__getitem__' > >>>>>>>>>>>>> 151 28.05.2013 08:51:34 ERROR Error executing hooks: > >>>>>> 'NoneType' > >>>>>>>> object > >>>>>>>>>>>>> has no attribute '__getitem__' > >>>>>>>>>>>>> 152 28.05.2013 08:52:34 ERROR Error executing hooks: > >>>>>> 'NoneType' > >>>>>>>> object > >>>>>>>>>>>>> has no attribute '__getitem__' > >>>>>>>>>>>>> > >>>>>>>>>>>>> Maybe someone could verify it. > >>>>>>>>>>>>> > >>>>>>>>>>>>> - Daniel > >>>>>>>>>>>>> > >>>>>>>>>>>>> _______________________________________________ > >>>>>>>>>>>>> Development mailing list > >>>>>>>>>>>>> Development(a)lists.ipfire.org > >>>>>>>>>>>>> http://lists.ipfire.org/mailman/listinfo/development > >>>>>>>>>>>> _______________________________________________ > >>>>>>>>>>>> Development mailing list > >>>>>>>>>>>> Development(a)lists.ipfire.org > >>>>>>>>>>>> http://lists.ipfire.org/mailman/listinfo/development > >>>>>>>>>> _______________________________________________ > >>>>>>>>>> Development mailing list > >>>>>>>>>> Development(a)lists.ipfire.org > >>>>>>>>>> http://lists.ipfire.org/mailman/listinfo/development > >>>>>>>>> _______________________________________________ > >>>>>>>>> Development mailing list > >>>>>>>>> Development(a)lists.ipfire.org > >>>>>>>>> http://lists.ipfire.org/mailman/listinfo/development > >>>>>>>> _______________________________________________ > >>>>>>>> Development mailing list > >>>>>>>> Development(a)lists.ipfire.org > >>>>>>>> http://lists.ipfire.org/mailman/listinfo/development > >>>>>>> _______________________________________________ > >>>>>>> Development mailing list > >>>>>>> Development(a)lists.ipfire.org > >>>>>>> http://lists.ipfire.org/mailman/listinfo/development > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Development mailing list > >>>>>> Development(a)lists.ipfire.org > >>>>>> http://lists.ipfire.org/mailman/listinfo/development > >>>> _______________________________________________ > >>>> Development mailing list > >>>> Development(a)lists.ipfire.org > >>>> http://lists.ipfire.org/mailman/listinfo/development > >>> _______________________________________________ > >>> Development mailing list > >>> Development(a)lists.ipfire.org > >>> http://lists.ipfire.org/mailman/listinfo/development > >> _______________________________________________ > >> Development mailing list > >> Development(a)lists.ipfire.org > >> http://lists.ipfire.org/mailman/listinfo/development > > > > >

1 0

Re: pyload
by Erik K. 24 Jul '13

24 Jul '13

> > Hi Stefan and Daniel, > @Stefan i think unrar is not available in Pakfire, but i compile it at this time. If the build process is finished, i upload it to my home directory. I will go then also for some tests. > > Feedback will come soon. > > Greetings > > > Erik > > Am 29.05.2013 um 21:53 schrieb Stefan Schantl: > >> Hello Daniel, >> >> thanks for testing the packages, are they also affected by the "/etc/init.d/" bug ? >> >> All mailing list followers, please join the team and test the pyload package and it's dependencies. >> >> The installation of the packages is pretty easy: >> >> * Install sqlite, pycurl and unrar by using pakfire. "pakfire install sqlite pycurl unrar" or do it over the WUI. >> >> * Download pyload and the dependecies from here: http://people.ipfire.org/~stevee/testing/ >> >> * Put them on your IPFire into the "/opt/pakfire/tmp" directory. >> >> * Unextract the downloaded files with tar - "tar -xvf file.ipfire" and install it with "./install.sh" >> >> * Be sure to install the pyload package at the end - pyload automatically will be started. >> >> The GUI, as Daniel already documented will be available at "http://<ip-of-your-ipfire>:8086", the default credentials are "pyload" with the password "secret". >> >> Please report any problems or errors, to get rid of them and to speed up the final merge into the main distribution. >> >> A big thanks, >> >> - Stefan >> >>> Yesterday I've tested the pyload packages from Stevee. >>> http://people.ipfire.org/~stevee/testing/ >>> >>> Installationorder: leptonica, tesseract-ocr, python-pyOpenSSL, >>> python-Jinja2, python-Beaker, python-thrift, python-simplejson, >>> python-pycrypto, python-pytesser, python-PIL, python-BeautifulSoup, >>> spidermonkey, sqlite, pycurl, unrar, pyload >>> >>> sqlite and pycurl you find in the pakfire. >>> >>> After I've installed everything the pyload webinterface was reachable on >>> ipfire:8086. >>> >>> username: pyload >>> password: secret >>> >>> At first pyload seems to work fine. Also automatic unrar and unzip of >>> compressed files work fine. >>> >>> The only thing is that every one minute there is the following entry in >>> the logfile. >>> >>> 149 28.05.2013 08:49:34 ERROR Error executing hooks: 'NoneType' object >>> has no attribute '__getitem__' >>> 150 28.05.2013 08:50:34 ERROR Error executing hooks: 'NoneType' object >>> has no attribute '__getitem__' >>> 151 28.05.2013 08:51:34 ERROR Error executing hooks: 'NoneType' object >>> has no attribute '__getitem__' >>> 152 28.05.2013 08:52:34 ERROR Error executing hooks: 'NoneType' object >>> has no attribute '__getitem__' >>> >>> Maybe someone could verify it. >>> >>> - Daniel >>> >>> _______________________________________________ >>> Development mailing list >>> Development(a)lists.ipfire.org >>> http://lists.ipfire.org/mailman/listinfo/development >> >> _______________________________________________ >> Development mailing list >> Development(a)lists.ipfire.org >> http://lists.ipfire.org/mailman/listinfo/development >

5 9

Strongswan 5 issues in IPFire 2.13
by Michael Tremer 14 Jul '13

14 Jul '13

Hey, when IPFire 2.13 was released, the latest version of strongswan was shipped with it. Apparently, some people have problems operating their VPN connections with it. This is a brief summary from my point of view: The first version with these changes that might cause trouble has been released in August 2012 with a big headline which said: Testers needed. * http://planet.ipfire.org/post/testers-needed-strongswan-5-0-0 * http://lists.ipfire.org/pipermail/development/2012-August/000039.html My mail on the mailing list states: > It should not require any manual interaction at all. Please install > and give me feedback about the connection stability and the > interoperability with other (proprietary) implementations. It's as if someone had known... If you think, we didn't have people who actually tested this, you are wrong. There were a lot of people and the reports I got of them were all like: "Yeah, this made my VPN tunnels more stable". Especially when the configuration of one connection has been edited, the other connections remained established all the time. A big advantage over the implementation in IPFire 2.11! Eight days before the final version of IPFire 2.13 was released, people started complaining. It was not a real bug report, but just a shout out "something went wrong, I could not be bothered, so I downgraded!". No technical details, no logs, no what-so-ever. Since the release, a bunch of more people complained about similar problems. Again, no one provided (or was willing to provide) information that helps to solve the problem. Nobody was even bothered to create a proper bug report in bugzilla. My VPN connections run for more than six months with strongswan 5 and I never had any problems since then. If someone really has interest in solving this, maybe it is time that you start the action and help the developers. This is not a project where you can tell people what they should do (for you). This is an Open Source project - so everyone is able to read the source code, check what changes have been made and to provide a fix. -Michael

4 5

Problems with Core 70 and OpenVPN N2N
by Erik K. 12 Jul '13

12 Jul '13

Hi all, have tried today Core 70 and OpenVPN N2N and i have had problems to establish the connection. The infrastructure: IPFire (remote) <--> Router <--> [ Internet ] <--> (local) Router <--> (local) IPFire So both sides with double NAT. The log messages gives me the following back Jul 11 18:17:35 ipfire Testn2n[13565]: UDPv4 link remote: 192.168.20.2:5329 Jul 11 18:19:09 ipfire Testn2n[13808]: TLS Error: client->client or server->server connection attempted from 192.168.20.2:5329 Jul 11 18:18:01 ipfire Testn2n[13565]: event_wait : Interrupted system call (code=4) have never seen this message (in the middle) before... So i looked to the configuration file on the TLS-client where the "Remote Host/IP" was stated with the 192.168.20.2 (red0 IP), i changed it then to the remote IP (in versions before Core 70 this was not necessary) and the following log output was stated. Jul 11 20:22:49 ipfire Testn2n[6875]: Expected Remote Options hash (VER=V4): '9e986809' Jul 11 20:22:49 ipfire-bbach Testn2n[[6875]: UDPv4 link remote: 172.11.xx.xx:5329 Jul 11 20:23:50 ipfire Testn2n[[6875]: [UNDEF] Inactivity timeout (--ping-restart), restarting Looks like a closed firewall. Portforwarding from both upstream routers to IPFire was made, outgoing FW was in mode 0 . May some one have an idea what´s causing this problem ? Greetings Erik

2 3

connections.cgi: iptables connection tracking.
by Kay-Michael Köhler 05 Jul '13

05 Jul '13

Hello everyone i'm going to start development on connections.cgi to have some kind of sorting at "iptables connection tracking" (status->connections) I think it is a good idea to have the following (asc/desc) sort options: "Protocol" "Source IP:Port" "Destination IP Port" "Connection status" If you guys agree it would be a please for me to share and post the patch here when i'm done. Regards Kay-Michael

2 12

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development July 2013