Transmission Control Protocol and Data
EL 5373
INTERNET ARCHITECTURE AND PROTOCOLS
RAVI RANDERIA
12567470
rbr294@nyu.edu
WORKSTATION: DESDEMONA-FENCHI MAC: f8:0f:41:c4:7f:a8
LAB REPORT 5
PAGES [6]
Exercise 1: iperf3 -s -p 5555: On execution of this command, the host is prompted to run on server mode and the server is made to listen or connect to port number 5555.
iperf3 -c 192.168.1.17 -p 8911 –u: Here, the host is prompted to run on client mode, connecting on port 8911 with server having IP address 192.168.1.17. The host is prompted to use UDP instead of TCP.
iperf3 -c 192.168.1.17 -p 8911 -n 10K -l 200: Here, the host is prompted to run on client mode, connecting on port number 8911 with server having IP address 192.168.1.17. The number of bytes to be transmitted is 10K and the length of the buffer is fixed at 200 bytes.
The length of the packet at the application layer of the second command 65507 bytes, which is the default maximum value of an UDP packet that can be transmitted even with fragmentation (since the length of the packet is not specified we came to this conclusion).
Yes, it makes a difference because in order to perform an iperf3 command, the user must establish both a client and server and hence, the server must be running.
Exercise 3:
Here we use “sudo tcpdump -enx -vv src host <your_host> and not tcp” command to capture all the packets originating from my host and “iperf3 -c <remote_host_running_server> -u -l <size> -n <size>” is used to send UDP datagram with given payload size to remote host while the remote host uses “iperf3 -s” to exexute an iperf3 server. 1472 bytes is the maximum value of data for a UDP datagram which is sent without fragmentation. This is observed from the tcpdump output for a fragment of 1473 bytes. We see that two fragments are being made. The first fragment is of 1480 bytes with an offset of 0 bytes and the second fragment is of 1 byte. Its seen from the ifconfig output given below that 1500 bytes is the MTU for an Ethernet
INTERNET ARCHITECTURE AND PROTOCOLS
RAVI RANDERIA
12567470
rbr294@nyu.edu
WORKSTATION: DESDEMONA-FENCHI MAC: f8:0f:41:c4:7f:a8
LAB REPORT 5
PAGES [6]
Exercise 1: iperf3 -s -p 5555: On execution of this command, the host is prompted to run on server mode and the server is made to listen or connect to port number 5555.
iperf3 -c 192.168.1.17 -p 8911 –u: Here, the host is prompted to run on client mode, connecting on port 8911 with server having IP address 192.168.1.17. The host is prompted to use UDP instead of TCP.
iperf3 -c 192.168.1.17 -p 8911 -n 10K -l 200: Here, the host is prompted to run on client mode, connecting on port number 8911 with server having IP address 192.168.1.17. The number of bytes to be transmitted is 10K and the length of the buffer is fixed at 200 bytes.
The length of the packet at the application layer of the second command 65507 bytes, which is the default maximum value of an UDP packet that can be transmitted even with fragmentation (since the length of the packet is not specified we came to this conclusion).
Yes, it makes a difference because in order to perform an iperf3 command, the user must establish both a client and server and hence, the server must be running.
Exercise 3:
Here we use “sudo tcpdump -enx -vv src host <your_host> and not tcp” command to capture all the packets originating from my host and “iperf3 -c <remote_host_running_server> -u -l <size> -n <size>” is used to send UDP datagram with given payload size to remote host while the remote host uses “iperf3 -s” to exexute an iperf3 server. 1472 bytes is the maximum value of data for a UDP datagram which is sent without fragmentation. This is observed from the tcpdump output for a fragment of 1473 bytes. We see that two fragments are being made. The first fragment is of 1480 bytes with an offset of 0 bytes and the second fragment is of 1 byte. Its seen from the ifconfig output given below that 1500 bytes is the MTU for an Ethernet