I actually made a mistake in my post: I should have said to use a separate pair
of pipes to dedicate bandwidth to your Vonage connection instead of queues.
When I was testing m0n0wall with my Vonage connection, I tried using one set of
pipes with VOIP packets assigned to the highest priority queue but still had too
many dropped packets no matter what priority levels were selected when other
traffic was significant.
I ended up setting the second pair of pipes dedicated to VOIP traffic to 128
kbit/s although this number is not critical as long as it is higher then the
VOIP bandwidth. Keep in mind that the used VOIP bandwidth and all other
bandwidth still has to be below your connection speed for the traffic shaper to
be effective. The flaw with this setup is that the VOIP bandwidth can not be
borrowed for other purposes when not needed for VOIP without using a different
On a side note, I hate using the term "bandwidth" for something measured in bits
per second. :(
On Fri, 15 Sep 2006 07:26:45 -0700, you wrote:
>To answer some of your questions, I was able to connect by plugging the
>Vonage adapter directly into the cable modem. I already have a separate set
>of queues set up for Vonage, and I only switched to Vonage after I got cable
>Internet. I'm fairly sure that if I can dedicate bandwidth to vonage rather
>than prioritise it that this will clear up. I'll also try to post my config
>files again (30 KB limit again).
>Thanks for your help,