Development February 2013

development@lists.ipfire.org

9 participants
13 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

IPFire 3.x packfire
by Thomas Ebert 10 Mar '13

10 Mar '13

I've tried to use this image: http://people.ipfire.org/~stevee/IPFire_3.x/VM-Images/20121006/i686/ipfire-… But i get the following error while trying these commands: pakfire install pakfire-builder pakfire update Loading installed packages Time: 00:00:17 Traceback (most recent call last): File "/bin/pakfire", line 61, in <module> cli.run() File "/usr/lib/python2.7/site-packages/pakfire/cli.py", line 286, in run return func() File "/usr/lib/python2.7/site-packages/pakfire/cli.py", line 306, in handle_update **args) File "/usr/lib/python2.7/site-packages/pakfire/api.py", line 53, in update allow_vendorchange=allow_vendorchange, allow_archchange=allow_archchange) File "/usr/lib/python2.7/site-packages/pakfire/base.py", line 501, in update t = solver.transaction File "/usr/lib/python2.7/site-packages/pakfire/satsolver.py", line 184, in transaction transaction.Transaction.from_solver(self.pakfire, self) File "/usr/lib/python2.7/site-packages/pakfire/transaction.py", line 235, in from_solver transaction.add(action_name, pkg) File "/usr/lib/python2.7/site-packages/pakfire/transaction.py", line 256, in add action = cls(self.pakfire, pkg) File "/usr/lib/python2.7/site-packages/pakfire/actions.py", line 42, in __init__ binary_package = self.pkg.get_from_cache() File "/usr/lib/python2.7/site-packages/pakfire/packages/solv.py", line 240, in get_from_cache return file.BinaryPackage(self.pakfire, self.repo, path) File "/usr/lib/python2.7/site-packages/pakfire/packages/file.py", line 143, in __init__ self.check() File "/usr/lib/python2.7/site-packages/pakfire/packages/file.py", line 169, in check assert self.format in PACKAGE_FORMATS_SUPPORTED, self.format AssertionError: 5 If needed, i can put logfiles here

3 21

IPFire 2.13 and nfs-server
by Stefan Schantl 01 Mar '13

01 Mar '13

Dear Mailing-List followers, just two days after we've released IPFire 2.13 I've got a bug report on our public IRC channel that the NFS-server wouldn't start any more. So I've performed an update and commited it into my IPFire-2.x Git repository. The changes can be found here: http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=03189f65a5… I've done some basic testing on my IPFire box yet, the rpc.nfsd will start now, but I haven't configured any exports so I'm not able to do a deeper testing. There is still some testing required, before we can merge them into the Main repository and distribute them. I've uploaded a pre-compiled version, for easy testing and would invite everyone to install and test. http://people.ipfire.org/~stevee/testing/nfs-1.2.7-5.ipfire To start testing, download and put the file into the "/opt/pakfire/tmp" directory on your IPFire box. Then extract the files from the compressed archive with "tar -xvf nfs-1.2.7-5.ipfire" and run "./install.sh" or "./update.sh". Please don't forget to provide feedback about your testing. Thanks in advance, Stefan

2 2

Mirror taking a long time
by R. W. Rodolico 28 Feb '13

28 Feb '13

I don't know where I should send this, so I'll do the development list. My syncIPFire script has been running a couple of days, steady. Is this a huge update? I mirror the whole site (ie, full), so I'm assuming with the new release it may take a while, but wanted to make sure of this. NOTE: I have the rsync job bandwidth limited to 512kb/s. I can kill the job and increase the bandwidth if needed. Anyway, just want to make sure this is a huge update and it is correct that it is taking a while. Rod -- R. W. "Rod" Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 http://www.dailydata.net 214.827.2170

2 1

Re: Problem with mISDN
by Arne Fitzenreiter 27 Feb '13

27 Feb '13

