-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Cristian wrote:
>
>
> On Mon, 05 Nov 2007 06:54:22 -0800, Tom Eastep <[EMAIL PROTECTED]>
> wrote:
>
>> Please forward the output of "shorewall dump" (as a compressed
>> attachment).
>> Capture the dump with the configuration that fails.
>
> Here they come
>
The broken.txt file doesn't have the default 512 tcrule!
Again -- Please collect the dump with the configuration that doesn't
work. According to your post:
...if I comment out the first line, traffic from 192.168.108.199
(dmz) goes always out through the right interface, but all the
traffic not specified in tcrules gets balanced between the two
connections.
That is exactly what that configuration should do and that's what you
sent me (the first line is commented out).
- -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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFHL2QuO/MAbZfjDLIRAsIbAJ99dbHec4jOlwqdVFbkQjVr14FNcQCgiXfv
rFWecDqMF9RIu/QsonBXLxI=
=ojZx
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
