Netduma Limiting UDP traffic ?

[adel75]

EDIT: it looks like it is a bug in iperf3 with some queuing mechanism. iperf2 doesn't show these packet losses.

 

 

Hi,

 

i am doing some testing on an R1 perf wise.

 

- R1 is plugged to a ERX.

- i'm behind a 1Gbit/s FTTH.

- NO CONGESTION CONTROL ans TURBO AND SUPERTURBO Configured.

 

when behind R1 testing at 12Mbps UDP:

 

@home:~$ iperf3 -c ping.online.net -u -b 12000000 -p 5202 

Connecting to host ping.online.net, port 5202

[  4] local 192.168.118.200 port 51312 connected to 62.210.18.40 port 5202

[ ID] Interval           Transfer     Bandwidth       Total Datagrams

..

.. 

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams

[  4]   0.00-10.00  sec  14.2 MBytes  11.9 Mbits/sec  1.140 ms  0/1813 (0%) 

 

when behind R1 testing at 15Mbps UDP, there is UDP packet loss:

 

@home:~$ iperf3 -c ping.online.net -u -b 15000000 -p 5202 

Connecting to host ping.online.net, port 5202

[  4] local 192.168.118.200 port 59820 connected to 62.210.18.40 port 5202

[ ID] Interval           Transfer     Bandwidth       Total Datagrams

...

...

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams

[  4]   0.00-10.00  sec  17.7 MBytes  14.9 Mbits/sec  1.092 ms  185/2265 (8.2%)  

[  4] Sent 2265 datagrams

 

 

 

when behind ERX directly and even at 30Mbps UDP, there is NO UDP packet loss:

 

iperf3 -c ping.online.net -u -b 30000000 -p 5202

Connecting to host ping.online.net, port 5202

[  6] local 192.168.1.101 port 56094 connected to 62.210.18.40 port 5202

[ ID] Interval           Transfer     Bandwidth       Total Datagrams

[  6]   0.00-1.01   sec  3.23 MBytes  27.0 Mbits/sec  414  

[  6]   1.01-2.01   sec  3.58 MBytes  30.0 Mbits/sec  458  

[  6]   2.01-3.01   sec  3.59 MBytes  30.1 Mbits/sec  459  

[  6]   3.01-4.01   sec  3.57 MBytes  30.0 Mbits/sec  457  

[  6]   4.01-5.00   sec  3.59 MBytes  30.2 Mbits/sec  459  

[  6]   5.00-6.00   sec  3.57 MBytes  29.9 Mbits/sec  457  

[  6]   6.00-7.00   sec  3.59 MBytes  30.1 Mbits/sec  459  

[  6]   7.00-8.01   sec  3.57 MBytes  29.8 Mbits/sec  457  

[  6]   8.01-9.00   sec  3.59 MBytes  30.1 Mbits/sec  459  

[  6]   9.00-10.01  sec  3.57 MBytes  29.9 Mbits/sec  457  

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams

[  6]   0.00-10.01  sec  35.4 MBytes  29.7 Mbits/sec  0.758 ms  0/4535 (0%)

 

 

UDP is very important for gaming traffic and  if there is a 13/14mbps on UDP limitation on R1 then it can explain some weird issues..

 

So question :

 

 

can people download iperf3 :

 

https://iperf.fr/iperf-download.php

 

and run this test :

 

- deactivate any Congestion Control and enable turbo and superturbo mode .

 

10Mbps test :   iperf3 -c ping.online.net -u -b 10000000 -p 5202

 

20Mbps test :   iperf3 -c ping.online.net -u -b 20000000 -p 5202

 

and then do the same directly behind their ISP router.

 

this would confirm/infirm that there is something with R1 regarding UDP.

[Netduma Fraser]

I don't know of any limitation and with congestion control off it's not trying to manage anything. Repeating the test do you get packet loss every time? 

[PharmDawgg]

Just an FYI: But I see that the R1 was connected to an ERX. I would check their forums because I believe there may be issues with them dropping UDP packets in particular.  

[adel75]

Just an FYI: But I see that the R1 was connected to an ERX. I would check their forums because I believe there may be issues with them dropping UDP packets in particular.  

that's for the ERL (Edge Router Lite) not the ERX.

[adel75]

I don't know of any limitation and with congestion control off it's not trying to manage anything. Repeating the test do you get packet loss every time? 

 

yes. that's fully reproductible. every time. with the commands i provided.

[adel75]

it looks like it is a bug in iperf3 with some queuing mechanism. iperf2 doesn't show these packet losses.

[Netduma Fraser]

it looks like it is a bug in iperf3 with some queuing mechanism. iperf2 doesn't show these packet losses.

 

Great to know, thanks for the update!