Donovan Baarda wrote: > On Mon, 2007-04-09 at 15:04 -0700, Tom Eastep wrote:
> Patch attached. The calculation for r2q is pretty basic... the (kbits / > 200) is a compromise to try and get decent quantum values for rates > between 1mbit and 100mbit. This gives quantum ~25,000 for speed "full", > and ~2500 for speeds "full/10". For rates < 1mbit I limit the minimum > r2q to 5 and rely on the fact that the minimum quantum is limited to the > device mtu. You can change the /200 to /400 to give quantum ~50,000 for > "full", and by my calcs you should still stay under the 60,000 max, but > I get the impression that high quantum's are a bad idea. > > Note at one stage I had also changed the calculate_quantum() function to > limit the output to 60000. However, this function is not used for the > device root class, so it didn't fix the "quantum warning". With the r2q > calc's you should never exceed 60,000 anyway... > > The most useful addition IMHO is the ability to not define a default > class, and have all unclassified traffic bypass TC. Thanks. Unfortunately, this patch is against Shorewall 3.2. Shorewall 3.4 is the current stable release and would be the earliest release that I would consider adding these changes to. I'll hack around with it when I have the time. -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
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
