iPerf is a tool for active measurements of the maximum achievable bandwidth on IP networks, and can be used to diagnose connection issues. Especially useful it can be to test connection issues between Radioserver and Dispatcher PCs, from repeaters to radioserver and so on.
You can get it via the following link: http://iperf.fr/iperf-download.php
To use iPerf to test connection from one network node to another you can do the following:
1) Install iPerf on both testing PCs. In case if you want to test radioserver-to-repeater connection, you will need to temporarily remove repeater from radionetwork, and replace it with a testing laptop with iPerf installed.
2) Start one instance of iperf as a "server". To do so, you need to start command promt in iPerf installation folder, and input a following command:
iperf -s -u -p 18500
This will start iPerf in server mode, listening on UDP 18500 port. Port number can be changed to whatever you need.
If you need to test TCP connection, remove "-u".
3) Start another iPerf instance on another PC as a client. To do so issue the following command:
iperf -c 192.168.10.10 -u -p 18500
This will start iperf as a client, trying to connect to mentioned IP address - 192.168.10.10 which must be replaced in your case by IP address of iPerf server.
Port number can be changed to any port you need to check (must be same as a port number that the server listens to)
If you are testing TCP connection, remove "-u"
4) There can be several different outcomes:
4a - "Success" - this data on client side shows the connectio is established and data is sent properly.
------------------------------------------------------------
Client connecting to 192.168.10.10, UDP port 18500
Sending 1470 byte datagrams
UDP buffer size: 63.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.10.10 port 55209 connected with 192.168.10.10 port 18500
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec
[ 3] Sent 893 datagrams
[ 3] Server Report:
[ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec 0.183 ms 0/ 893 (0%)
Also, on the server side:
------------------------------------------------------------
Server listening on UDP port 18500
Receiving 1470 byte datagrams
UDP buffer size: 63.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.10.10 port 18500 connected with 192.168.10.10 port 55209
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec 0.063 ms 0/ 893 (0%)
4b - "Failure" - In this case you get the report on client side:
------------------------------------------------------------
Client connecting to 192.168.10.10, UDP port 18500
Sending 1470 byte datagrams
UDP buffer size: 63.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.10.10 port 65213 connected with 192.168.10.10 port 18500
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec
[ 3] Sent 893 datagrams
[ 3] WARNING: did not receive ack of last datagram after 10 tries.
This WARNING at the end is showing that the server did not respond to the sent packets.
On the server side there will be no data about incoming connections.
So, depending on what result you get you can see if it is possible to establish needed connection using provided information or not.
Comments