Bullshit. I've used Packeteers at two different companies, and they blow chunks. They do the actual job of throttling very well, but the matching algorithms are near worthless.

Say, for example, you want to give a certain priority to a set of networks. In addition, you want to give a different priority to HTTP data. The Packeteer will match the "first" one. But there's no way to determine what the "first" one is going to be. Actually, you can force one to be first, but it also puts it before any other rules. So if you have anything even remotely complex, you're screwed.

You'd think that you could have matching rules and sub-rules. But you can't. So if you want to apply one priority to other campus networks, another to HTTP traffic, and another to HTTP traffic on other campus networks, you have to create three separate rules. This is a pain to create and to administer, but it ought to work okay, right? Well, no, because there is apparently no "AND" rule, so there's no way to say "HTTP and destination". I feel sure that I must be wrong about this, despite having looked for it for over a year. Let's assume I am wrong; then it should work okay, right? Nope, because there is a maximum limit for the global number of rules you can define, and if your networks are disjoint and you have to list a dozen each time, you run out really quickly.

I would never, ever, recommend Packeteer to anyone. Well, if it was free or cheap, it would be okay, but as Taym points out, it's wildly expensive, and the cost of your license is based on how much traffic it will deal with.

In summary, forget anyone ever mentioned it.