Internet connection speed test from the device
Usually, Internet connection speed is measured directly from the router's local network using a PC or mobile device. This test can be performed in various ways, as described in detail in the guide How to measure the Internet connection speed?.
However, you can also measure your Internet connection speed directly from the device. This method is possible for both local and remote connections to the router. This can be done using the throughput testing utility iPerf. The iPerf3 package is included in the KeeneticOS router operating system starting with version 5.0.
To use iPerf, you need to first install the iPerf3 system component on the device. This can be done on the General System Settings page in the KeeneticOS Update and Component Options by clicking Component options.
The iPerf utility settings will appear on the Diagnostics page in the Network Connection Test section. Select iPerf and click Show settings.
In the Server address field, enter the IP address of the public IPerf3 server that will be used for testing. You can find the addresses of public IPerf3 servers on the Internet.
In the utility settings, you can also select the IP version (IPv4 / IPv6), protocol (TCP / UDP), traffic direction (Inbound — for testing incoming traffic / Outbound — for testing outgoing traffic), port number (default is 5201, we recommend not changing the default value), bitrate, number of streams (default is 1, we recommend not changing the default value), data transfer limit (seconds / bytes).
To run the test, click the Start the test button. In this case, the iPerf3 client on the router will connect to the specified iPerf3 server, and then data will be transferred between them to measure the bandwidth of the Internet channel.
İpucu
For more accurate results, we recommend using a server located in your region.
Use TCP* protocol testing without limiting the maximum speed, setting the test time to at least 10 seconds (usually 10 to 30 seconds is sufficient to measure the bandwidth of the Internet channel).
* — Do not use the UDP protocol when measuring the internet connection speed from a router. Unlike TCP, UDP does not use packet delivery control or transmission speed control algorithms, and it behaves differently on the network.
During testing, a fairly large amount of data is transmitted or received. Keep this in mind when using a tariff with a traffic limit. In this case, you can set a data transfer limit.
Upon completion of the test, the connection will be terminated, and the test results will be displayed. For example:
The average internet connection speed obtained during the test will be displayed in the Bitrate field in Mbit/s. In our example, the internet channel bandwidth measurement was 188 Mbit/s on a 200 Mbit/s tariff.
Önemli
The measurement results are approximate and may not always be entirely accurate.
To measure your speed correctly during testing, disconnect your home devices from the network or reduce network activity to eliminate their impact on the results. During testing, turn off applications that use Internet traffic (torrent clients, VPN servers, etc.) on your router. For more accurate and reliable results, we recommend running the Internet speed test 2—3 times and comparing the results (you can also run the test with different public servers). Take into account the average result of the measurements. The speed results obtained during measurement are approximate and are usually lower (by approximately 5—6% for IPoE and up to 10% for PPPoE, L2TP, and PPTP) than the maximum Internet channel speed specified in your tariff plan (this is due to the amount of service information used during data transmission).
Test results may vary significantly depending on the load on the data transfer channels and provider gateways, iPerf servers, the time of day when the test is performed, the type of connection, and other factors.
Please note that the iPerf3 server can only accept connections from one client at a time. If the server is busy with another client, you will see the error server is busy running a test. try again later when you attempt to run the test. In this case, you need to wait for the server to become available and rerun the test after a short interval.