The IPFire development team has just released the 61st core update for IPFire 2.11.

This update brings a lot of exciting changes, new features and several bug fixes. We have had many different contributors who have sent us patches and we’d like to thank them very much for their help.

Improved OpenVPN support

Since IPFire 2.11, OpenVPN net2net (N2N) or site2site (S2S) connections are supported. Here are some of the exciting new features:

  • Static routes may be defined for OpenVPN clients (Nico Prenzel).
  • Connections can now be renamed when importing them.
  • OpenVPN N2N connections are displayed with their status on the index page.
  • Optional client-config-dir (CCD) is supported which enables the option to add configuration parameters for a single client connection.

Connection tracking

On the connections page, you can now see how much traffic has been transfered over a single connection. There is also different highlighting for multicast traffic.

Various contributions

Jan Lentfer updated some parts of the build toolchain (bison, flex, m4) as well as PAM.
Thanks to Bernhard Bitsch, there is now a form validation check for the upstream proxy on the proxy configuration page.
Roger Devaux reported a problem with creating proxy reports when the logfiles had a size of several tens of gigabytes which has now been fixed.

Packages which have been updated for security reasons

  • php 5.3.14 – over 30 bugs have been fixed

More changes

On the service overview page, the memory usage had a flaw to not show the correct amount of resident memory. This has been fixed.
The squid web proxy service has been updated to 3.1.20 and is now compiled with ICAP support enabled (upon user request).

There are now more bandwith options for the download/upload throttling, as well as the list of archive types has been enhanced to make it much more effective.

The fireinfo system can now properly detect memory cards in the Raspberry Pi computer.

——

The Reiser4 filesystem will not be supported on anymore. The IPFire developers believe that this is one of the best filesystems around, but as it does not get any support by the Linux kernel developers, it has become too difficult to keep our kernels in sync with the Reiser4 development state. Please make a backup of your system and reinstall it with one of the filesystems offered by the installer; installation only takes about half an hour. To check if your system uses Reiser4, you will see an applicable notice on the index page of the web interface if a reinstall due to this issue is required.

In the near future, the IPFire developers will be working on the next major version of IPFire, which will come with an updated Linux 3.x kernel. If you have any suggestions or patches to send in please go to our planet and learn how. We encourage everyone who downloads and uses IPFire to get involved in any way they can. Please consider donating or joining the project community!

Michael Tremer - August 3, 2012 at 12:00 am