Problems Corrected in 3.2.9

1)  While most distributions store the Shorewall Lite compiled program
    in /var/lib/shorewall-lite/, Shorewall includes features that allow
    that location to be changed on a per-distribution basis. The
    default for a particular distribution may be determined by the
    command "shorewall[-lite] show config".

        [EMAIL PROTECTED]:~/shorewall/trunk$ shorewall show config
        Default CONFIG_PATH is /etc/shorewall:/usr/share/shorewall
        LITEDIR is /var/lib/shorewall-lite
        [EMAIL PROTECTED]:~/shorewall/trunk$

    The LITEDIR setting is the location where the compiled script
    should be placed. Unfortunately, the "shorewall [re]load" command
    previously used the setting on the administrative system rather
    than the one from the firewall system so it was possible for that
    command to upload the compiled script to the wrong directory.

    To work around this problem, Shorewall now determines the LITEDIR
    setting on the firewall system and uses that setting for uploading
    the compiled script and its companion .conf file.

2)  Previously, IP ranges and ipset names were handled incorrectly in
    the last column of the maclist file with the result that run-time
    errors occured.

3)  The new SIP and H323 Netfilter helper modules were not being
    automatically loaded by Shorewall. They have now been added to the
    /usr/share/shorewall[-lite]/modules files.

Other Changes in 3.2.9

1)  Previously, 'ipsecnat' tunnels allowed AH traffic by default
    (unless 'isecnat:noah' was given). Given that AH is incompatible
    with nat-traversal, 'ipsecnat' now implies 'ipsecnat:noah'.

2)  A macro that handles SixXS has been contributed by Christian
    Roessner.

3)  It is rather difficult to code a 'params' file that assigns other
    than constant values such that it works correctly with Shorewall
    Lite. To work around this problem, a new EXPORTPARAMS option
    has been added to shorewall.conf. When EXPORTPARAMS=No, the
    'params' file is no longer copied to the compiler output.

    With EXPORTPARAMS=No, if you need to set environmental variables on
    the firewall system for use by your extension scripts, then do so
    in the init extension script.

    The default is EXPORTPARAMS=Yes to retain the current behavior. So
    if you are happy with the current behavior, you need make no change
    to your shorewall.conf file.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ [EMAIL PROTECTED]
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to