Development August 2012

development@lists.ipfire.org

7 participants
12 discussions

IPFire "thirteen"
by Michael Tremer 04 Sep '12

04 Sep '12

Hello, this is to announce the first test release for IPFire 2.13 with codename "thirteen". So what has been going on? The IPFire project is going to release another release of IPFire 2. This is kind of inevitable because we feel that the current base is getting a bit old and that we should refresh some of the components to make life easier in the future. IPFire 2 will have to live for a long time until there is a working release of IPFire 3. Updates components: The Linux kernel Arne has been working on updating to the latest LTS kernel, which is Linux 3.2. It is maintained by Ben Hutchings for a couple of years, so this is a good base to build our little system on. The mission critical drivers (networking, media and some more) have been picked from the Linux 3.5 release (compat-wireless 3.5.x) for better hardware support. I will leave out what the benefits are. You all know. Glibc update Glibc has been updated to the 2.12 branch. This is a huge step (from 2.3.6) which brings us a lot of advantages. New software compiles much better without annoying patches, software runs much master and a lot of security holes have been closed. Glibc is compiled with the most optimization as possible. We don't expect this to break anything, but you never know. It is the biggest change that has ever been done in user space since the release of IPFire 2.1. GCC + binutils (aka toolchain) The basic toolchain components have been updated. Mainly: GCC 4.4.7, binutils 2.22. Advantages: More speed (in compiling and code execution), compiler bugs fixes. Enables us to use some hardening features in the kernel. The toolchain may now be cross-compiled on x86_64 which get us rid of the requirement of a 32bit host system for building IPFire. Although IPFire remains i586. The same cross-compiling thing works for ARM, which is even more important because there are not many distributions supporting armv5tel. Stripping binaries has been improved. More basic system libraries and tools have been updated: zlib 1.2.7, ncurses 5.9, bash 3.2 (with a bunch of patches), readline 6.2, iproute 3.5.1, gettext 0.18.1.1, ccache 3.1.8, less 443, file 5.11, texinfo 4.13a and some more which I have completely forgotten. PCRE The PCRE library now comes in two flavours. The first version is a compat version for tools which have been compiled against the previous package. The new one comes with a JIT compiler, which makes processing regular expressions much faster. The URL filter feature may benefit from that the most. rrdtool Has been updated and draws its graphs with help of cairo/pango/pixman. This is much faster and looks a bit prettier. :D grub has got a new patchset. Some packages which have been unused/unusable for some time have been removed: resier4progs, libaal, hddtemp, applejuice, iptstate, splix. glib(2), fontconfig and freetype are not a package anymore. These are essential for a huge number of addons. ---- Well, these are some things and now we need you all for testing. As you may have guessed, some of the changes are scary and so we need the evidence that everything works pretty well. You will only find an ISO image and no update, because a) the update has not been built, yet and b) we don't want you to crash your production systems. Please use your testing hardware of virtual machines. The first is the better option. Don't forget to report any bugs and also give feedback if you are not experiencing any serious problems. http://people.ipfire.org/~ms/unsupported/ipfire-2.11-thirteen/ Michael

2 2

Re: IPFire2 thirteen won't install
by Michael Tremer 04 Sep '12

04 Sep '12

On Fri, 2012-08-31 at 16:32 +0200, Daniel Weismüller wrote: > Yes, this worked! > > Thirteen looks fine at a first look. > All standart services starting. Hopefully. > + webif looks as usual; graphs are all available and pretty > + clamav, squid, url-filter, upd-accelerator, works fine Good. > - core 61 is shown What's wrong with that? > - linux-pae download wrong kernel (2.6.x); after uninstalling it the > bootmenu still shows linux-pae There is still no new repository for IPFire 2.13. Until that has been set up, there is no PAE kernel.

3 2

IPFire2 thirteen won't install
by Daniel Weismüller 31 Aug '12

31 Aug '12

Hi I've tested the new thirteen and can't install it. Wheather in Virtualbox nor on a native machine. The installationprocedure don't find an HDD for installation. In my opinion the error lies in the script /bin/mountdest.sh If I edit the line 26 and remove "-or -name vd*" the script works fine and the installtionprocedure won't crash. - Daniel -- __________________________________________ You need a firewall? Easy to use? Powerful? Modular? For free? www.ipfire.org An Open Source Firewall Solution

2 1

IPFire and FireFilter (aka Copfilter)
by Erik K. 25 Aug '12

25 Aug '12

Hi all, i have found the latest news on the planet from Michael --> http://planet.ipfire.org/post/ipfire-and-firefilter-aka-copfilter and i think this is a great idea. This supplement fills up a gap in IPFire. I hope the Copfilter developers are joining the IPFire project to release their good work also for this platform. Also i have seen in the last time a lot of people coming from IPCop to IPFire Forum and they was asking for additional solutions like Copfilter for IPFire. There is a survey in the Copfilter forum for this idea, so may a similar thread in the IPFire forum can be also a good idea. What do you think about this ? Greetings Erik

