It's just tc or the BSD equivalent under the hood, but it's point and click and easy to turn off.
More details at: http://mattgemmell.com/2011/07/25/network-link-conditioner-i...
It's just tc or the BSD equivalent under the hood, but it's point and click and easy to turn off.
More details at: http://mattgemmell.com/2011/07/25/network-link-conditioner-i...
I guess the advantage of a dedicated pain box is that any device, regardless of operating system, could use it. Network Link Conditioner (and the two pieces of software mentioned so far by siblings of your comment) are all OS X-specific. (That's another webdev gripe for another day.)
On Windows, there's a few mentioned here: http://stackoverflow.com/questions/1094760/network-tools-tha...
#create firewall bandwidth configuration
sudo ipfw pipe 1 config bw 15KByte/s
#add config to firewall
sudo ipfw add 1 pipe 1 src-port 80
#change. during testing
sudo ipfw pipe 1 config bw 115KByte/s
#delete. after testing
sudo ipfw delete 1I have bash aliases for various levels of ipfw throttling, but I've ended up using other programs because 768k/s with no latency seems to load some kinds of sites disturbingly close to the speed they load if I let the bandwidth back up to its 18mbit/s normal speed, which I think has to do with latency. Lots of the Mac OS standalone programs that do this kind of thing, like Link Conditioner or Speed Limit, add configurable latency to requests as well.
0: http://www.openbsd.org/faq/pf/
1: http://developer.apple.com/library/mac/#documentation/Darwin...