TTiperf: Difference between revisions
Content deleted Content added
Created page with "This page has information to those customers who have kindly offered to help in diagnosing the ongoing peak time slow throughput problems we've been seeing in February and Mar..." |
mNo edit summary |
||
| Line 2: | Line 2: | ||
==Summary== |
==Summary== |
||
On TalkTalk DSL circuits we've been seeing slow single thread TCP throughput in the evenings. |
On TalkTalk DSL circuits we've been seeing slow single thread TCP throughput in the evenings. ie, a VDSL circuit in sync at 79.9M can see < 10M throughput. Running multiple single thread downloads can fill the link as each will use around 10M |
||
Various things have been tried to narrow down what is causing this, but so far it still remains a mystery! |
Various things have been tried to narrow down what is causing this, but so far it still remains a mystery! |
||
| Line 13: | Line 13: | ||
To help with the investigations we've asked customers to run an iperf3 server and allow our IPs in |
To help with the investigations we've asked customers to run an iperf3 server and allow our IPs in |
||
===Installing iperf3:=== |
|||
iperf3 on linux systems should be available in your normal software repositries, eg: |
|||
debian: |
|||
sudo apt-get install iperf3 |
|||
redhat: |
|||
| ⚫ | |||
sudo yum install iperf3 |
|||
===Running iperf=== |
|||
simply running: |
|||
iperf3 -s |
|||
This will listen on the default port of 5201 |
|||
| ⚫ | |||
Allow these IPs to access your machine on TCP port 5201 |
|||
90.155.53.38 |
90.155.53.38 |
||
2001:8b0:0:53::38 |
2001:8b0:0:53::38 |
||