What's your strategy towards traffic prioritization/management.

I am not really to just get a list of packet shaping solutions. Instead, I would like to get recommendations about traffic management strategies that include:

  • What software/hardware products you use, or have used
  • How this solution is/was implemented
  • Why would you recommend (or not) this solution/strategy

Here are some solutions I've heard of, but haven't had much (if at all) experience with them:

Some notes:

  • I'm debating myself whether or not to include pricing information
  • This is assuming you have the NEED for traffic management

closed as not a real question by Mark Henderson Jan 16 '12 at 3:42

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

locked by HopelessN00b Dec 5 '14 at 9:50

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. See the help center for guidance on writing a good question.

Read more about locked posts here.


I like using squid with the delay pools option as a really simple starting point. The weakness of this solution is that it will only help with types of traffic that can be forced through the proxy.

To set it up you just put squid on your edge device configure as needed. The configure the clients for protocols that cannot be transparently intercepted.


There's a wonderful HowTo for Linux on advanced routing and traffic control. It includes a very nice section on bandwidth management by classifying traffic.

  • I'm familiar with this as far as being an option, is this a recommendation based on actual experience? If so, please give more details about this solutions if you can. Thanks! – l0c0b0x May 16 '09 at 22:23
  • Speaking of lartc, I haven an open question looking for tools to manage tc easier. (serverfault.com/questions/2986/linux-tc-policy-routing-tools) – Zoredache May 16 '09 at 22:56

Netequalizer has put together a page that lists what users have been saying on independent blogs, forums and listservs. So, it's a good way to get some feedback from people who are actually using it -- http://netequalizernews.com/about-the-netequalizer/what-netequalizer-users-are-saying/


I have done quite a bit of work with Packeteer devices. They are the defacto corporate standard product for managing bandwidth I think.

They are hardware devices that sit inline, you can then limit traffic by machine or by application. You can setup both priorities and hard limits.

So for example, you can setup your WAN link to put email as a low priority, using say 256k only. You could setup RDP traffic to be top priority and have as much nadwidth as you think it would need. In fact you can set a limit for a protocol over all and per connection in that protocol.

Packetter devices are pretty simple to get right, but there is a lot of advanced features to play with. I'd recommend them. Of course they are not cheap... sorry.

Not the answer you're looking for? Browse other questions tagged or ask your own question.