iPerf3

 Today I worked on installing and using iperf, which is a tool for measuring network performance.  I used my PC as the server and my Raspberry Pi as the client. After the tool was downloaded on both machines, the results looked like this:

From the server side (PC)


C:\Users\James>cd C:\iperf


C:\iperf>iperf3.exe -s

-----------------------------------------------------------

Server listening on 5201 (test #1)

-----------------------------------------------------------

Accepted connection from 10.0.0.94, port 35190

[  5] local 10.0.0.93 port 5201 connected to 10.0.0.94 port 35194

[ ID] Interval           Transfer     Bitrate

[  5]   0.00-1.01   sec  4.38 MBytes  36.3 Mbits/sec

[  5]   1.01-2.01   sec  5.12 MBytes  42.9 Mbits/sec

[  5]   2.01-3.01   sec  4.88 MBytes  41.0 Mbits/sec

[  5]   3.01-4.00   sec  4.62 MBytes  39.1 Mbits/sec

[  5]   4.00-5.00   sec  5.12 MBytes  43.0 Mbits/sec

[  5]   5.00-6.00   sec  4.88 MBytes  40.8 Mbits/sec

[  5]   6.00-7.01   sec  5.00 MBytes  41.6 Mbits/sec

[  5]   7.01-8.00   sec  4.12 MBytes  34.9 Mbits/sec

[  5]   8.00-9.01   sec  5.00 MBytes  41.9 Mbits/sec

[  5]   9.01-10.01  sec  5.00 MBytes  41.9 Mbits/sec

[  5]  10.01-10.03  sec   128 KBytes  51.6 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval           Transfer     Bitrate

[  5]   0.00-10.03  sec  48.2 MBytes  40.4 Mbits/sec                  receiver

-----------------------------------------------------------

Server listening on 5201 (test #2)

-----------------------------------------------------------

From the Client Side (Raspberry Pi)

james@PI5:~ $ iperf3 -c 10.0.0.93

Connecting to host 10.0.0.93, port 5201

[  5] local 10.0.0.94 port 35194 connected to 10.0.0.93 port 5201

[ ID] Interval           Transfer     Bitrate         Retr  Cwnd

[  5]   0.00-1.00   sec  5.79 MBytes  48.6 Mbits/sec    0    314 KBytes       

[  5]   1.00-2.00   sec  5.90 MBytes  49.5 Mbits/sec    0    503 KBytes       

[  5]   2.00-3.00   sec  5.81 MBytes  48.7 Mbits/sec    0    693 KBytes       

[  5]   3.00-4.00   sec  5.00 MBytes  41.9 Mbits/sec    0    708 KBytes       

[  5]   4.00-5.00   sec  5.00 MBytes  41.9 Mbits/sec    0    708 KBytes       

[  5]   5.00-6.00   sec  3.75 MBytes  31.5 Mbits/sec    0    820 KBytes       

[  5]   6.00-7.00   sec  5.00 MBytes  41.9 Mbits/sec    0    962 KBytes       

[  5]   7.00-8.00   sec  5.00 MBytes  41.9 Mbits/sec    0    962 KBytes       

[  5]   8.00-9.00   sec  5.00 MBytes  41.9 Mbits/sec    0    962 KBytes       

[  5]   9.00-10.00  sec  5.00 MBytes  41.9 Mbits/sec    0    962 KBytes       

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval           Transfer     Bitrate         Retr

[  5]   0.00-10.00  sec  51.2 MBytes  43.0 Mbits/sec    0             sender

[  5]   0.00-10.03  sec  48.2 MBytes  40.4 Mbits/sec                  receiver


iperf Done.




Comments

Post a Comment

Popular posts from this blog

ARP--Address Resolution Protocol

 ARP is a program that helps connect an IP address to a physical address (MAC) over a Local Area Network.   An analogy/pneumonic device.   Apartment's  Real  Person The IP address on a local address is like an apartment's address in a city. It's helpful to get packages delivered, but it doesn't tell the carrier which apartment it is going. ARP helps the packet get from the apartment gate to the apartment door.  Apartment's Real Person.  
Read more

HSRP Configuration

Image
I began by configuring HSRP for the 10.10.10.0/24 using the IP addresses shown in the topology above. My first step was to check to see if G0/1 has been configured on R1 & R2.   It was not on either router, so I configured them and added a virtual IP address.    After that, I checked to see which was the active router (R2). Then, I checked to see that PC2 could ping the default gateway 10.10.10.1, followed by testing upstream connectivity.   I finished this portion of the lab by checking MAC addresses on the active router, the virtual interface, and PCs.  
Read more

OSPF--Load Balancing

Image
The lab configuration entails three network hops from R1 to reach R4, passing through R2, while there are only two hops from R5. As all the interfaces are Fast Ethernet, there would be an excessive load on R5 which could cause issues.  To solve this problem, I configured the links between R1 to R5 and then R5 to R4 at the cost of 1500.   Two hops at 1500 = total cost of 3000. Three hops at 1000 (Previously set at auto-config) = 3000.  So now the traffic should be redistributed evenly. It worked!  
Read more