Merci.

J’ai négligé d’installer la version 3 disponible en package sur le site 
iperf.fr et fait confiance aux repositories officiels dont elle est absente. La 
présence de la version 2 par défaut dans Debian est-elle du à une divergence de 
vues avec les développeurs ? 

Après quelques tests vers des destinations extra-européennes j’aimerai les 
commentaires de ceux qui ont l’habitude de l'outil. Tous les tests ont été 
effectués depuis une interface Fast Ethernet.



 1 - vis-à-vis du Kazakhstan (iperf.it-north.net)



 1.1 en upload depuis la machine locale, TCP parvient à saturer l'interface


iperf3 -fm -c iperf.it-north.net -p 5201
Connecting to host iperf.it-north.net, port 5201
[  4] local 192.168.1.252 port 51830 connected to 82.200.209.194 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  3.52 MBytes  29.5 Mbits/sec    0    905 KBytes       
[  4]   1.00-2.00   sec  11.6 MBytes  97.0 Mbits/sec    0   1.52 MBytes       
[  4]   2.00-3.00   sec  11.2 MBytes  94.2 Mbits/sec    0   1.52 MBytes       
[  4]   3.00-4.00   sec  11.2 MBytes  94.3 Mbits/sec    0   1.52 MBytes       
[  4]   4.00-5.00   sec  11.2 MBytes  94.3 Mbits/sec    0   1.52 MBytes       
[  4]   5.00-6.00   sec  11.2 MBytes  93.9 Mbits/sec    0   1.52 MBytes       
[  4]   6.00-7.00   sec  11.2 MBytes  94.3 Mbits/sec    0   1.52 MBytes       
[  4]   7.00-8.00   sec  11.2 MBytes  93.8 Mbits/sec    0   1.52 MBytes       
[  4]   8.00-9.00   sec  11.2 MBytes  94.4 Mbits/sec    2   1.52 MBytes       
[  4]   9.00-10.00  sec  11.2 MBytes  94.4 Mbits/sec    0   1.52 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   105 MBytes  88.0 Mbits/sec    2             sender
[  4]   0.00-10.00  sec   102 MBytes  85.9 Mbits/sec                  receiver

iperf Done.



 1.2 en download, TCP est cappé à 2Mbits !


iperf3 -fm -R -c iperf.it-north.net -p 5201
Connecting to host iperf.it-north.net, port 5201
Reverse mode, remote host iperf.it-north.net is sending
[  4] local 192.168.1.252 port 51826 connected to 82.200.209.194 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   249 KBytes  2.04 Mbits/sec                  
[  4]   1.00-2.00   sec   277 KBytes  2.27 Mbits/sec                  
[  4]   2.00-3.00   sec   277 KBytes  2.27 Mbits/sec                  
[  4]   3.00-4.00   sec   286 KBytes  2.34 Mbits/sec                  
[  4]   4.00-5.00   sec   283 KBytes  2.32 Mbits/sec                  
[  4]   5.00-6.00   sec   274 KBytes  2.25 Mbits/sec                  
[  4]   6.00-7.00   sec   266 KBytes  2.18 Mbits/sec                  
[  4]   7.00-8.00   sec   286 KBytes  2.34 Mbits/sec                  
[  4]   8.00-9.00   sec   266 KBytes  2.18 Mbits/sec                  
[  4]   9.00-10.00  sec   280 KBytes  2.29 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  2.71 MBytes  2.28 Mbits/sec    0             sender
[  4]   0.00-10.00  sec  2.71 MBytes  2.28 Mbits/sec                  receiver

iperf Done.



L’aller et le retour empruntent-ils des routes différentes ? Notre ISP 
achète-t-il un transit asymétrique vers cette partie du monde ? Quels outils 
utiliser pour le vérifier ? Simple curiosité, c’est sans doute la première fois 
que je me connecte sur un serveur au Kazakhstan.




 2 - vis-à-vis des US (iperf.he.net)



 2.1 en download depuis Hurricane, TCP met du temps à saturer l’interface


iperf3 -fm -R -t 20 -c iperf.he.net -p 5201
Connecting to host iperf.he.net, port 5201
Reverse mode, remote host iperf.he.net is sending
[  4] local 192.168.1.252 port 50792 connected to 216.218.227.10 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   841 KBytes  6.89 Mbits/sec                  
[  4]   1.00-2.00   sec  3.33 MBytes  27.9 Mbits/sec                  
[  4]   2.00-3.00   sec  3.56 MBytes  29.9 Mbits/sec                  
[  4]   3.00-4.00   sec  3.55 MBytes  29.7 Mbits/sec                  
[  4]   4.00-5.00   sec  3.48 MBytes  29.2 Mbits/sec                  
[  4]   5.00-6.00   sec  3.53 MBytes  29.6 Mbits/sec                  
[  4]   6.00-7.00   sec  3.84 MBytes  32.2 Mbits/sec                  
[  4]   7.00-8.00   sec  4.26 MBytes  35.8 Mbits/sec                  
[  4]   8.00-9.00   sec  4.71 MBytes  39.5 Mbits/sec                  
[  4]   9.00-10.00  sec  5.31 MBytes  44.6 Mbits/sec                  
[  4]  10.00-11.00  sec  5.79 MBytes  48.6 Mbits/sec                  
[  4]  11.00-12.00  sec  6.60 MBytes  55.4 Mbits/sec                  
[  4]  12.00-13.00  sec  7.79 MBytes  65.4 Mbits/sec                  
[  4]  13.00-14.00  sec  9.10 MBytes  76.4 Mbits/sec                  
[  4]  14.00-15.00  sec  10.6 MBytes  89.2 Mbits/sec                  
[  4]  15.00-16.00  sec  9.16 MBytes  76.9 Mbits/sec                  
[  4]  16.00-17.00  sec  1.08 MBytes  9.03 Mbits/sec                  
[  4]  17.00-18.00  sec  2.88 MBytes  24.2 Mbits/sec                  
[  4]  18.00-19.00  sec  3.61 MBytes  30.3 Mbits/sec                  
[  4]  19.00-20.00  sec  4.93 MBytes  41.4 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-20.00  sec   105 MBytes  44.2 Mbits/sec  1268             sender
[  4]   0.00-20.00  sec  99.0 MBytes  41.5 Mbits/sec                  receiver

