Thanks, Jerry. Cristian -- there is certainly something inconsistent in the numbering of the providers between the working and non-working configurations.
-Tom -------- Original Message -------- Subject: Re: [Shorewall-users] Shorewall 3.2.9 (Etch) 2 providers and traffic shaping Date: Tue, 06 Nov 2007 13:51:25 -0500 From: Jerry Vonau <[EMAIL PROTECTED]> To: Tom Eastep <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Hi Tom: > The only difference that I see in the two is that, because you haven't > applied the patch which corrects a problem with HIGH_ROUTE_MARKS=No (see > http://www.shorewall.net/shorewall_index.htm#Notice), your working > configuration is operating as if you had set TC_EXPERT=Yes. So, grasping at > straws, you might set TC_EXPERT=Yes in the non-working configuration and see > if that makes any difference. > > Jerry: Do you see anything in Cristian's dumps? > The only thing that jumps out at me is the route rules between the working/non-working configs: Routing Rules working 0: from all lookup 255 10001: from all fwmark 0x1 lookup smrt2 <<<<<< 10002: from all fwmark 0x2 lookup fweb1 <<<<<< 10256: from all fwmark 0x100 lookup smrt2 10512: from all fwmark 0x200 lookup fweb1 20256: from 82.104.128.42 lookup smrt2 20257: from 82.104.128.43 lookup smrt2 20258: from 82.104.128.44 lookup smrt2 20512: from 21.244.102.218 lookup fweb1 32766: from all lookup main 32767: from all lookup default Routing Rules non working 0: from all lookup 255 10001: from all fwmark 0x1 lookup fweb1 <<<<<< 10002: from all fwmark 0x2 lookup 3 <<<<<< 10256: from all fwmark 0x100 lookup fweb1 10512: from all fwmark 0x200 lookup smrt2 20000: from 82.104.128.42 lookup smrt2 20001: from 82.104.128.43 lookup smrt2 20002: from 82.104.128.44 lookup smrt2 20256: from 21.244.102.218 lookup fweb1 32766: from all lookup main 32767: from all lookup default That hoses the track option, right? What's up with table "3"(in the non-working dump), that could be a hang-around-er from not having the routing rules/tables cleared with that version. I'd like to see back to back dumps of the working config, after a network restart, and then adding in the shaping stuff, with a network restart, just to be sure the base line is the same The other interesting thing is that the providers are processed in a different order, the route rules assignment order is changed, could be just the listing order in the providers file, just not sure from here. Jerry -- 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
signature.asc
Description: OpenPGP digital 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
