-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 James Gray wrote:
> Thanks for the patches Tom. Are you releasing a new 3.4? Just curious as it > would make my version-management easier than rolling my own (patched) RPM. > Furthermore, the behaviour described seems to reflect the battles I've had > over the last few days with my multi-ISP setup with HIGH_ROUTE_MARKS=No. > Problem disappeared when I started using high route marks in PREROUTING. I see no reason to stick with 3.4 series when shorewall-shell-4.0.2 is nearly 100% identical with latest 3.4 series release. I'd make supporting 3.4 versions questionable because only real changes to shorewall-shell-4 and shorewall-common-4 are packaging related. - -- Tuomo Soini <[EMAIL PROTECTED]> Linux and network services +358 40 5240030 Foobar Oy <http://foobar.fi/> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFGzWpwTlrZKzwul1ERAtbfAJ9illgOI7Rb63/t4p7Opa5v2TqhdQCglWTq +BzA8FtI91JEE9cVRoiXlEQ= =KNHn -----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 Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
