diff --git a/Shorewall-Website/mailing_list.htm b/Shorewall-Website/mailing_list.htm index 9f6e85750..24053d3e2 100755 --- a/Shorewall-Website/mailing_list.htm +++ b/Shorewall-Website/mailing_list.htm @@ -30,7 +30,6 @@ Documentation License

2004-11-09

-

See the Shorewall Website for Shorewall information and documentation.
@@ -254,9 +253,9 @@ Mailman
  • SpamAssassinSpamAssassin Logo
    • + href="http://www.spamassassin.org">SpamAssassin Logo
  • Postfix

    The current 2.0 Stable Release is 2.0.13 -- Here are the release notes.
    -The current Developement Release is 2.2.0 Beta 6 -- Here +The current Developement Release is 2.2.0 Beta 7 -- Here are the release + href="http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta7/releasenotes.txt">release notes.

    Copyright © 2001-2004 Thomas M. Eastep

    @@ -44,7 +44,7 @@ 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”.

    -

    2004-12-02

    +

    2004-12-04

    Table of Contents

    Introduction @@ -59,7 +59,9 @@ Shorewall
    Shorewall on Mandrake® with a two-interface setup?
    License

    News

    -

    Shorewall +

    Shorewall 2.2.0 Beta 7
    +Shorewall 2.0.13
    Shorewall 2.0.12
    @@ -164,6 +166,109 @@ of the license is included in the section entitled "GNU Free Documentation License".

    News

    +12/04/2004 - +Shorewall 2.2.0 Beta 7
    +
    +Problems Corrected:
    +
      +
    1. The "shorewall add" and "shorewall delete" commands now work in a +bridged environment. The syntax is:
      + 
      +           shorewall +add <interface>[:<port>]:<address> <zone>
      +           shorewall +delete <interface>[:<port>]:<address> <zone>
      + 
      +   Examples:
      + 
      +           shorewall +add br0:eth2:192.168.1.3 OK
      +           shorewall +delete br0:eth2:192.168.1.3 OK
      +
      +
      2. +
    2. Previously, "shorewall save" created an out-of-sequence restore +script. The commands saved in the user's /etc/shorewall/start script +were executed prior to the Netfilter configuration being restored. This +has been corrected so that "shorewall save" now places those commands +at the end of the script.
      +
      +To accomplish this change, the "restore base" file +(/var/lib/shorewall/restore-base) has been split into two files:
      + 
      +/var/lib/shorewall/restore-base -- commands to be executed before +Netfilter the configuration is restored.
      + 
      +/var/lib/shorewall/restore-tail -- commands to be executed after the +Netfilter configuration is restored.
      +
      +
      3. +
    3. Previously, traffic from the firewall to a dynamic zone member +host did not need to match the interface specified when the host was +added to the zone. For example, if eth0:1.2.3.4 is added to dynamic +zone Z then traffic out of any firewall interface to 1.2.3.4 will obey +the fw->Z policies and rules. This has been corrected.
      4. +
    4. Shorewall uses the temporary chain 'fooX1234' to probe iptables +for detrmining which features are supported. Previously, if that chain +happened to exist when Shorewall was run, capabilities were +mis-detected.
      5. +
    +New Features:
    +
      +
    1. You can now use the "shorewall show zones" command to display the +current contents of the zones. This is particularly useful if you use +dynamic zones (DYNAMIC_ZONES=Yes in shorewall.conf).
      + 
      +    Example:
      + 
      +        ursa:/etc/shorewall # +shorewall show zones
      +        Shorewall-2.2.0-Beta7 Zones +at ursa - Sat Nov 27 11:18:25 PST 2004
      + 
      +        loc
      +           +eth0:192.168.1.0/24
      +           +eth1:1.2.3.4
      +        net
      +           +eth0:0.0.0.0/0
      +        WiFi
      +           +eth1:0.0.0.0/0
      +        sec
      +           +eth1:0.0.0.0/0
      + 
      +        ursa:/etc/shorewall #
      +
      +
      2. +
    2. Variable expansion may now be used with the INCLUDE directive.
      + 
      +    Example:
      + 
      +        /etc/shorewall/params
      + 
      +            +FILE=/etc/foo/bar
      + 
      +        Any other config file:
      + 
      +            +INCLUDE $FILE
      +
      +
      3. +
    3. The output of "shorewall status" now includes the results of "ip +-stat link ls". This helps diagnose performance problems caused by link +errors.
      4. +
    4. Previously, when rate-limiting was specified in +/etc/shorewall/policy (LIMIT:BURST column), any traffic which exceeded +the specified rate was silently dropped. Now, if a log
      +level is given in the entry (LEVEL column) then drops are logged at +that level at a rate of 5/min with a burst of 5.
      +
      5. +
    12/02/2004 - Shorewall 2.0.13