Simulating a bad internet connection

Question

I'm developing an embedded device which has access to the internet through LAN. I'm in the testing phase now, and I would like to test how the device performs when the connection to the internet is poor. Currently, the device is connected to a router through a hub, which I use to monitor the packets with Wireshark. What's the best way to throttle down the internet speed of the device to mimic a scenario that may happen?

Can I do it through a PC? Do I need access to the router? If so, is it possible to limit the speed of each IP in the router interface?

Actually, a friend suggested that I will purchase a usb2lan ethernet card, and to bridge the PC lan connection to the embedded device, and then using a software QoS limiter. do you think it will work ?

Answer 1

You can try using "Fiddler"

You have options to simulate bad network (like old modems 33k or 56k)

You need to plug in your device to your PC and turn on the proxy (every request will be transfered through Fiddler)

Then you could test your code with a bad network then see what happening ;)

Answer 2

If you have a Mac handy, Macs have kernel facility called dummynet built in, which you control through ipfw. It allows you to simulate a slow connection, randomly drop packets with certain probabilities, and more.

The same facility exists in Linux and other OSes.

From the dummynet homepage:

As of Feb.2010 we have released the third major version of dummynet, which now runs on all main platforms: FreeBSD, Mac OS X as part of the native distributions, and you can find Linux, OpenWRT and Windows versions here.

It can do a lot for you:

limit the total incoming TCP traffic to 2Mbit/s, and UDP to 300Kbit/s

ipfw add pipe 2 in proto tcp
ipfw add pipe 3 in proto udp
ipfw pipe 2 config bw 2Mbit/s
ipfw pipe 3 config bw 300Kbit/s

limit incoming traffic to 300Kbit/s for each host on network 10.1.2.0/24.

ipfw add pipe 4 src-ip 10.1.2.0/24 in
ipfw pipe 4 config bw 300Kbit/s queue 20 mask dst-ip 0x000000ff

simulate an ADSL link to the moon:

ipfw add pipe 3 out
ipfw add pipe 4 in
ipfw pipe 3 config bw 128Kbit/s queue 10 delay 1000ms
ipfw pipe 4 config bw 640Kbit/s queue 30 delay 1000ms

Answer 3

This is another OSX solution, have a look at the Network Link Conditioner.

The following quote is ripped from the following blog (All credit for the below should go to Matt Gemmell):

http://mattgemmell.com/2011/07/25/network-link-conditioner-in-lion/

Get the Hardware IO Tools for Xcode. To do this, go into the Xcode menu, then choose “Open Developer Tool” and finally “More Developer Tools…”. You’ll be taken to Apple’s developer downloads site; you should download the “Hardware IO Tools for Xcode”.

The resulting disk image will contain (amongst other things) a preference pane for System Preferences, called “Network Link Conditioner”. Double-click the prefpane file and authenticate to allow it to be installed. You’ll then see the pane in System Preferences.

You can choose from various different types of network conditions using the Profile popup menu.

You can also add profiles of your own by clicking Manage Profiles, either from scratch or via duplicating an existing profile.

Extremely handy for simulating less than optimal network conditions while testing an app. Just don’t forget to switch it off afterwards!

Answer 4

You may use (almost) any linux distribution from liveCd (like ubuntu, mandriva, others) to run it on any hardware you want, and use the kernel-based tool netem, aka "Network Emulation" with the "iproute2" package tools. It lets you control delays, package loss, corruption, duplication and other possible problems of wide area network.

There is list of most used simulations, like:

• Rate control using Token Bucket Filter:

  tc qdisc add dev eth0 root handle 1:0 netem delay 100ms
  tc qdisc add dev eth0 parent 1:1 handle 10: tbf rate 256kbit buffer 1600 limit 3000
  

• Delay all packets by fixed time: tc qdisc add dev eth0 root netem delay 100ms

• Package loss: tc qdisc change dev eth0 root netem loss 0.1%