In addition to Bills notes, be sure to check out this thread: http://forum.pfsense.org/index.php?topic=821.0
In a nutshell, the p2p catch all flag in addition to make sure you lower or raise all protocols possible on the lower / raise screen. Scott On 4/26/06, Bill Marquette <[EMAIL PROTECTED]> wrote: > On 4/26/06, mOjO <[EMAIL PROTECTED]> wrote: > > the epic struggle continues... > > i have Cable internet with a 8mb download and 768kb upload. my pfSense > > box is an old AMD K6-2 350mhz box with 128MB ram. > > i used the traffic shaper wizard (god bless the wizard) to configure my > > QoS and it does work but i want to even further prioritize the Vonage > > because when the torrents are really going i sometimes hear weird audio > > "artifacts" and while I hear the other end fine (plenty of downstream > > b/w) the other end complains of me breaking up and there is definitely a > > noticable 1-2 sec. delay in their response. I just got off the phone and > > it was usable but a bit choppy on his end and it cut me off twice. > > Right now I have 3 active torrents and 2 seeding with total download > > around 90KB/sec and upload around 53KB/sec, pfSense shows 1500 states, > > 29% memory usage, and a steady 15-25% CPU usage. everything appears to > > be registering in the appropriate queues (I can see the VoIP queue go up > > when i talk and the P2P queue is active as well). So I want the Vonage > > to work flawlessly despite the abuse i put my WAN link through. I have > > opened and forwarded UDP 5060-5061 to the vonage router which is on my > > regular internal lan. > > > > The QoS settings are really greek to me and i've perused some docs which > > do explain the settings to some degree but i'm still not sure what > > really helps vonage work smoothly. Can anybody reccomend any settings > > changes beyond what the wizard sets for vonage? > > Reserve more outbound (qVOIPUp queue) bandwidth for vonage. Also, > shrink the outbound bandwidth on the root queue (qWANRoot). You might > be slightly starving the VOIP queues. You didnt' mention what type of > provider you have, but here are some useful tips. > > No ISP gives you the exact bandwidth you pay for (unless you are a > business class customer - and even then, look at your contracts). > ALTQ needs a little headroom to queue packets - I'd recommend shaving > off a couple dozen Kbit/second - but this is where traffic shaping > becomes a fine art...shave off until it "feels right". > > PPPOE has overhead. A 768K circuit is 768K _inclusive_ of the > transport - which will likely include PPPOE framing and probably ATM > framing. A good rule of thumb with PPPOE is to subract close to 20% > of your circuit speed (again...tweak until it starts sucking and back > off a hair). > > VOIP is extremely sensitive to dropped or delayed packets - put a max > ceiling on your P2P if this becomes a problem. Make use of the > artificial ceiling that most BT clients have, don't rely on the shaper > to do it for you. > > Traffic shaping helps, but it's not perfect. Bottom line is that an > oversubscribed line is going to suck regardless of how you tweak the > shaping - although you can make it tolerable with shaping as opposed > to completely intolerable. > > The wizard is a good starting point (we need people to document it > well). Here's a good resource to read > http://wiki.pfsense.com/wikka.php?wakka=HFSCBandwidthShapingNotes > > > --Bill > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
