############ So your Mark=3 class on eth1 defines a much wider pipe than eth0 (128K *BYTES* per second guaranteed and 256K *BYTES* per second max). So even though you are now correctly classifying traffic with your tcrules, you will not have any effective shaping of download traffic to 192.168.200.1. ############
exactly :-) Now it's: ############################## eth0 1 16kbps 30kbps 2 eth0 2 full full 1 default eth1 3 16kbps 30kbps 2 eth1 4 full full 1 default ############################### working perfectly right :-)) ----- Original Message ----- From: "Tom Eastep" <[EMAIL PROTECTED]> To: "Shorewall Users" <[email protected]> Sent: Tuesday, January 02, 2007 3:15 PM Subject: Re: [Shorewall-users] TC - not marking correctly > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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
