I realize this answer is a bit late and probably isn't quite what you are looking for, but I recently did something similar for a client.
What I did was pretty simple, establish 2 connections and toggle between the two. First pick a stable connection source, fiber, cable, DSL what have you. Then pick a high latency connection with significant packet loss, Satellite, WiMax/3g (Clear or Sprint in a weak area or indoors for instance), etc. Once you establish a base line on the good connection, you can toggle at will to the more fragile connection and compare the differences. Furthermore if 802.11a/b/g/n are options for your testing environment, an even simpler solution might be to run the test(s) directly connected to the router or immediately adjacent to it, with high signal power vs turning the router output power down to the bare minimum, on a noisy channel, and putting some distance between yourself & the router to weaken the signal as much as possible. This option allows you to test semi-real world scenarios and lets you see how environmental factors will affect packet loss. Obviously the second option only tests behavior on a single connection type but it does make it easy to have fairly granular control over your testing regime while still evaluating close to real world scenarios. Anyways, the group probably has better solutions, but these ideas are what immediately came to my mind and I didn't see anything about stressing the connection itself, so I figured I'd chime in. Sincerely, Steve /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
