Cnistnet controls Network Packet Loss

Use of cnistnet

(14:30:19)

{
Function onclick ()
{
Scope. articel_quote_alert & scope. articel_quote_alert ('5548dcdb0100a5tz '); Return false;
}
} "Href =" javascript:; "> Reprinted

Tags: Cnistnet Miscellaneous

Category: Technical logs

64 bytes from 192.168.7.86: icmp_seq = 36 TTL = 64 time = 100 MS
64 bytes from 192.168.7.86: icmp_seq = 37 TTL = 64 time = 100 MS

--- 192.168.7.86 Ping statistics ---
38 packets transmitted, 34 encoded ed, 10% packet loss, time 37055 Ms
RTT min/AVG/max/mdev = 100.363/100.594/102.102/0.495 MS, pipe 2
[Root @ localhost nistnet-3.0a] # cnistnet-u-A 192.168.7.88 192.168.7.87 -- delay 100.000 -- bandwidth 200000 -- drop 5
Addnistnet: 192.168.7.88: 0 to 192.168.7.87: 0 (prot 0 cos 0 ),
Delay 100.000000 (Sigma 0.000000 Corr 0.000000 ),
Bandwidth 200000, drop 5.000000 (Corr 0.000000 ),
DUP 0.000000 (Corr 0.000000 ),
Drdmin 0, drdmax 0, drdcongest 0
[Root @ localhost nistnet-3.0a] # cnistnet-R
Cnistnet-A 192.168.7.88 192.168.7.87 -- delay 100.000 -- drop 5.0003 -- bandwidth 200000
Cnistnet-A 192.168.7.86 192.168.7.87 -- delay 100.000 -- drop 5.0003 -- bandwidth 200000
[Root @ localhost nistnet-3.0a] #

The above is the command script of the basic server. Generally, you can use cnistnet-u to check whether it is started. If it is not started, a script without a directory will be reported, after the startup, use cnistnet-R to view the status. You can view the latency, jitter, and packet loss related to the control.

It is found that the cnistnet software is still good and can simulate and test the network conditions. However, to load some library files, the above test is carried out in the Linux as4 update5 system.