Ladies and Gents,
after further analyzing the situation I have noticed that my traffic
optimization rules do not really seem to identify traffic with the rules ALL
protocols 1-9999 ports. Why is that ?
The rule that works is the one where the packets identified by SRC/DST ip
address.
Please see screenshots below.

--Yarick

On 10/23/05, YARICK <yarick at yarick dot com> wrote:
>
> Your weights for the queques sound reasonable.
> Question: if the bandwidth 10 or 100 MBPS
> Would it be enough to simply create a PIPE for voip and a smaller pipe for
> verything else,
> While setting IP Type of Service (TOS) to the best possible setting for
> VOIP traffic.
> Without using QUEs.
>
> http://www2.tjwv.com/listing/Yarick/MONOWALL.jpg
>
>
>
> On 10/23/05, Chris Bagnall <m0n0wall at minotaur dot cc> wrote:
> >
> > Be aware that different devices use different RTP port ranges. Asterisk
> > defaults to 10000-20000, but this is easily configurable in rtp.conf.
> > Grandstream devices tend to use 5004-5008, I'm sure other devices
> > (sipura,
> > cisco, etc.) all use different ranges.
> >
> > What would be useful is to know how you've arranged the weights on your
> > queues. I tend to shove VoIP queues with a weight of 80, generic net
> > access
> > around a weight of 17, leaving 2 for "hated" (FTP, etc.) and 1 for
> > "despised" (BitTorrent, etc.)
> >
> > Regards,
> >
> > Chris
> > --
> > C.M. Bagnall, Director, Minotaur I.T. Limited
> > This email is made from 100% recycled electrons
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> >
> >
>