Test the network using iperf

  1. Install iperf and iperf3
  2. on server side, issue below command to listen on specific port, for example, port 80

    iperf3 -c 54.252.131.163 -p 80 -i 1 t 10

  3. on client side, issue below command to start testing

    iperf3 -c 54.252.131.163 -p 80 -i 1 t 10 ( i = interval, t=how long, all in seconds )

    You might need to run for long time then visualize the data to analyse the network bottleneck

Simple but quite powerful command

Standard error (stderr)

[root@ip-192-168-1-57 ec2-user]# fdafda > error.txt

bash: fdafda: command not found

[root@ip-192-168-1-57 ec2-user]# cat error.txt

[root@ip-192-168-1-57 ec2-user]#

[root@ip-192-168-1-57 ec2-user]# fdafda 2> error.txt

[root@ip-192-168-1-57 ec2-user]# cat error.txt

bash: fdafda: command not found

Redirect Stderr to Stdout

[root@ip-192-168-1-57 log]# ls -ly > lstest.txt 2>&1   (2> means stderr, &1 means stdout )

[root@ip-192-168-1-57 log]#

[root@ip-192-168-1-57 log]#

[root@ip-192-168-1-57 log]# more lstest.txt

ls: invalid option — ‘y’

Try ‘ls –help’ for more information.