TTiperf: Difference between revisions
m (→iperf) |
mNo edit summary |
||
Line 5: | Line 5: | ||
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! |
||
These tests are being headed up by Andrew, you can find me in IRC. |
|||
==Status post== |
==Status post== |
||
Line 10: | Line 12: | ||
*https://aastatus.net/2358 |
*https://aastatus.net/2358 |
||
==iperf== |
==Running iperf== |
||
To help with the investigations we've asked customers to run an iperf3 server and allow our IPs in. We'd ask that you keep the iperf server running all the time throughout the duration as then staff can run tests without having to bother you! |
To help with the investigations we've asked customers to run an iperf3 server and allow our IPs in. We'd ask that you keep the iperf server running all the time throughout the duration as then staff can run tests without having to bother you! |
||
Line 21: | Line 23: | ||
sudo yum install iperf3 |
sudo yum install iperf3 |
||
You can read about iperf in the manual (man iperf3) or at https://iperf.fr/ |
|||
⚫ | |||
⚫ | |||
simply running: |
simply running: |
||
iperf3 -s |
iperf3 -s |
||
This will listen on the default port of 5201 |
This will listen on the default port of 5201. It will run on the console, so may be best run in a screen session or as a background daemon (-d option) |
||
===IPs to allow:=== |
===IPs to allow:=== |
Revision as of 09:00, 10 March 2017
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 March 2017.
Summary
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!
These tests are being headed up by Andrew, you can find me in IRC.
Status post
The status post should be update daily with information:
Running iperf
To help with the investigations we've asked customers to run an iperf3 server and allow our IPs in. We'd ask that you keep the iperf server running all the time throughout the duration as then staff can run tests without having to bother you!
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
You can read about iperf in the manual (man iperf3) or at https://iperf.fr/
starting iperf
simply running:
iperf3 -s
This will listen on the default port of 5201. It will run on the console, so may be best run in a screen session or as a background daemon (-d option)
IPs to allow:
Allow these IPs to access your machine on TCP port 5201
90.155.53.38 2001:8b0:0:53::38 90.155.23.30 2001:8b0:0:23::30 81.187.30.90 2001:8b0:0:30::90
Let us know
Once your side is set up, please email support@aa.net.uk with a subject of "iperf" and the IPv4 or IPv6 address of your iperf server.