TOTAL
Since dec 2006
1'942'871 Visitors
4'218'042 Pages

Nov 2010 Stats
82'909 Visitors
146'476 Pages
196 countries
Full statistics



Help us translate
our tutorials!

JOIN the
OpenManiak Team.
OM TEAM
Director:
Blaise Carrera
Tutorials creation:
Blaise Carrera
Translaters:
Giovanni Fredducci
Angel Chraniotis
Moham. H. Karvan
Alexandro Silva
Blaise Carrera
Andrei Chertolyas
Sergiy Uvarov
Nickola Kolev
Łukasz Nowatkowski
Ivo Raisr
Catalin Bivolaru
Bogdan A. Costea
Kirill Simonov
Oliver Mucafir
JaeYoung Jeon
Seungyoon Lee
Jie Yu & Si Cheng
Tao Wei
YukiAlex
Fumihito Yoshida
Muhammad Takdir
Çağdaş Tülek
Auditors
Leslie Luthi
Joe Anderson
Jennifer Ockwell
Nigel Titley
Alison Rees
Sabrina Barbey
Webmaster:
Blaise Carrera
WANEM - The Easy Tutorial - Basic Mode

WANem Basic mode
Last Change : Jul 05 2010 french flagenglish flag


Tool
Install
Ergonomy
Forum



Details What is WANem?
Screenshots
Prerequisites
Basic configurations
Network Scenarios
Basic mode
Advanced mode




If you like our tutorials, don't hesitate to support us and visit our sponsors!
Si vous aimez nos tutoriaux, n'hésitez pas à nous supporter et visiter nos sponsors!



After having launched and configured WANem successfully, we are now ready to use it.

The goal is to test from the client machine, the behaviour of your favorite software located on the server by simulating different network link qualities.

For the purpose of our test we will just use the Ping command and compare the results in different scenarios. Ping is set to send 1500 bytes icmp packets.
In your environment, the client could be an IP phone and the server a PBX such as Asterisk. An other example would be a client willing to reach centralised resources such as a Citrix server.

In this page we will study WANem basic mode. The WANem advanced mode tutorial is available if you need to configure detailed settings.



Start WANem

Click on "Apply settings". This will start WANem with blank settings.




C:\Documents and Settings\admin>ping 192.168.1.68 -t -l 1500
Pinging 192.168.1.68 with 1500 bytes of data:

Reply from 192.168.1.68: bytes=32 time=1ms TTL=127
Reply from 192.168.1.68: bytes=32 time=1ms TTL=127
Reply from 192.168.1.68: bytes=32 time=1ms TTL=127
Reply from 192.168.1.68: bytes=32 time=1ms TTL=127
Reply from 192.168.1.68: bytes=32 time=1ms TTL=127
    -> change applied
Reply from 192.168.1.68: bytes=32 time=1335ms TTL=127
Reply from 192.168.1.68: bytes=32 time=219ms TTL=127
Reply from 192.168.1.68: bytes=32 time=14ms TTL=127
Reply from 192.168.1.68: bytes=32 time=13ms TTL=127
Reply from 192.168.1.68: bytes=32 time=12ms TTL=127
Reply from 192.168.1.68: bytes=32 time=15ms TTL=127
Reply from 192.168.1.68: bytes=32 time=12ms TTL=127
The Ping command shows a "time" value which is the RTT or Round Trip Time. RTT is the time needed for a packet to travel between two hosts and come back.
We see that the RTT has increased from 1 ms to around 12-15ms due to the packets processing time on WANem.



Delay (Latency):

The delay also called latency is the one-way time needed for a packet to travel from a host to another host.
Latency or delay should not be confused with RTT which measures two-way latency.
If you have a symmetric network path and similar upload and download bandwidths, latency is basically equals to RTT divided by 2.

Latency is set to 100ms


C:\Documents and Settings\admin>ping 192.168.1.68 -t -l 1500
Pinging 192.168.1.68 with 1500 bytes of data:

Reply from 192.168.1.68: bytes=1500 time=9ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=8ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=7ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=6ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=7ms TTL=127
    -> change applied
Reply from 192.168.1.68: bytes=1500 time=210ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=209ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=208ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=210ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=209ms TTL=127
The RTT has increased by 200ms because the 100ms latency has been applied to packets in both directions.



Predefined Bandwidth:

You can set a predefined bandwidth in the scrolling list. The bandwith value will be applied in both directions.

Select "DS-0, Pulse Code Modulation - 64Kbps"

As a reminder, the bandwith is generally displayed in bit/s or b/s and an amound of data such as a hard drive capacity in byte or B. As 1 byte is equals to 8 bits, 64 Kb/s is equals to 8KB/s.


C:\Documents and Settings\admin>ping 192.168.1.68 -t -l 1500
Pinging 192.168.1.68 with 1500 bytes of data:

Reply from 192.168.1.68: bytes=1500 time=8ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=7ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=9ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=7ms TTL=127
    -> change applied
Reply from 192.168.1.68: bytes=1500 time=1049ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=767ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=726ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=685ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=644ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=599ms TTL=127
The response time has greatly increased because of the bandwith restriction.



Customized bandwidth:

To select a customised bandwidth, select "Other" in the scrolling list and set your value in the bandwidth field.

The bandwidth is set to 1500


C:\Documents and Settings\admin>ping 192.168.1.68 -t -l 1500
Pinging 192.168.1.68 with 1500 bytes of data:

Reply from 192.168.1.68: bytes=1500 time=14ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=13ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=12ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=15ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=14ms TTL=127
    -> change applied
Request timed out.
Reply from 192.168.1.68: bytes=1500 time=43ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=42ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=41ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=23ms TTL=127
Reply from 192.168.1.68: bytes=1500 time=41ms TTL=127
The response time has increased to around 40ms. This result could be compared with the previous one when the bandwidth is set to 64kbit/s.



Bandwidth and Latency

Bandwidth and latency can also be set together.

Important notice:
As of 1.2 version, WANem does not provide a correct behaviour when several settings are used together. So for the moment use only one setting at a time.


Top of the page





If you liked our tutorials, don't hesitate to support us and visit our sponsors!
Si vous aimez nos tutoriaux, n'hésitez pas à nous supporter et visiter nos sponsors!