Hi FurryNutz,
I'm currently on Firmware Version 1.00.B11 ( I may upgrade and try version 1.02 next weekend if I'm bored)
https://iperf.frIPerf which is a freeware application that can run under a variety of operating systems such as Windows, MAC OS and Linux. The application requires
two machines where one acts as a listening Server and one as a sending Client. ( I'm using a Macbook pro and a Synology NAS ).
IPerf generates traffic from the Client side towards the Server side and the results are displayed on how much traffic we were able to send under a specific time window and what throughput was achieved.
You might be curious to choose another application like FTP or Windows file sharing, however, there is an important detail to highlight here, FTP/SMB relies on the disk read/write speeds, Iperf does not since it is traffic handling on the NIC itself. So in case you are having some really old IDE type Hard Drive on your Server side results will be affected in a negative way. Windows file sharing also can have varying speeds depending on Microsoft proprietary file transfer protocol which lower down the speeds in certain cases. So the bottom line for this is to use IPerf for throughput testing, if you want to test write speed over the network they've added a feature in the latest version to do so.
- Download the executables for both machines ( Client and Server ) https://iperf.fr/iperf-download.php
- Decide which machine is the server and which is the client
- Run the commands below in "quotes" ( Do not type the quotes)
- Machine1 ( Server ) : "/usr/local/bin/iperf3 -s" The server machine is now listening for iperf connections
- Machine2 ( Client ) : "/usr/local/bin/iperf3 -c xxx.xxx.xxx.xxx -t 5" replace xxx. with the ip address of your server machine. This will test the throughput for 5 seconds.
You should see results similar to this
On the server when you start listening you should see something like so:
MacBook-Pro:iperf$ /usr/local/bin/iperf3 -s
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
On the client machine, you should see something like so: ( Note the -T argument lets you give the test a name)
MacBook-Pro:iperf$ /usr/local/bin/iperf3 -c 192.168.0.163 -t 5 -T Ethernet
Ethernet: Connecting to host 192.168.0.163, port 5201
Ethernet: [ 4] local 192.168.0.123 port 55749 connected to 192.168.0.163 port 5201
Ethernet: [ ID] Interval Transfer Bandwidth
Ethernet: [ 4] 0.00-1.00 sec 113 MBytes 944 Mbits/sec
Ethernet: [ 4] 1.00-2.00 sec 112 MBytes 939 Mbits/sec
Ethernet: [ 4] 2.00-3.00 sec 112 MBytes 940 Mbits/sec
Ethernet: [ 4] 3.00-4.00 sec 112 MBytes 940 Mbits/sec
Ethernet: [ 4] 4.00-5.00 sec 112 MBytes 940 Mbits/sec
Ethernet: - - - - - - - - - - - - - - - - - - - - - - - - -
Ethernet: [ ID] Interval Transfer Bandwidth
Ethernet: [ 4] 0.00-5.00 sec 561 MBytes 941 Mbits/sec sender
Ethernet: [ 4] 0.00-5.00 sec 561 MBytes 941 Mbits/sec receiver
Ethernet:
Ethernet: iperf Done.
There's a really good write up on iperf here:
https://www.es.net/assets/Uploads/201007-JTIperf.pdfThere seems to be a windows GUI versions here
http://www.iperfwindows.com https://www.perfsonar.net/media/cms_page_media/3407/1.1-TCP-Labs.pdfI'm sorry it's not a very detailed guide, however, hopefully this information is useful and will help some people debug network errors as speedtest.net is not the best way.
Wes