Mike Lander wrote:
> When classifying data in tc rules does it matter if you enter
> data in these two methods? With high marks yes, Mark in Forward Yes
> The first way seems more efficient but I was curious which way
> is the best?
> 
> (1)
> If you want to route through a  certain Isp and use class 3.  This way I 
> noticed the
> packets are marked in the postrouting chain only. (does tcpost chain shape 
> as well?)
> tc rules entry
> 256:103     $FW            0.0.0.0/0 tcp                 80,443,3128
> 512:203     $FW            66.224.62.96/27 all
> 512:203     0.0.0.0/0      66.224.62.96/27   all
> mangle table results------------------------------------------
> Chain tcpost (1 references)
>  pkts bytes target     prot opt in     out     source 
> destination
>  535K   75M CLASSIFY   tcp  --  *      *       0.0.0.0/0 
> 0.0.0.0/0           multiport dports 80,443,3128 CLASSIFY set 256:103
> 36209   12M CLASSIFY   all  --  *      *       0.0.0.0/0 
> 66.224.62.96/27     CLASSIFY set 512:203

That whole thing is nonsense.

a) You can't influence routing in the POSTROUTING chain -- "POST" means
"after".

b) 256:103 indicates that you have 256 interfaces under traffic shaping
and you want to classify the traffic for interface 256 with mark value
03 (which isn't possible since leading zeros are dropped). Of course, it
is clearly documented that Shorewall doesn't support more than 10
interfaces being traffic shaped.

> 
> (2)
> Or you can enter this way in tc rules, which then marks route in the
> Pre routing chain and the shaping in the Forward Chain
> tc rules entry
> 512:P eth3:10.19.227.0/24  64.42.53.203   all
> 3 eth3:10.19.227.0/24  64.42.53.203   all
> mangle table results------------------------------------------
> Chain tcfor (1 references)
>  pkts bytes target     prot opt in     out     source 
> destination
>   588 40397 MARK       all  --  eth3   *       10.19.227.0/24 
> 64.42.53.203        MARK set 0x3
> Chain tcpre (3 references)
>  pkts bytes target     prot opt in     out     source 
> destination
>   598 42399 MARK       all  --  eth3   *       10.19.227.0/24 
> 64.42.53.203        MARK or 0x200
> Where with this one you could have entered ?
> 512:203     eth3:10.19.227.0/24      64.42.53.203       all

Mike, you need to read the documentation about CLASSIDs again -- you
clearly don't understand them.

-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

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to