Development November 2014

development@lists.ipfire.org

4 participants
8 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

Pull request - updates for 'tar' and 'ethtool'
by Matthias Fischer 02 Dec '14

02 Dec '14

Hi all, I prepared two updates for 'tar' and 'ethtool': tar - Update to 1.28: http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=8c80423c… ethtool - Update to 3.16: http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=191e9a0c… I tested these updates in productive mode. For me, they seem to run fine - if there are problems, please let me know! Regards Matthias -- tails, linux, USB, CD, secure desktop, IRC, truecrypt, tor, onion

2 1

Pull request - grep / file / hdparm / gnupg / fcron / screen
by Matthias Fischer 02 Dec '14

02 Dec '14

Hi all, I prepared updates for several IPFire-components and would like to send a pull request hereby: grep - Update to 2.21: http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=7f88f8f5… file - Update to 5.20: http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=264b8ae7… hdparm - Update to 9.45: http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=068babfb… gnupg - Update to 1.4.18: http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=b92f39bc… fcron - Update to 3.2.0: http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=c814d7b5… screen - Update to 4.2.1: http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=2a219580… If there are problems, please let me know! Regards Matthias -- tails, linux, USB, CD, secure desktop, IRC, truecrypt, tor, onion

2 1

GIT - 'push' / 'pull' not working
by Matthias Fischer 29 Nov '14

29 Nov '14

Hi, since yesterday, while trying to 'push' some updates (grep / hdparm / gnupg) to repo, I'm getting the following errors: ***SNIP*** root@Devel: /home/matz/ipfire-2.x # git push mfischer gnupg ssh: connect to host git.ipfire.org port 22: No route to host fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ***SNAP*** The same happens with - for example - 'git pull origin next'. Testing with 'ping': ***SNIP*** root@Devel: /home/matz/ipfire-2.x # ping git.ipfire.org PING gw03.ipfire.org (178.63.73.248) 56(84) bytes of data. 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=1 ttl=53 time=17.8 ms 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=2 ttl=53 time=17.3 ms 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=3 ttl=53 time=16.8 ms 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=4 ttl=53 time=18.8 ms 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=5 ttl=53 time=16.7 ms 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=6 ttl=53 time=17.6 ms 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=7 ttl=53 time=16.4 ms 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=8 ttl=53 time=17.1 ms 64 bytes from git.ipfire.org (178.63.73.248): icmp_seq=9 ttl=53 time=17.7 ms ^C --- gw03.ipfire.org ping statistics --- 10 packets transmitted, 9 received, 10% packet loss, time 9014ms rtt min/avg/max/mdev = 16.491/17.393/18.810/0.680 ms ***SNAP*** The machine had no problems so far, updates are running ('apt-get ...' is working OK) - in my opinion I didn't change anything. Bug or Feature? Regards Matthias -- tails, linux, USB, CD, secure desktop, IRC, truecrypt, tor, onion

2 1

New Addon Libvirt
by Jonatan Schlag 27 Nov '14

27 Nov '14

Hi Michael, Thanks for your answer. It is a bit hard to tell what went wrong here just by the information I have. Could you please upload the binary packages to somewhere so that I can run it with some debugging tools and see what I can find out? Yes, I have uploaded the packages there: https://drive.google.com/folderview?id=0BwPTTWcqF8fhbnBEN3NjeVJ2c2c&usp=sha… Basically something is trying to access memory that is either not there or does not belong to the application. Check if you have the latest version and maybe there is something in the libvirtd bugtracker. I have the latest version of libvirt but Glibc is form the year 2012. In the libvirt bugtracker is nothing. No, you can update that as well if you want. I guess that you will require a recent version to work with libvirtd any way. Yes, but now qemu is compiled with: --extra-cflags="$(CFLAGS)" and with this option qemu 2.20 (the current version) do not find gcc. I will see what I can do. Thanks for your help. When you need other files or a explanation write me. Best Regards Jonatan PS: @Michael Tremer: Sorry that I send you this E-mail direct . I only answered on your mail, but i do not notice that that this only cause a direct E-Mail to you and not to the Mailing list. You can ignore this Mail. Sorry for this Mistake.

1 0

New Addon Libvirt
by Jonatan Schlag 26 Nov '14

26 Nov '14

Hi at all At first sorry for my awful English, I hope you can understand me. Now to the topic. I would use my Ipfire as a host for some virtual machines. Qemu is as a package available but I would like to manage my virtual machines about libvirt. So libvirt is not available for Ipfire. So I try to compile it for Ipfire and I managed it. The libvirt daemon run on my Ipfire! I must build 4 dependencies (libyajl, libpciaccess, lipdevmapper and util-macros). But now I get a Segmention fault when I type “libvirtd”. This is the error ( I find it in the kernel log files): libvirtd[31422]: segfault at 0 ip a19fe6a1 sp 9bfc4f0c error 4 in libc-2.12.so[a 1983000+174000] This file is part of glibc. I do not know how I can solve this error, but I will do what I can do to help you, say what I must do and will try it. Best Regards Jonatan PS: I am called Yassen in the forum. PSS: Is there a reason why the qemu version is so old ?

2 1

Pull request - various updates
by Matthias Fischer 18 Nov '14

18 Nov '14

2 1

IPFire2.x build hangs already on ICMPv6
by Sascha Kilian 10 Nov '14

10 Nov '14

Hi, after some time i was not here, i am back :) I build IPFire again from Scratch and it already hangs on Nagios 3.0.6 Log Snipp checking for ping... /bin/ping checking for ping6... no checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... I have sended a lfs patch for Nagios and other modules to remove IPV6 Support from IPFire 2.x to compile IPFire 2.x success. I rebuild my Patches and give u the github Repository from me :) If there a other Workaround for this bug? best regards Sascha

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development November 2014