1 0

New toolchain release available
by Michael Tremer 24 Aug '12

24 Aug '12

Hey, I just wanted to inform you that the new toolchains with the new compiler and glibc have been uploaded. Content: * GCC 4.4.7 * binutils 2.22 * glibc 2.12 This is for use with the glibc-update2 branch. http://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=shortlog;h=refs/heads/g… 42.6M http://source.ipfire.org/toolchains/ipfire-2.11-toolchain-5-i586.tar.gz 45.1M http://source.ipfire.org/toolchains/ipfire-2.11-toolchain-5-armv5tel.tar.gz Michael

1 0

Dropping versatile kernel
by Michael Tremer 13 Aug '12

13 Aug '12

Hi Arne, you just dropped the Linux kernel which was compiled for ARM Versatile from IPFire 2.x: http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=c94c1fa5574230d9edbe… The reasons are that there is no use for it except virtual environments with QEMU. However, these are very slow and pretty much unusable. Do you think there are any other reasons to keep the versatile kernel in IPFire 3? I guess we could drop it, too. A benefit would be a massive increase in build time of the kernels for ARMv5tel which is more than 8 hours on Pandaboard. Michael

2 2

Re: SECURITY ADVISORY: outgoing firewall accepts packets unintendedly
by Michael Tremer 12 Aug '12

12 Aug '12

Removed that unused variable. http://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=commitdiff;h=4e2bce1804… On Thu, 2012-08-09 at 11:58 +0200, Bernhard Bitsch wrote: > Why are there settings for chain policy? They are not used and cannot be set by > a iptables command, but would be useful.

1 0

Re: Re: [Development] Strongswan 5.0.0
by Mieszko Ślusarczyk 07 Aug '12

07 Aug '12

Here is working config for iOS devices (iPhone, iPod Touch, iPad). refer to the article; http://wiki.ipfire.org/de/configuration/services/ipsec/ios /etc/ipsec.user.conf is little different ("rightsubnet=vhost:%no,%priv" should be replaced with rightsubnet=<normal ip notation for subnet (like 10.0.0.0/24)>) Also "pfs=no" parameter is useless (but harmless to keep) I removed "leftfirewall=yes" as well Complete /etc/ipsec.user.conf (replace stuff in <> brackets): conn <conectionname> keyexchange=ikev1 authby=xauthrsasig xauth=server left=<ipfire fqdn> leftsubnet=0.0.0.0/0 leftcert=/var/ipfire/certs/hostcert.pem right=%any rightsubnet=<subnet for ipsec vpn(different than green, blue, orange or openvpn subnet; for example:10.0.0.0/24)> rightsourceip=<internal ip address(not in green, blue, orange or openvpn subnet; for example: 10.0.0.11/24)> rightcert=/var/ipfire/certs/<conectionname>cert.pem auto=add lefthostaccess=yes compress = yes -- Mieszko Ślusarczyk Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

1 0

[Development] Strongswan 5.0.0
by Michael Tremer 07 Aug '12

07 Aug '12

Hello, as Core Update 61 has now been released, it is time to go on with developments for the next one: I have updated strongswan to version 5.0.0 which finally removes the pluto daemon which was responsible for IKEv1 connections. However, pluto has gotten very old and was created in the beginnings of the IPsec for Linux developments back in freeswan times. charon was introduced by strongswan some time ago when IKEv2 connections got supported. It handles IKEv1 connections as well as IKEv2 connections since strongswan version 5.0.0. What are the benefits for IPFire? As mentioned earlier, pluto is very old and got very hard to maintain. There have been problems with VPNs that terminate at hosts with dynamic IP addresses, so we needed to restart the entire IPsec subsystem in intervals of 5 minutes. This caused some trouble in stability terms. charon handles those dynamic endpoints much better without the need to restart anything. Connections may now be added and removed smoothly and in total there should be much more connection stability. There is also some new code for hybrid IPsec VPNs which can be used with Android 4 and maybe Apple iOS. I have not done any investigation on this topic, because I am not interested, but hopefully somebody else gives it a shot. I have now packaged the changes into a small package which wants to be installed on your system. http://people.ipfire.org/~ms/unsupported/core-upgrade-2.11-strongswan.ipfire 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. I am looking forward to it. Michael P.S. If you reply to this mail make sure to keep both mailing lists.

2 6

SECURITY ADVISORY: outgoing firewall accepts packets unintendedly
by Michael Tremer 07 Aug '12

07 Aug '12

Hello, there is a problem in the outgoing firewall if it is used in mode 1. Packets are accepted from blue even if there is no rule for the MAC address of the sender. This problem has got a medium severity and does not affect any other configuration of the outgoing firewall and does not occur when no blue network interface exists. There is a fix available: http://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=commitdiff;h=78a14abf81… Please install and test. I am not going to repeat this request anymore. Michael

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development August 2012