Shorewall Release Model

Tom Eastep

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover, and with no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License.


Table of Contents

Shorewall Releases

Shorewall Releases

  1. Releases have a three-level identification x.y.z (e.g., 4.5.0).

  2. The first two levels (x.y) designate the major release number (e.g., 4.5).

  3. The third level (y) designates the minor release Number.

  4. Installing a new minor release involves no migration issues unless you want to take advantage of an enhancement. For example, if you are running 4.5.0 and I release 4.5.1, your current configuration is 100% compatible with the new release.

  5. A major release may have migration issues. These are listed in the release notes and on the upgrade issues page.

  6. Support is available through the Mailing List for the most recent Major Release.

  7. After the introduction of a new major release, support is still available for the prior major release until the principle distributions have upgraded to that new release. Fixes will only be provided for the last minor release in the previous Major Release. For example, once 4.5.0 was released, the only fixes for major issues with 4.4.27 would be released for the 4.4 series.

  8. Support for the prior major release ends once the major Linux distributions have upgraded to that release.

  9. Once a minor release has been announced, work begins on the next minor release. Periodic Beta releases are made available through announcements on the Shorewall Development and Shorewall User mailing lists. Those Beta releases are numberd w.x.y-Beta1, ...Beta2, etc. Support for the Beta releases is offered through the Shorewall Development mailing list in the form of emailed patches. There is no guarantee of compatability between one Beta release and the next as features are tweaked.

  10. When the next minor release is functionally complete, one or more release candidates are announced on the Shorewall Development and Shorewall User mailing lists. These release candidates are numbered w.x.y-RC1, ...-RC2, etc.

  11. What does it mean for a major release to be supported? It means that that if a bug is found, we will fix the bug and include the fix in the next minor release.

  12. Between minor releases, bug fixes are made available via patch releases. A patch release has a four-level identification x.y.z.N where x.y.z is the minor release being fixed and N = 1.2.3...

The currently-supported major release 4.5.


Frequently Used Articles

- FAQs - Manpages - Configuration File Basics - Beginner Documentation - Troubleshooting

Shorewall 4.4/4.5/4.6 Documentation

Shorewall 4.0/4.2 Documentation

Shorewall 5.0/5.1/5.2 HOWTOs and Other Articles

- 6to4 and 6in4 Tunnels - Accounting - Actions - Aliased (virtual) Interfaces (e.g., eth0:0) - Anatomy of Shorewall - Anti-Spoofing Measures - AUDIT Target support - Bandwidth Control - Blacklisting/Whitelisting - Bridge/Firewall - Building Shorewall from GIT - Commands - Compiled Programs - Configuration File Basics - DHCP - DNAT - Docker - Dynamic Zones - ECN Disabling by host or subnet - Events - Extension Scripts - Fallback/Uninstall - FAQs - Features - Fool's Firewall - Forwarding Traffic on the Same Interface - FTP and Shorewall - Helpers/Helper Modules - Installation/Upgrade - IPP2P - IPSEC - Ipsets - IPv6 Support - ISO 3661 Country Codes - Kazaa Filtering - Kernel Configuration - KVM (Kernel-mode Virtual Machine) - Limiting Connection Rates - Linux Containers (LXC) - Linux-vserver - Logging - Macros - MAC Verification - Manpages - Manual Chains - Masquerading - Multiple Internet Connections from a Single Firewall - Multiple Zones Through One Interface - My Shorewall Configuration - Netfilter Overview - Network Mapping - No firewalling of traffic between bridge port - One-to-one NAT - Operating Shorewall - OpenVPN - OpenVZ - Packet Marking - Packet Processing in a Shorewall-based Firewall - 'Ping' Management - Port Forwarding - Port Information - Port Knocking (deprecated) - Port Knocking, Auto Blacklisting and Other Uses of the 'Recent Match' - PPTP - Proxy ARP - QuickStart Guides - Release Model - Requirements - Routing and Shorewall - Routing on One Interface - Samba - Shared Shorewall/Shorewall6 Configuration - Shorewall Events - Shorewall Init - Shorewall Lite - Shorewall on a Laptop - Shorewall Perl - Shorewall Setup Guide - SMB - SNAT - Split DNS the Easy Way - Squid with Shorewall - Starting/stopping the Firewall - Static (one-to-one) NAT - Support - Tips and Hints - Traffic Shaping/QOS - Simple - Traffic Shaping/QOS - Complex - Transparent Proxy - UPnP - Upgrade Issues - Upgrading to Shorewall 4.4 (Upgrading Debian Lenny to Squeeze) - VPN - VPN Passthrough - White List Creation - Xen - Shorewall in a Bridged Xen DomU - Xen - Shorewall in Routed Xen Dom0

Top of Page