Felipe Román <from...@gmail.com> wrote:

> to the point.
> I have a "problem" with QoS, we have different speed in the network 
> provider link, 100mbit download and 100mbit upload in the national 
> connections, and 10mbit download and 10mbit upload on international 
> connections.

*IFF* you can define a rule for one or other of the traffic types then simply 
define two sets of classes. Eg :
- 1 + 10 + 11
-   |    + 12
-   |    + 13
-   |    + 14
-   |
-   + 20 + 21
-        + 22
-        + 23
-        + 24

Where 1 is the head queue attached to the interface, 10 is a queue shaped to 
(say) 99Mbit (*NOT* mbit !), and 20 is a queue shaped to (say) 9.9Mbit).

It's worth a good read of http://lartc.org, specifically chapter 9 
http://lartc.org/howto/lartc.qdisc.html
There's some heavy reading there, but it's worth the effort to understand how 
it all works.

I have a setup at work with a similar structure, except we use it for 
controlling customer bandwidth - eg "customer A can have 2Mbit guaranteed and 
up to 10Mbit if available", "customers in list B can have minimum 1Mbit between 
them and up to 10Mbit if available", and so on. That's the 10, 20, ... level, 
then below that you can put high priority traffic into 11, 21, "bulk" traffic 
into 14, 24, ... and so on.
The original setup was done with customer TC rules, the later setup as done 
with Shorewall's builtin functions.

Note that you cannot truly shape traffic that has already been received 
(inbound), but you can shape it on egress from the internal interface with some 
success. Note that you can't shape inbound traffic to the router - to do that 
you'd need to use an intermediate queuing device, but that puts other 
restrictions on the setup.
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to