das hab ich dich in der Beta noch ausprobiert... Auf jeden fall ist jetzt die Modulsuchreihenfolge wiedermal falsch und er lädt die veralteten Module aus den Kernel (eigentlich sollte er die beim Build löschen aber da musste ja mal wieder an den Pfaden rumgeändert werden und ich habs nicht gemerkt.) lösch mal lib/modules/*-ipfire*/kernel/drivers/isdn/hardware/mISDN lib/modules/*-ipfire*/kernel/drivers/isdn/mISDN und mach dann "depmod -a" und einen reboot, dann sollte mISDN wieder laden. Asterisk hab ich nicht probiert... Arne On 2013-02-26 13:04, Thomas Ebert wrote: > Hello Michael, > > can you log into the system and check the following directory: ls > -al /lib/modules/3.2.38-ipfire/mISDN/ > > These are my files > -rw-r--r-- 1 root root 16240 2013-02-16 17:38 avmfritz.ko > -rw-r--r-- 1 root root 106556 2013-02-16 17:38 hfcmulti.ko > -rw-r--r-- 1 root root 33175 2013-02-16 17:38 hfcpci.ko > -rw-r--r-- 1 root root 37531 2013-02-16 17:38 hfcsusb.ko > -rw-r--r-- 1 root root 27446 2013-02-16 17:38 l1oip.ko > -rw-r--r-- 1 root root 98851 2013-02-16 17:38 mISDN_core.ko > -rw-r--r-- 1 root root 6062 2013-02-16 17:38 mISDN_dsp_kb1ec.ko > -rw-r--r-- 1 root root 71469 2013-02-16 17:38 mISDN_dsp.ko > -rw-r--r-- 1 root root 6025 2013-02-16 17:38 mISDN_dsp_mec2.ko > -rw-r--r-- 1 root root 7269 2013-02-16 17:38 mISDN_dsp_mg2ec.ko > -rw-r--r-- 1 root root 5093 2013-02-16 17:38 mISDN_dsp_octwareec.ko > -rw-r--r-- 1 root root 7610 2013-02-16 17:38 mISDN_dsp_oslec.ko > -rw-r--r-- 1 root root 18136 2013-02-16 17:38 mISDNinfineon.ko > -rw-r--r-- 1 root root 23778 2013-02-16 17:38 mISDNipac.ko > -rw-r--r-- 1 root root 25584 2013-02-16 17:38 mISDNisar.ko > -rw-r--r-- 1 root root 17157 2013-02-16 17:38 mISDN_l1loop.ko > -rw-r--r-- 1 root root 16898 2013-02-16 17:38 netjet.ko > drwxr-xr-x 2 root root 4096 2013-02-16 17:38 octvqe > -rw-r--r-- 1 root root 10826 2013-02-16 17:38 speedfax.ko > -rw-r--r-- 1 root root 19295 2013-02-16 17:38 w6692.ko > -rw-r--r-- 1 root root 31988 2013-02-16 17:38 xhfc.ko > > But i've also a starting error (IPFire 2.13 i586): > [root@ipfire ~]# /etc/init.d/mISDN start > Starting mISDNv2 ... > FATAL: Error inserting mISDN_dsp_oslec > (/lib/modules/3.2.38-ipfire/mISDN/mISDN_dsp_oslec.ko): Unknown symbol > in module, or unknown parameter (see dm[ FAIL ] > > Regards > Thomas > > Am 26.02.2013 11:07, schrieb Michael Liekmeier: > >> Hallo, >> >> after the core update 66 asterisk don't work anymore. >> >> I get the following errow messeg >> >> /etc/init.d/mISDN start >> insmod: can't read 'usrlibasteriskmodules/mISDN_core.ko': No such >> file or directory >> insmod: can't read 'usrlibasteriskmodules/mISDN_dsp.ko': No such >> file or directory >> insmod: can't read 'usrlibasteriskmodules/hfcpci.ko': No such file >> or directory >> >> How can fix this problem? >> >> Regards >> >> Michael >> >> _______________________________________________ >> Development mailing list >> Development(a)lists.ipfire.org >> http://lists.ipfire.org/mailman/listinfo/development [1] > > > > Links: > ------ > [1] http://lists.ipfire.org/mailman/listinfo/development > > _______________________________________________ > Development mailing list > Development(a)lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/development

2 1

Re: Upgrade of essential tools libusb dbus systemd
by Michael Tremer 26 Feb '13

26 Feb '13

