On Sat, 2010-09-11 at 12:17 -0700, Tom Eastep wrote: > > I'm guessing it is 'cls_flow'.
Bingo! > Shorewall 4.4.6 did not accurately detect > the availability of that capability. Explains it then. :-) But strangeness ensues. My connection is capable of 15Mbps down/1Mbps up. When I set the IN-BANDWIDTH absurdly high, like 24mbit, of course, I see the full 15Mbps down. However when I go down to 12mbit, I only see between 7-8Mbps down. Setting IN-BANDWIDTH to 15mbit yields between 11-12Mbps and setting IN-BANDWIDTH to 18mbit yields 14-15Mbps. Any thoughts as to why the discrepancies? On another note, maybe I am just misunderstanding, but it seems this Simple TC mode is only dealing with downstream bandwidth and not upstream bandwidth (even though, typically, on consumer and even some small business connections, there is lots of downstream bandwidth compared to upstream bandwidth). Is my understanding correct here? Priority dequeuing seems like a reasonable approach for the downstream side where we cannot really shape bandwidth anyway (that is more properly done upstream), but what about preventing saturation of the upstream bandwidth interrupting latency sensitive applications like VIOP and whatnot? b.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
