[ previous ] [ next ] [ threads ]
 From:  LEE Tet Yoon <leety at ihug dot co dot nz>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Misunderstanding the QoS feature in m0n0
 Date:  Tue, 20 Mar 2007 05:41:56 +1200
At 01:41 a.m. 20/03/2007, you wrote:
>> For example. Let's say I've a DSL connection, 1Mb download, 512
>> upload. What I ideally would want to have is QoS for VoIP (I've a PBX
>> in my network). So I want VoIP to always have priority in the network.
>> But I do not want to "waste" bandwidth. For what I understand, the
>> "pipe" is always reserved, and if VoIP is not being used, other
>> traffic will not be able to use all the available bandwidth.
>> Sorry if the explanation is a little confusing... What I mean is: Is
>> for example my p2p client able to use all the available bandwidth (if
>> no VoIP connection is alive), and in the moment that a VoIP call is
>> being started "prioritize" the VoIP packets, so they arrive on time?
>The pipe is not being reserved in the way you mean it. At least not in a
>typical set-up, as the one whihc is produced by the "magic shaper wirzard".
>You use queues for the priorization of the traffic. The traffic is then
>allowed to use the pipe accoridng to it's priority. If no other traffic
>occurs, P2P trffic gets the whole bandwidth of the pipe.
>However, the pipe needs to be configured in a way that the buffer of the DSL
>modem never gets filled. Because as soon as packets get to the modem, they
>are out of reach of the m0n0wall. And the modem will sequentially process
>it's buffer, regardless of any QoS demands. For that reason, the pipes are
>typically configured with 10% less bandwidth that the "native" bandwidth of
>the modem/DSL line.
>Note that you'll most likely need NO traffic shaping for the downstream,
>since your LAN has most likely significantly more bandwidth than your DSL
>downlink. As there's no danger of some network buffer filling up, you can
>set the corresponding pipe to a bandwidth value which exceeds the DSL
>downstream bandwidth. No waste of bandwidth there!
>On the upstream however, you'll need the loss of 10% of the bandwidth. In
>return you receive a *much* better latency!

It's my understanding that limiting downstream is sometimes helpful when you want to prioritise
traffic. Reason being, some ISPs will have their own QOS which you may not like (e.g. some have
their own queuing). To try and override this, if you set a downstream limit below the ISPs, it means
the traffic should be regulated by your own QOS not the ISPs. Of course, it's a lot more difficult
to regulate downstream then upstream anyway and depending on how the ISPs QOS (if any) is set up, it
may not help. But I believe it is useful sometimes.