On Mon, 2013-02-25 at 23:00 +0100, Thomas Ebert wrote: > Hey Michael, > > thanks for the detailed informations. You are right mostly i needed the > actual libs to compile new software that depends on it. > > Give me some tasks for IPFire 3 and i look what i can do. At the moment > i didn't know the details on it and what working have to be done. The > web-ui isn't my part but on needed binaries and tools + configuration I > can help. Well, let's see what your interests are. There is plenty to do, so I don't really know where to start. Do you have time tonight, to join the IRC channel and have a chat? > Maybe this isn't the right place to talk about it... or not? Contact me > via e-mail or put some informations in this thread how i can help to > make more progress in IPFire 3. I mean by that ... More people = Faster work Yes, this is absolutely the right place to talk about things like these. We appreciate any help. Best, -Michael

2 1

Problem with mISDN
by Michael Liekmeier 26 Feb '13

26 Feb '13

Hallo, after the core update 66 asterisk don't work anymore. I get the following errow messeg /etc/init.d/mISDN start insmod: can't read 'usrlibasteriskmodules/mISDN_core.ko': No such file or directory insmod: can't read 'usrlibasteriskmodules/mISDN_dsp.ko': No such file or directory insmod: can't read 'usrlibasteriskmodules/hfcpci.ko': No such file or directory How can fix this problem? Regards Michael

2 1

Upgrade of essential tools libusb dbus systemd
by Thomas Ebert 25 Feb '13

25 Feb '13

How about to upgrade the tools libusb, dbus and systemd to an actual build? A quick check shows that only a very basic tools on a core installation use the shared libraries: usb_modeswitch linux-gate.so.1 => (0xffffe000) libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0xb777b000) libc.so.6 => /lib/libc.so.6 (0xb7604000) /lib/ld-linux.so.2 (0xb7784000) gpg linux-gate.so.1 => (0xffffe000) libresolv.so.2 => /lib/libresolv.so.2 (0xb770e000) libbz2.so.1.0 => /lib/libbz2.so.1.0 (0xb76fd000) libreadline.so.6 => /usr/lib/libreadline.so.6 (0xb76ca000) libdl.so.2 => /lib/libdl.so.2 (0xb76c5000) libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0xb76bc000) libc.so.6 => /lib/libc.so.6 (0xb7545000) libncurses.so.5 => /usr/lib/libncurses.so.5 (0xb7528000) libtinfo.so.5 => /usr/lib/libtinfo.so.5 (0xb750b000) /lib/ld-linux.so.2 (0xb7728000) AddOn packages with depencies: bluetooth apcupsd usbutils v4l-dvb nut

2 1

Multiple SSL implementations
by Michael Tremer 12 Feb '13

12 Feb '13

Hello, I think it is time to discuss a thing, that has been stuck in my head for some time now: We have too many SSL implementations in the system. And as we are already discussion what we can remove from the distribution (Xen), I'd like to think about the SSL libraries. IPFire 3 comes with openssl, GnuTLS, nss and polarssl. They all basically implement the same protocols, but they differ a bit in their interfaces, so a lot of projects prefer the one or an other. When we had the Lucky Thirteen problem last week, I had to patch all four libraries. That's redundant work and I don't see any sense in that. I even see this as a security issue, because it is not easy to keep track of security issues in all libraries. I would like to think about how we can get rid of some of these libraries: * openssl We cannot get rid of this one because openssl is widely used and I tend to think that it is the de-facto standard library. A bit of a problem is the GPL-incompatible license. * GnuTLS This is a much better choice in terms of licenses and GnuTLS is also widely used. I'd like to keep it. * nss The reason we have this is that RedHat started to move a lot of their own software to it because nss is FIPS certified. However, this certification is not important to us at this point in time and nss is only used by glibc, apr-util and curl. All of them could be compiler either without nss or with an other SSL library. * polarssl This library came into the distribution very recently and is used by the authoritative powerdns server. As far as I am aware, powerdns cannot use any other library. Conclusively, we can't (or don't want) to get rid of openssl, GnuTLS and polarssl. But nss looks like a candidate for me. Opinions? -Michael

4 6

ipfire dutch translation
by H. Horsten 12 Feb '13

12 Feb '13

Hi, Please find attached the dutch translation files for the webgui and installation program. Regards, Hans

3 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development February 2013