On 09/29/2017 07:35 AM, Vieri Di Paola via Shorewall-users wrote: > > ________________________________ > From: Tom Eastep <[email protected]> >> >> Remember that MARK is not a terminating target -- so the *last* MARK > >> rule to match the packet is the one that assigns the mark. > > I was aware of that when I wrote the rules. > > My providers file is: > > ISP1 1 1 - $IF_ISP1 $IF_ISP1_GW > track,balance=3,persistent > ISP2 2 2 - $IF_ISP2 $IF_ISP2_GW > track,balance=2,persistent > ISP3 3 3 - $IF_ISP3 $IF_ISP3_GW > track,balance=1,persistent > ISP4 4 4 - $IF_ISP4 $IF_ISP4_GW > track,balance=1,persistent > > > ...and the *last* line of my mangle file is: > > MARK(3):P - 193.104.0.136
It is the *next to the last* rule that is causing the problem. > > >> Your> statistical MARK rules are overwriting your intended mark values most >> of > >> the time. > > > If by "statistical" you mean the marks produced by "balance" in the providers > file then am I mistaken to think that the last mangle rule defined overwrites > previous marks? > >> You need to populate the TEST column of your route marking> rules to stop >> this unintended overwriting of previously assigned marks. > > > The TEST column in the mangle file? > Not quite sure which value to use for a MARK rule on the last line of that > file. Again, it isn't the last rule that is the issue. -Tom -- Tom Eastep \ Q: What do you get when you cross a mobster with Shoreline, \ an international standard? Washington, USA \ A: Someone who makes you an offer you can't http://shorewall.org \ understand \_______________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
