Goosemaster
Lifer
I am using multiple rules and such for various services. What would an appropriate rule/ruleset be for basic web browsing?Should prioritizing DNS lookups and HTTP downloads be enough?
That is what I am doing right now and unfortuantely the results have gotten pretty bad recently. ( I raised the connection ceiling on BT from like 200-400 to 800 😱)
We are talking about 2000ms+ pings when the WAN is under full load (BT + VoIP + a few people browsing + IM etc simultaneously). I was using multiple pipes since they seemed to focus more on providing usage ceilings when I want to focus on minimums (guarenteed bandwidth allotments). Services like VoIP had their own dedicated pipe but the resutls weren't promsing, so I lumped everything back into two generic upload and a download pipes. My queues seem to be in order for these two pipes but you never know.....maybe I made a mistake and should go back to multiple pipes.
In addition, for the http download rule, should the source port be set to *.* ?
I would just like to have a discussion on my traffic shaping problems.
Thanks
That is what I am doing right now and unfortuantely the results have gotten pretty bad recently. ( I raised the connection ceiling on BT from like 200-400 to 800 😱)
We are talking about 2000ms+ pings when the WAN is under full load (BT + VoIP + a few people browsing + IM etc simultaneously). I was using multiple pipes since they seemed to focus more on providing usage ceilings when I want to focus on minimums (guarenteed bandwidth allotments). Services like VoIP had their own dedicated pipe but the resutls weren't promsing, so I lumped everything back into two generic upload and a download pipes. My queues seem to be in order for these two pipes but you never know.....maybe I made a mistake and should go back to multiple pipes.
In addition, for the http download rule, should the source port be set to *.* ?
I would just like to have a discussion on my traffic shaping problems.
Thanks
