Beta 1 is now available for testing.

Problems Corrected:

1)  Previously, nested conditionals did not work correctly in all
     cases. In particular:

        ?IF $FALSE
            ?IF $FALSE
               foo
               bar
            ?ENDIF
            baz
            bop
        ?ENDIF

     In this case, the lines 'baz' and 'bop' were incorrectly included
     when they should have beeen omitted.

New Features:

1)  The TPROXY tcrules action introduced in Shorewall 4.4.7 was
     incomplete and required additional logic to be added in the 'start'
     or 'started' extension scripts.

     In this release, the TPROXY implementation has been changed and an
     additional DIVERT action has been created. Because the new TPROXY
     has a different set of parameters than the prior one, the tcrules
     file now supports two formats:

     FORMAT 1 - (default, deprecated )

         The TPROXY action allows three arguments, the first of which
         ('mark') is required.

     FORMAT 2

        The TPROXY action has two optional arguments:

            port -- the port on which the proxy is listening. While
                    this argument is optional, it will normally be
                    supplied.

            ip address -- The address on which the proxy is listening.

     The format is specified by a line line this:

        FORMAT {1|2}

     The Sample configurations have been updated to use FORMAT 2.

     The format-2 tcrules file also supports the DIVERT action. The
     DIVERT action directs matching packets to the local system if there
     is a transparent socket in the local system that matches the
     destination of the packet.

     Finally, the providers file supports a new 'tproxy' option. When
     'tproxy' is specified:

     - It must be the only OPTION given
     - The MARK, DUPLICATE and GATEWAY columns must be empty.

     The 'tproxy' option causes a reserved mark value to be associated
     with the provider and for its associated routing rule to have
     priority 1.

     Here is the TPROXY configuration at shorewall.net:

     tcrules:

       FORMAT 2
       #ACTION                  SOURCE  DEST    PROTO   DEST    SOURCE
       #                                                        PORT(S) PORT(S)
       ...
       DIVERT                   eth1    -       tcp     -       80
       DIVERT                   eth0    -       tcp     -       80
       TPROXY(3129,172.20.1.254)        eth2    -       tcp     80

       Note: eth1 and eth0 are Internet interfaces and eth2 connects to         
            the local LAN.

     providers:

       #NAME  NUMBER MARK DUPLICATE INTERFACE GATEWAY   OPTIONS
       ...
       Squid  3     -    -          lo       -          tproxy

     /etc/squid3/squid.conf:

         ...
        http_port 172.20.1.254:3129 tproxy
         ...

Thank you for testing,
-Tom
-- 
Tom Eastep        \ When I die, I want to go like my Grandfather who
Shoreline,         \ died peacefully in his sleep. Not screaming like
Washington, USA     \ all of the passengers in his car
http://shorewall.net \________________________________________________

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel

Reply via email to