iperf Done.


Le résultat est probablement normal ?



 2.2 Impossible d’obtenir un résultat en download en utilisant UDP


iperf3 -fm -u -b 70M -R -c iperf.he.net -p 5201
Connecting to host iperf.he.net, port 5201
Reverse mode, remote host iperf.he.net is sending
[  4] local 192.168.1.252 port 38587 connected to 216.218.227.10 port 5201
iperf3: OUT OF ORDER - incoming packet = 3 and received packet = 0 AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 4 and received packet = 0 AND SP = 28
iperf3: OUT OF ORDER - incoming packet = 8 and received packet = 0 AND SP = 28
iperf3: OUT OF ORDER - incoming packet = 6 and received packet = 0 AND SP = 28
iperf3: OUT OF ORDER - incoming packet = 7 and received packet = 0 AND SP = 28



 2.3 en upload depuis la machine locale, j’ai du mal à croire les résultats


iperf3 -fm -c iperf.he.net -p 5201
Connecting to host iperf.he.net, port 5201
[  4] local 192.168.1.252 port 50746 connected to 216.218.227.10 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  4.12 MBytes  34.6 Mbits/sec    0    226 KBytes       
[  4]   1.00-2.00   sec  1.74 MBytes  14.6 Mbits/sec    7    256 KBytes       
[  4]   2.00-3.00   sec  1.24 MBytes  10.4 Mbits/sec   10    139 KBytes       
[  4]   3.00-4.00   sec   827 KBytes  6.78 Mbits/sec    1    110 KBytes       
[  4]   4.00-5.00   sec   509 KBytes  4.17 Mbits/sec    2   86.3 KBytes       
[  4]   5.00-6.00   sec   445 KBytes  3.65 Mbits/sec    1   69.3 KBytes       
[  4]   6.00-7.00   sec   382 KBytes  3.13 Mbits/sec    1   52.3 KBytes       
[  4]   7.00-8.00   sec   382 KBytes  3.13 Mbits/sec    1   62.2 KBytes       
[  4]   8.00-9.00   sec   318 KBytes  2.60 Mbits/sec    2   39.6 KBytes       
[  4]   9.00-10.00  sec   191 KBytes  1.56 Mbits/sec    1   32.5 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  10.1 MBytes  8.46 Mbits/sec   26             sender
[  4]   0.00-10.00  sec  6.14 MBytes  5.15 Mbits/sec                  receiver

iperf Done.


Une règle de shapping semble attaquer le traffic TCP pour le faire tomber à 
1Mbps. Pour quelle raison pourrait-elle être en place sur l'Atlantique ? Notre 
ISP n’aime pas iperf ?



 2.4 tandis que le même upload en UDP montre une autre réalité


iperf3 -fm -u -b 70M -c iperf.he.net -p 5201
Connecting to host iperf.he.net, port 5201
[  4] local 192.168.1.252 port 59511 connected to 216.218.227.10 port 5201
[ ID] Interval           Transfer     Bandwidth       Total Datagrams
[  4]   0.00-1.00   sec  7.94 MBytes  66.6 Mbits/sec  1016  
[  4]   1.00-2.00   sec  8.33 MBytes  69.9 Mbits/sec  1066  
[  4]   2.00-3.00   sec  8.65 MBytes  72.5 Mbits/sec  1107  
[  4]   3.00-4.00   sec  8.22 MBytes  68.9 Mbits/sec  1052  
[  4]   4.00-5.00   sec  8.24 MBytes  69.1 Mbits/sec  1055  
[  4]   5.00-6.00   sec  8.67 MBytes  72.7 Mbits/sec  1110  
[  4]   6.00-7.00   sec  7.55 MBytes  63.3 Mbits/sec  966  
[  4]   7.00-8.00   sec  9.06 MBytes  76.0 Mbits/sec  1160  
[  4]   8.00-9.00   sec  8.33 MBytes  69.9 Mbits/sec  1066  
[  4]   9.00-10.00  sec  7.91 MBytes  66.3 Mbits/sec  1012  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total 
Datagrams
[  4]   0.00-10.00  sec  82.9 MBytes  69.5 Mbits/sec  0.112 ms  81/10609 
(0.76%)  
[  4] Sent 10609 datagrams

iperf Done.




Merci pour vos commentaires et possible liens vers d’autres outils et documents 
d’intérêt sur le sujet.


--
Frédéric Dumas
f.du...@ellis.siteparc.fr





Le 19 août 2017 à 05:37, lilian coupat <lil...@abeille.com> a écrit :

> bonjour,
> 
> utilise iperf3
> 
> lilian
>       Lilian Coupat | Abeille Informatique
> 5 Avenue du Maréchal Leclerc - 63800 Cournon d'Auvergne
> 04 73 145 145 | lil...@abeille.com | www.abeille.com
> 
> 
>> Le 19 août 2017 à 01:48, Frederic Dumas <f.du...@ellis.siteparc.fr> a écrit :
>> 
>> iperf -fm -c ping.online.net -p 5206
> 



---------------------------
Liste de diffusion du FRnOG
http://www.frnog.org/

Répondre à