From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.21 - Core Update 129 released
Date: Mon, 08 Apr 2019 19:35:33 +0100 [thread overview]
Message-ID: <mailman.6.1554748561.3848.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2770 bytes --]
https://blog.ipfire.org/post/ipfire-2-21-core-update-129-released
This is the official release announcement for IPFire 2.21 - Core Update 129 - an update that introduces routed IPsec VPNs and comes with various other changes that update the core system and fix several bugs.
IPsec Reloaded
IPsec has been massively extended. Although IPsec in IPFire is already quite versatile and delivered high performance [1], some features for experts were required and are now available through the web UI:
• Routed VPNs with GRE & VTI [2]
• Transport Mode for net-to-net tunnels
• IPsec connections can now originate from any public IP address of the IPFire installation. This can be selected on a per-connection basis.
The code has also been cleaned up the UI has been made a little bit tidier to accommodate for the new settings.
Smaller changes include:
• The "On-Demand" mode is finally the default setting. Tunnels will shut down when they are not used and they will be established again when they are required.
Misc.
• DHCP: A crash has been fixed when filenames containing a slash have been entered for PXE boot.
• DHCP: Editing static leases has been fixed
• Domains in the "DNS Forwarding" section can now be disabled for DNSSEC validation. This is a dangerous change, but has been requested by many users.
• Updated packages: bind 9.11.6, groff 1.22.4, ipset 7.1, iptables 1.8.2, less 530, libgcrypt 1.8.4, openssl 1.1.1b, openvpn 2.4.7, squid 4.6, tar 1.32, unbound 1.9.0, wpa_supplicant 2.7
• New commands: kdig 2.8.0
• The build system has been optimised to reduce build time of the whole distribution to around 4-5 hours on a fast machine.
Add-Ons
• Alexander Koch has contributed zabbix_agentd which is the agent that is installed on the monitored machine. With this [3], IPFire can now be integrated into an environment that is monitored by Zabbix.
• On that note, the SNMP daemon has also been updated to version 5.8 for people who use the SNMP protocol for monitoring.
• tor has been updated to 0.3.5.8 and some minor bugs have been fixed in the web user interface
• The spectre-meltdown-checker script is available as an add-on which allows IPFire users to test their hardware for vulnerabilities
• Other updates: amavisd 2.11.1, hostapd 2.7, postfix 3.4.3
Thank you very much to everyone who contributed to this Core Update. Please support our project and donate today [4] so that we can keep up our work!
[1] https://blog.ipfire.org/post/feature-spotlight-galois-counter-mode-ipsec-with-10g
[2] https://blog.ipfire.org/post/routed-ipsec-vpns-are-landing-in-ipfire-2-21-core-update-129
[3] https://wiki.ipfire.org/addons/zabbix_agentd
[4] https://www.ipfire.org/donate
reply other threads:[~2019-04-08 18:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.6.1554748561.3848.ipfire-announce@lists.ipfire.org \
--to=ipfire-announce@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox