If you're developing Web or mobile applications, you'll certainly be confronted to poor network conditions.
The problem now is "how can I test my application under bad network conditions". Well you could rent a forein internet connection or use tools that reports performance from various remote countries however this is not a good debugging environment.
The solution is to use
TC and NetEM on your front development server (typically Web or reverse proxy server), then use filters so only one client station (the debugging station) is impacted.
Don't forget to use filter otherwise all your clients will be impacted.
Below an example on how to emulate a network with :
- 1Mbps bandwidth
- 400ms delay
- 5% packet loss
- 1% Corrupted packet
- 1% Duplicate packet
The debugging
client IP is 192.168.0.42 (i.e the IP impacted by the bad network performance);
The following commands need to be executed on the front developement server, please set the appropriate NIC for you environment (eth0 used below) :
# Clean up rules
tc qdisc del dev eth0 root
# root htb init 1:
tc qdisc add dev eth0 handle 1: root htb
# Create class 1:42 with 1Mbps bandwidth
tc class add dev eth0 parent 1:1 classid 1:42 htb rate 1Mbps
# Set network degradations on class 1:42
tc qdisc add dev eth0 parent 1:42 handle 30: netem loss 5% delay 400ms duplicate 1% corrupt 1%
# Filter class 1:42 to 192.168.0.42 only (match destination IP)
tc filter add dev eth0 protocol ip prio 1 u32 match ip dst 192.168.0.42 flowid 1:42
# Filter class 1:42 to 192.168.0.42 only (match source IP)
tc filter add dev eth0 protocol ip prio 1 u32 match ip src 192.168.0.42 flowid 1:42
To check that the rules are properly set use the following commands :
tc qdisc show dev eth0
tc class show dev eth0
tc filter show dev eth0
Once you're done with the testing, cleanup the rules with the command :
tc qdisc del dev eth0 root
There is many other options you can use (correlation, distribution, packet reordering, etc), please check the documentation available at :
http://www.linuxfoundation.org/collaborate/workgroups/networking/netem
If this setup fits your requirements, I advice you to create a shell script so you can start/stop the rules with custom values. Be aware that you can also make filters based on source/destination ports, etc.
If you have more complex requirements, you can try WANem, which is a live Linux Distribution with a graphical interface on top of NetEM. Please be aware that this requires route modifications on your client and server (or any other routing tricks).
http://wanem.sourceforge.net/
http://sourceforge.net/projects/wanem/files/Documents/WANemv11-Setup-Guide.pdf
I didn't had the opportunity to try it, please let me know if you have any feedback.
