Qos/TrafficShaping(on Shorewall) Howto available for Web-viewing
Ow Mun Heng
ow.mun.heng at wdc.com
Thu Apr 29 02:08:34 UTC 2004
> -----Original Message-----
> From: fedora-list-bounces at redhat.com
> [mailto:fedora-list-bounces at redhat.com]On Behalf Of Homer
> On Tue, 2004-04-27 at 21:03, Ow Mun Heng wrote:
>
> >
> > Please have a view and please feedback accordingly. I think
> It needs a little more work, esp in that QoS only can shape outgoing
> traffic and not incoming.
> >
>
> That's the reason I didn't use Wondershaper.. I've got
> 4 interfaces in
> my firewall and needed to throttle them all differently.. To throttle
> both directions, you have to apply tc rules to both
> interfaces.. IE: you
> want 192.168.1.1 to have 256k with QOS both ways, you have to mark the
> packets as they come in, and then let tc use the marks to set
> the packet
> to a rule.. Then you do it for the other interface.. So you end up
> marking the packets coming in both interfaces, and in my case, I mark
> according to origination and destination.. You've just set it for 256k
> both ways.. And yes, I use Shorewall as well.. Works like a
> champ ;) As
> for you're HowTo, it looked pretty good, just wanted to let
> you know how
> to handle both directions... For your next HowTo ;)
Actually, I updated the docs yesterday. I did mention that we can perform
QoS on incoming connection but that would really mean, either dropping
packets as they come in or severely limitting your downstream bandwidth.
I don't really think you can somehow Shape what your ISP sends you
unless you have access to the ISP's routers etc.
If I am mistake, please educate me.
More information about the fedora-list
mailing list