How to use Iperf to test the speed on TP-Link routers
Archer C5400 , Archer C4 , Archer C5 , Archer C2 , Archer AX95 , Archer C59 (EU) , Archer AX96 , Archer AX23 (EU) , Archer VR1200v , Archer GE550 , Archer BE850 , ER7206 , ER8411 , Archer C58HP , Archer C8 , Archer C9 , Archer C6 , Archer C7 , Archer MR400(APAC) , Archer C20 W , Archer AX90 , Archer C5400X , Archer AX5400 , Archer AX53 (RU) , ER707-M2 , Archer A1200 , TL-ER600VPN , Archer AX73 (EU) , Archer AX80 , Archer VR400 , ER7212PC , Archer AX4200 , Archer C3200 , Archer XR500v , Archer A2 , Archer AX75 , TL-ER6120G , Archer AX73 , Archer VR2100 , Archer VR2800v , Archer VR600v , Archer VR1210v , Archer VR600b , Archer A6 , Archer A7 , Archer AX72 , Archer A5 , Archer A8 , Archer A9 , Archer C20
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
Usually, people may want to use Speedtest® to measure the speed of the router when they encounter the problem that the device connected behind the router has a slower rate or that its speed is much slower than the ISP bandwidth.
But the result of Speedtest® may be affected by the ISP and network delay, so we recommend you use the iPerf tool to test. This tool is a little software, and it is convenient to operate. Besides, when using iPerf, the host can connect to the server directly, eliminating the effects of the ISP and network congestion, and it can measure the most accurate speed, reducing the network influence to the lowest.
Additionally, compared to Speedtest®, iPerf can conveniently conduct speed tests between two devices on the same local network as it allows for customizing the server.
Step 1 Install iPerf on computers
- Before having a test, you may need to install iPerf on both computers, and you can refer to the iPerf official website to download it: https://iperf.fr/iperf-download.php
- The latest version of iPerf is iPerf3, so we used in this FAQ is iPerf3. Please choose the right software version for your computer when downloading. For example, the operating system of the PC we used in this FAQ is Windows 11 64-bit, so we downloaded iPerf3-3.1.3-win64. After downloading, you will get a zip file. Extract the zip file, there will be two files: cygwin1.dll and iperf3.exe as the following figure shows.
Note: Using different versions of iPerf for server and client may result in unsuccessful speed tests. - Copy these two files to the path C:\Windows\System32, and then the installation is complete.
Let's take a LAN-to-LAN speed test, for example.
Step 2 Setup the iPerf Server and Client to measure the speed of the router (LAN to LAN)
When using iPerf to test the speed, we need to set one PC as a server and another PC as a client. In this FAQ we set PC A as the server and PC B as the client.
- On PC A, press Windows key + R; put cmd in the Open bar and click OK; in the CMD dialog box, input the command iperf3 -s and press enter to set PC A as a server.
- Perform the same operation on PC B to run CMD; in the CMD dialog box, input the command iperf3 -c 192.168.68.51, where the c means to set PC B as a client, and the IP address behind -c is the IP address of the server. After inputting this command, type the Enter key to start measuring the speed.
Note: You can use iperf3 -c 192.168.0.1 -P <parallel> -t <time> instead, where <parallel> is the number of parallel client streams to run (default 1), <time> is the time in seconds to transmit for (default 10 secs). Take the picture above as an example. Sometimes, having a too-low parallel setting can result in slower speeds. In such cases, it's advisable to increase the parallel setting appropriately.
Step 3 How to perform LAN-to-WAN and WAN-to-LAN speed test
Set up the topology as shown below:
- In the diagram above, PC A is connected to the WAN port of the router. PC B is connected to the LAN port of the router.
Note: Please disable the firewall on both computers before testing. The firewall may block test traffic. - Set the IP address of PC A to 192.168.0.1 and the subnet mask to 255.255.255.0.
Note: Due to PC B connecting to the Router directly, PC B need not configure the Static IP address manually, PC B will get the IP address from the Router automatically. If you disabled the DHCP Server function on the Router, please set the Static IP address for PC B also.
Note: Sometimes you may encounter a situation where the IP of PC B is 192.168.0.X. In this case, you should set the address of PC A to 192.168.1.1 with a mask of 255.255.255.0. (Just make sure A and B are not in the same IP address range.) - Set the static IP address for the WAN port of the Router as 192.168.0.2 with the mask of 255.255.255.0. Go to the web interface of the Router first. Configure the static IP address for the WAN port of Router, as shown in the figure:
- Once the IP address configuration is completed, the next step is to run the iPerf3 speed test. Similar to Step 2, first run iperf3 -s on the Server (PC A); then on the Client (PC B), run:
- iperf3 -c 192.168.0.1 to test LAN-to-WAN speed, which represents the upload speed in our daily lives.
- iperf3 -c 192.168.0.1 -R to test WAN-to-LAN speed, which represents download speed, where -R indicates traffic in a reverse direction.
Note: You can also add -P <parallel> -t <time> after the above commands, leaving a space between each.
Looking for More
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or