Jool is an Open Source SIIT and NAT64 for Linux.
As far as we know, Jool is a compliant SIIT and Stateful NAT64. This is the roadmap as of 2016-10-07:
- Milestone 4.0.0 will be an internal refactor which should enhance Jool’s config versatility.
- Milestone 4.1.0 will add several more features.
New bug reports might interpolate other milestones in-between. Feedback from users can persuade us to change priorities. See Contact for options on this.
Our latest important release is version 3.5.2.
Version 3.4.6 has been released.
3.4.6 simply mirrors the #232 fix (already in 3.5.2) into the 3.4 series. You don’t need to downgrade if you’re using Jool 3.5.
Version 3.5.2 has been released.
- Fixed a kernel panic. (Both SIIT and NAT64.)
- Improved the build system: #233 and #234
- Fixed the RFC6791 pool.
Version 3.5.1 has been released. Both apply to NAT64:
Version 3.5.0 has been released! The new features are
- Atomic Configuration
- Session Synchronization
- Namespace Instances
- A v6 RFC6791 prefix
- Documented Testing Framework (unit and graybox)
Some functionality was dropped:
Jool 3.4.5 was released.
- Added support for kernels 4.6 and 4.7.
- Deleted constant warning due to an empty pool6.
- Improved the implicit blacklist:
- Blacklisted directed broadcast.
- Applied the implicit blacklist to EAMT-based translation.
(Among other things, this prevents an overly-intrusive EAMT from hogging packets intended for the translator.)
jool_siitcan now be modprobed in the same namespace without suffering a Netlink socket collision.
Version 3.4.4 released. One bug was found:
- NAT64 Jool’s implementation of empty pool4 used to mistake point-to-point interface addresses, leading to packet drops.
Version 3.4.3 released.
- Added support for a wider range of kernels. Support is now from Linux 3.2 to 4.4, and also RHEL 7.0 to 7.2.
- New configuration flag for NAT64:
- New configuration flag for NAT64:
Version 3.4.2 released. There are three bugfixes:
- Bogus pointers and memory leaks caused by
--flushand termination of pool6791 and blacklist (SIIT Jool).
--session --displaynow require network admin privileges (NAT64 Jool).
- Needlessly purged some compilation warnings in old gcc versions (NAT64 Jool).
Careful with #2! You might need to update scripts.
Version 3.4.1 released. There are three bugfixes:
- Kernel panic due to incorrect namespace API handling.
- Fixed compilation for kernels 4.1 and above.
- The userspace applications used to return success after errors found by the module.
Version 3.4.0 released. This is a fat one.
- Refactors to pool4 add mark-dependent sourcing and port ranges (which in turn removes the need for a second IPv4 address), and fixes the excessive memory usage.
- The EAMT now implements Hairpinning and overlapping entries, which are newer updates to the EAM draft.
- Minimal namespace features, which allow Host-Based Edge Translation (now called Node-Based Translation) and (subjectively) better filtering.
- The userspace application now prints the friendlier error messages that used to be dumped in the kernel log only.
- Removed reliance on dead code deletion, which used to prevent compilation on some systems.
- Two bugfixes.
- A spanish version of this site.
--csvcan now be used on all configuration targets.
If you want to upgrade, please keep in mind pool4 is not completely backwards-compatible. In Jool 3.3, any packet would be masked using any available pool4 entry. In Jool 3.4, every pool4 entry only masks packets wielding specific marks (which defaults to zero). See
--markfor more details.
Version 3.3.5 released.
- A connection could be masked using port zero (NAT64 Jool).
- Incorrect routing when pool6791 was empty (SIIT Jool).
- Memory leak on
--eamt --flush(SIIT Jool).
Version 3.3.4 released.
Also, it has been noticed SIIT Jool installations in kernels 3.5 and below need IPv4 forwarding active. In other words, add
sudo sysctl -w net.ipv4.conf.all.forwarding=1
to the modprobe procedure.
In addition, version 3.3.3 contains the following:
Version 3.3.2 released.
This is the summary:
- There are new configuration flags:
- The userspace app was misbehaving in several ways. While all of its bugs had workarounds, it was a pain to use.
Also, unrelated to the code, we now have two mailing lists:
- email@example.com is intended to spread news. Since we currently don’t have other major events, the plan is to only use it to announce new releases coming out. Click here to start listening.
- firstname.lastname@example.org can be used for public discussion (help, proposals, whatever). I will also drop the news here so people doesn’t have to subscribe to both at a time. Click here to register.
email@example.com can still be used to reach us developers only.
We’d also like to apologize for the certificate hiccup we had recently. Though they are being generated, the mailing list archives are also not available yet, and this is in our admins’ TODO list.
Important bug discovered!
We just released Jool 3.3.1.
Jool 3.3.0 is finished.
Filtering couldn’t make it into the milestone, but Stateless IP/ICMP Translation (SIIT) is now supported.
We also refactored the userspace app somewhat; please review your scripts:
- The kernel’s per-interface MTU setting replaced
--bib6were deprecated because they’re considered redundant. See
- Three global flags were also deprecated for different reasons.
We also released Jool 3.2.3, which is bugfixes since 3.2.2. One of the bugs is a DoS vulnerability, so upgrading to at least 3.2.3 is highly recommended.
An important bug was discovered, and version 3.2.2 is out.
It has come to our attention that we are also lacking an explanation of IP literals, so there should be another codeless update like this in the near future.
Version 3.2.1 released. The 3.2 series is now considered more mature than 3.1.
The important changes are
- Jool used to always attempt to mask packets using the first prefix of the pool. This meant that Jool was unable to handle more than one prefix.
- The memory leak in the core has been purged.
The less noticeable ones are
log_martiansis no longer a step in modprobing Jool (though it doesn’t bite if you keep it).
- The SNMP stat updates returned. See
- Corner-case packets now get checksums updated correctly.
It took it a really long time to overcome testing, but version 3.2.0 is finally released.
We changed the minor version number this time, because the userspace application has a slightly different interface; the single-value configuration parameters have been joined:
--fragmentation. The application also has three new features:
The second main novelty is the finally correct implementation of Simultaneous Open of TCP Connections. The translation pipeline should now be completely quirkless.
A little confusion also revealed that the path to libnl used to be hardcoded in the configuration script. If you used to have trouble compiling the userspace application, you might want to try again using the new version.
The more unnoticeable stuff includes a complement to the old issue #65 and a healthier code-to-comment ratio :). The user documentation, on the other hand, received a significant refactor, so looking at the diff might not be overly productive this time.
One thing we did not complete was the fragmentation refactor. This is in fact the reason why this milestone dragged. We appear to really need to reconcile the kernel’s defragmenter and the RFC in order to implement filtering policies however, so it’s still considered an active issue.
We also released 3.1.6, which is small fixes from 3.1.5, in case somebody has a reason to continue using the 3.1.x series.
By the way:
Version 3.1.5 released.
Our most important fix is issue #92. Incorrect ICMP errors used to confuse IPv4 nodes, which lowered the reliability of 4-to-6 traffic.
Aside from that, the userspace application has been tightened. It doesn’t crash silly anymore when it has to output large BIB or session tables, and works a lot harder to keep the database free from trashy leftover records.
Then we have a couple of performance optimizations. In particular (and more or less as a side effect), by aligning log priorities to those from the rest of the kernel, more care has been taken to keep the log cleaner.
If people doesn’t find critical bugs in this version, this appears to be the end of the 3.1.x series. We’ll go back to aim for 100% RFC compliance in the next update.
Version 3.1.4 released. Fixes:
Version 3.1.3 released. Fixes:
- An incorrect implementation used to ban configuration on certain systems.
- A bug used to prevent Jool from sending certain ICMP errors.
- A memory leak.
- Slightly optimized the packet translation algorithm by replacing some spinlocks with RCUs.
Website released. This website!
And with it comes a new release. 3.1.2 fixes:
- 21-centuried the userspace-app’s installation procedure.
- Jool is now more explicit regarding the suffix of prefixes.
- Jool no longer wrecks itself when modprobed with invalid arguments.
Version 3.1.1 released.
It contains two bugfixes:
- Added permission checking to the admin-related userspace requests.
- Fixed compatibility issues with ~3.1 kernels.
Version 3.1.0 released. Jool finally handles fragments!
Other important fixes:
- Major optimizations on both the BIB and session databases. The module should scale a lot more gracefully as clients demand more traffic.
- Jool no longer requires a separate IPv4 address.
- Kernel panic during removal of the module fixed.
- And More stuff.