CODA-4582 - Open Issues for Investigation

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
I Plan to Stick Around
Posts: 52

Re: CODA-4582 - Open Issues for Investigation

When is .29 coming
Network Architect
Network Architect
Posts: 611

Re: CODA-4582 - Open Issues for Investigation


@dallasdinatake wrote:
When is .29 coming

Target date for Rogers to receive the code is currently mid June. Now I typically take a few days to slowly push it to a couple of trial participants at first to ensure that it does not contain major issues.

Resident Expert
Resident Expert
Posts: 6,061

Re: CODA-4582 - Open Issues for Investigation

Let me interpret the results as posted by @DeeNice:

 

[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 1.10 GBytes 945 Mbits/sec 0.198 ms 750666/783248 (96%)
[ 4] Sent 783248 datagrams

iperf Done.

 


I'm a Reliable Contributor
Posts: 607

Re: CODA-4582 - Open Issues for Investigation

Thanks for the update @RogersDave 

 

I am willing to test .29 as soon as you have it available.

 

@Datalink I have a feeling that D3.1 on upstream will really improve things overall including UDP, It's summer in 1 month, I wonder if they will start to deploy it in Ontario at least, god know we might only get it at the end of Summer in NB Smiley Tongue

Network Architect
Network Architect
Posts: 611

Re: CODA-4582 - Open Issues for Investigation


Datalink wrote: 

Thanks Datalink, sorry it's still early and I work too hard trying to make your Internet better Smiley Happy

I Plan to Stick Around
Posts: 10

Re: CODA-4582 - Open Issues for Investigation

@RogersDave @Datalink

 

Fair enough. Good observation, this is why i'm in Systems and not Networking... UDP packet loss is apparently that much harder to track than TCP. My concern is that anything that requires UDP is essentially useless in my house and there's no hard time to resolution. 

 

Moving on, if you can give me an exact command to run I can post results. Additionally, if you're looking for a guinea pig, I've got Windows and Linux VM's at home running 24/7 if you need a reporting agent installed somewhere. 

I Plan to Stick Around
Posts: 154

Re: CODA-4582 - Open Issues for Investigation

@DeeNice do you have a VPN that you can try to shuttle your UDP traffic over?

I Plan to Stick Around
Posts: 10

Re: CODA-4582 - Open Issues for Investigation

No VPN, That might work actually, but i'm not paying for a second account, it shouldn't be necessary to tunnel to another provider to have proper UDP traffic flowing. 

I Plan to Stick Around
Posts: 154

Re: CODA-4582 - Open Issues for Investigation


@DeeNice wrote:

No VPN, That might work actually, but i'm not paying for a second account, it shouldn't be necessary to tunnel to another provider to have proper UDP traffic flowing. 


Well, yeah, but it is what it is. If a $3/mo VPN fixes your problem, that's far cheaper than anything else that you could possibly do to fix it.

Highlighted
Resident Expert
Resident Expert
Posts: 6,061

Re: CODA-4582 - Open Issues for Investigation

After this mornings discussion I ran a few Iperf tests with Iperf 3.16, running with a direct connection to the modem with the modem in Bridge mode.  Rather interesting results to say the least, repeatable 50 Mb/s up  590 MB/s down.  So, it can be done, but there is more to running a high speed Iperf UDP test than meets the eye.  I had to use the iperf -w option to set the Socket Buffer Size and eventually pretty well maxed out the buffer size.  I stopped at 500Mb.  The limit is around 530Mb.  Without that Socket Buffer Size set, this test would be dead in the water. From what I can see, anyone wanting to run high speed receive UDP would have to employ a very fast processor and a router/firewall that is much more than your ordinary consumer firewall.  I think that concurrent traffic thru the router also has a lot to do with poor UDP performance that is normally observed.  It looks like the modem can do rather well with v2.0.10.27 loaded.  It might in fact be able to run faster downloads but with my processor, I hit 91% CPU utilization at 590 Mb/s.  This is on an Ivy Bridge-Extreme which is an Intel HexaCore Core i7-4930K, 3400 MHz on an Asus P9X79 Pro motherboard with 16 Gb ram. So, the 4930 is no slouch but I haven't overclocked the processor.  There are some notes on the github site regarding processor allocation, but I don't know if the windows version can do anything with that, possibly that only applies to the linux versions.  @DeeNice you were wondering about Gateway mode versus Bride mode.  My opinion at this point is that the modem can do much much better in Bridge mode than Gateway mode.  The requirement as I have indicated is a fast router/firewall.  Something like a Microtick 36 or 72 core, or possibly a pfsense built on a multi-core processor.  Just to note, on my ASUS RT-AC68U, I had to reduce the bandwidth to 500M to see both received and server bandwidth end up with the same numbers, so, with no other traffic through the router this does work, but, when you throw in gaming and Discord and twitch, that Iperf test result can go down to single or double digit data rates.

 

When you look at the results below, there are two sections ,the received data and the server transmitted data. Watching Iperf run, a couple of things will happen, Iperf either runs as expected, or, Iperf indicates a slower than expected receive value such as the following.  You can see the receive data rate at 300 Mb/s, while the server data rate is up at 500 Mb/s.   I don't know why it cycles from a good run to a bad run, but it does. No explanation at this point.

 

Received Bandwidth at ~300 Mb/s

 

[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 37.3 MBytes 313 Mbits/sec 0.007 ms 22879/61054 (37%)
[ 4] 1.00-2.00 sec 28.7 MBytes 241 Mbits/sec 0.006 ms 32012/61391 (52%)
[ 4] 2.00-3.00 sec 34.7 MBytes 291 Mbits/sec 0.006 ms 25254/60830 (42%)
[ 4] 3.00-4.00 sec 38.9 MBytes 326 Mbits/sec 0.008 ms 21195/61040 (35%)
[ 4] 4.00-5.00 sec 37.4 MBytes 313 Mbits/sec 0.008 ms 22811/61077 (37%)
[ 4] 5.00-6.00 sec 15.1 MBytes 127 Mbits/sec 0.040 ms 44941/60398 (74%)
[ 4] 6.00-7.00 sec 28.9 MBytes 242 Mbits/sec 0.007 ms 31902/61493 (52%)
[ 4] 7.00-8.00 sec 38.8 MBytes 325 Mbits/sec 0.007 ms 21660/61383 (35%)

Server Transmitted data:  Bandwidth at 500 Mb/s

 

[ ID] Interval Transfer Bandwidth Total Datagrams
[ 5] 0.00-1.00 sec 55.6 MBytes 466 Mbits/sec 56885
[ 5] 1.00-2.00 sec 60.0 MBytes 503 Mbits/sec 61408
[ 5] 2.00-3.00 sec 59.4 MBytes 498 Mbits/sec 60827
[ 5] 3.00-4.00 sec 59.6 MBytes 500 Mbits/sec 61023
[ 5] 4.00-5.00 sec 59.7 MBytes 501 Mbits/sec 61105
[ 5] 5.00-6.00 sec 59.6 MBytes 500 Mbits/sec 60985
[ 5] 6.00-7.00 sec 59.4 MBytes 499 Mbits/sec 60872

 

 

Here are the command lines with the results shown below:

 

Receive at 590 Mb/s.  Note the maxed out socket buffer size  -w 500M:

 

iperf3 -c iperf.he.net -p 5201 -u -l 1k -b 590000k -w 500M -t 30 -i 1 -R -f -k -V --get-server-output

 

Transmit:

 

iperf3 -c iperf.he.net -p 5201 -u -l 1k -b 50000k -w 20M -t 30 -i 1 -f -k -V --get-server-output

 

 

I think going beyond 590 Mb/s down will take some research.  At this point I don't know why UDP receive would be more demanding than a straight TCP speedtest which runs up to 950 Mb/s.   I know that a speedtest on this modem does not run as a clean test.  You can see that if you monitor the speedtest with Wireshark.  There are numerous errors scattered throughout the test.  Maybe Iperf does some amount of packet reconstruction, don't know? Is 590 Mb/s a modem limit with the 1k buffer length or is this a CPU limit or ethernet port limit?  Also don't have that answer.

 

 

Edit:  After additional testing today with the modem in Gateway mode, I've come to the conclusion that pure IPV4 UDP performance is an issue for the 4582.  For some reason that I don't know of yet, it looks like IPV4 NAT is doing a number on UDP performance.  I ended dropping down to 1 Mb/s on the receive side to get to a point where there were no errors.  I then kicked the modem into Dual Stack mode and ran Iperf, which ran in IPV6 mode on its own.  With IPV6, Iperf ran 40 Mb/s up without errors and 500 Mb/s down without errors.  I would guess that later tonight I'd see 50 Mb/s up without errors.  So, that leaves users in a conundrum when it comes to gaming and using the modem in Gateway mode.  If your game runs UDP on IPV4 only, then I would expect you to have problems.  If your game runs IPV6 then for the most part I would expect your gaming to be trouble free, given the no error data rates that I saw in testing.  This is probably most problematic for XBox One users running a peer to peer game versus one that goes thru a server, so, it might be a point to match the modem operating mode, IPV4, IPV6 or Dual stack to the specific XBox game that you are running.  Fwiw .....

 

 

 

Receive UDP test at 590 Mb/s:

 

C:\temp\iperf>iperf3 -c iperf.he.net -p 5201 -u -l 1k -b 590000k -w 500M -t 30 -i 1 -R -f -k -V --get-server-output
iperf 3.1.6
CYGWIN_NT-10.0 CC2 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64
Control connection MSS 0
warning: Warning: UDP block size 1024 exceeds TCP MSS 0, may result in fragmentation / drops
Time: Wed, 24 May 2017 14:25:57 GMT
Connecting to host iperf.he.net, port 5201
Reverse mode, remote host iperf.he.net is sending
Cookie: CC2.
[ 4] local 2607:xxxx:xxx:xx:xx:xxxx:xxxx:xxxx port 62903 connected to 2001:470:0:238::2 port 5201
Starting Test: protocol: UDP, 1 streams, 1024 byte blocks, omitting 0 seconds, 30 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 64.7 MBytes 542 Mbits/sec 0.055 ms 0/66229 (0%)
[ 4] 1.00-2.00 sec 69.5 MBytes 583 Mbits/sec 0.009 ms 0/71206 (0%)
[ 4] 2.00-3.00 sec 69.1 MBytes 580 Mbits/sec 0.008 ms 0/70759 (0%)
[ 4] 3.00-4.00 sec 68.6 MBytes 576 Mbits/sec 0.037 ms 0/70287 (0%)
[ 4] 4.00-5.00 sec 57.1 MBytes 479 Mbits/sec 0.009 ms 0/58478 (0%)
[ 4] 5.00-6.00 sec 69.9 MBytes 586 Mbits/sec 0.008 ms 0/71528 (0%)
[ 4] 6.00-7.00 sec 69.6 MBytes 584 Mbits/sec 0.006 ms 0/71269 (0%)
[ 4] 7.00-8.00 sec 69.6 MBytes 584 Mbits/sec 0.006 ms 0/71272 (0%)
[ 4] 8.00-9.00 sec 69.8 MBytes 585 Mbits/sec 0.171 ms 0/71424 (0%)
[ 4] 9.00-10.00 sec 63.2 MBytes 530 Mbits/sec 0.007 ms 0/64713 (0%)
[ 4] 10.00-11.00 sec 69.7 MBytes 585 Mbits/sec 0.009 ms 0/71417 (0%)
[ 4] 11.00-12.00 sec 69.7 MBytes 584 Mbits/sec 0.009 ms 0/71334 (0%)
[ 4] 12.00-13.00 sec 69.5 MBytes 583 Mbits/sec 0.009 ms 0/71210 (0%)
[ 4] 13.00-14.00 sec 68.5 MBytes 574 Mbits/sec 0.009 ms 0/70103 (0%)
[ 4] 14.00-15.00 sec 66.5 MBytes 557 Mbits/sec 0.009 ms 0/68052 (0%)
[ 4] 15.00-16.00 sec 69.8 MBytes 586 Mbits/sec 0.009 ms 0/71506 (0%)
[ 4] 16.00-17.00 sec 67.9 MBytes 570 Mbits/sec 0.150 ms 0/69550 (0%)
[ 4] 17.00-18.00 sec 69.1 MBytes 580 Mbits/sec 0.010 ms 0/70738 (0%)
[ 4] 18.00-19.00 sec 67.7 MBytes 568 Mbits/sec 0.009 ms 0/69372 (0%)
[ 4] 19.00-20.00 sec 64.8 MBytes 543 Mbits/sec 0.008 ms 0/66343 (0%)
[ 4] 20.00-21.00 sec 65.3 MBytes 548 Mbits/sec 0.009 ms 0/66837 (0%)
[ 4] 21.00-22.00 sec 65.1 MBytes 546 Mbits/sec 0.009 ms 0/66646 (0%)
[ 4] 22.00-23.00 sec 65.2 MBytes 547 Mbits/sec 0.010 ms 0/66811 (0%)
[ 4] 23.00-24.00 sec 69.0 MBytes 579 Mbits/sec 0.009 ms 0/70645 (0%)
[ 4] 24.00-25.00 sec 69.2 MBytes 580 Mbits/sec 0.009 ms 0/70842 (0%)
[ 4] 25.00-26.00 sec 69.3 MBytes 581 Mbits/sec 0.009 ms 0/70925 (0%)
[ 4] 26.00-27.00 sec 66.1 MBytes 554 Mbits/sec 0.009 ms 0/67647 (0%)
[ 4] 27.00-28.00 sec 68.1 MBytes 571 Mbits/sec 0.009 ms 0/69738 (0%)
[ 4] 28.00-29.00 sec 69.2 MBytes 580 Mbits/sec 0.010 ms 0/70816 (0%)
[ 4] 29.00-30.00 sec 65.4 MBytes 549 Mbits/sec 0.010 ms 0/66978 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-30.00 sec 2.07 GBytes 591 Mbits/sec 0.009 ms 0/2080428 (0%)
[ 4] Sent 2080428 datagrams
CPU Utilization: local/receiver 91.4% (32.6%u/58.8%s), remote/sender 32.7% (7.4%u/25.3%s)

Server output:
iperf 3.0.7
-----------------------------------------------------------
Time: Wed, 24 May 2017 14:25:55 GMT
Accepted connection from 2607:xxxx:xxx:xx:xx:xxxx:xxxx:xxxx, port 60915
Cookie: CC2.
[ 5] local 2001:470:0:238::2 port 5201 connected to 2607:xxxx:xxx:xx:xx:xxxx:xxxx:xxxx port 62903
Starting Test: protocol: UDP, 1 streams, 1024 byte blocks, omitting 0 seconds, 30 second test
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 5] 0.00-1.00 sec 66.2 MBytes 556 Mbits/sec 67827
[ 5] 1.00-2.00 sec 70.5 MBytes 592 Mbits/sec 72208
[ 5] 2.00-3.00 sec 70.0 MBytes 588 Mbits/sec 71722
[ 5] 3.00-4.00 sec 70.4 MBytes 590 Mbits/sec 72050
[ 5] 4.00-5.00 sec 70.6 MBytes 592 Mbits/sec 72274
[ 5] 5.00-6.00 sec 70.1 MBytes 588 Mbits/sec 71746
[ 5] 6.00-7.00 sec 70.4 MBytes 590 Mbits/sec 72065
[ 5] 7.00-8.00 sec 70.6 MBytes 593 Mbits/sec 72333
[ 5] 8.00-9.00 sec 70.0 MBytes 587 Mbits/sec 71659
[ 5] 9.00-10.00 sec 70.4 MBytes 591 Mbits/sec 72106
[ 5] 10.00-11.00 sec 70.6 MBytes 592 Mbits/sec 72268
[ 5] 11.00-12.00 sec 70.0 MBytes 587 Mbits/sec 71644
[ 5] 12.00-13.00 sec 70.4 MBytes 591 Mbits/sec 72115
[ 5] 13.00-14.00 sec 70.4 MBytes 591 Mbits/sec 72085
[ 5] 14.00-15.00 sec 70.0 MBytes 588 Mbits/sec 71719
[ 5] 15.00-16.00 sec 70.5 MBytes 591 Mbits/sec 72151
[ 5] 16.00-17.00 sec 70.5 MBytes 591 Mbits/sec 72190
[ 5] 17.00-18.00 sec 70.1 MBytes 588 Mbits/sec 71766
[ 5] 18.00-19.00 sec 70.4 MBytes 591 Mbits/sec 72086
[ 5] 19.00-20.00 sec 70.6 MBytes 592 Mbits/sec 72259
[ 5] 20.00-21.00 sec 70.1 MBytes 588 Mbits/sec 71763
[ 5] 21.00-22.00 sec 70.4 MBytes 590 Mbits/sec 72063
[ 5] 22.00-23.00 sec 70.6 MBytes 592 Mbits/sec 72272
[ 5] 23.00-24.00 sec 70.0 MBytes 587 Mbits/sec 71708
[ 5] 24.00-25.00 sec 70.4 MBytes 590 Mbits/sec 72079
[ 5] 25.00-26.00 sec 70.5 MBytes 592 Mbits/sec 72223
[ 5] 26.00-27.00 sec 70.1 MBytes 588 Mbits/sec 71781
[ 5] 27.00-28.00 sec 70.3 MBytes 590 Mbits/sec 72019
[ 5] 28.00-29.00 sec 70.6 MBytes 592 Mbits/sec 72268
[ 5] 29.00-30.00 sec 70.1 MBytes 588 Mbits/sec 71771


iperf Done.

 

 

Transmit test at 50 Mb/s:

 

C:\temp\iperf>iperf3 -c iperf.he.net -p 5201 -u -l 1k -b 50000k -w 20M -t 30 -i 1 -f -k -V --get-server-output
iperf 3.1.6
CYGWIN_NT-10.0 CC2 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64
Control connection MSS 0
warning: Warning: UDP block size 1024 exceeds TCP MSS 0, may result in fragmentation / drops
Time: Wed, 24 May 2017 13:51:50 GMT
Connecting to host iperf.he.net, port 5201
Cookie: CC2.
[ 4] local 2607:xxxx:xxx:xx:xx:xxxx:xxxx:xxxx port 52214 connected to 2001:470:0:238::2 port 5201
Starting Test: protocol: UDP, 1 streams, 1024 byte blocks, omitting 0 seconds, 30 second test
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.01 sec 5.56 MBytes 46.4 Mbits/sec 5693
[ 4] 1.01-2.01 sec 5.96 MBytes 50.0 Mbits/sec 6103
[ 4] 2.01-3.01 sec 5.95 MBytes 49.9 Mbits/sec 6096
[ 4] 3.01-4.01 sec 5.95 MBytes 49.9 Mbits/sec 6097
[ 4] 4.01-5.01 sec 5.96 MBytes 50.0 Mbits/sec 6100
[ 4] 5.01-6.01 sec 5.98 MBytes 50.2 Mbits/sec 6124
[ 4] 6.01-7.01 sec 5.95 MBytes 49.9 Mbits/sec 6089
[ 4] 7.01-8.01 sec 5.98 MBytes 50.1 Mbits/sec 6119
[ 4] 8.01-9.01 sec 5.95 MBytes 49.9 Mbits/sec 6088
[ 4] 9.01-10.01 sec 5.98 MBytes 50.1 Mbits/sec 6119
[ 4] 10.01-11.01 sec 5.94 MBytes 49.9 Mbits/sec 6087
[ 4] 11.01-12.01 sec 5.96 MBytes 50.0 Mbits/sec 6104
[ 4] 12.01-13.01 sec 5.96 MBytes 50.0 Mbits/sec 6107
[ 4] 13.01-14.01 sec 5.96 MBytes 50.0 Mbits/sec 6104
[ 4] 14.01-15.01 sec 5.96 MBytes 50.0 Mbits/sec 6105
[ 4] 15.01-16.01 sec 5.96 MBytes 50.0 Mbits/sec 6100
[ 4] 16.01-17.01 sec 5.97 MBytes 50.1 Mbits/sec 6112
[ 4] 17.01-18.01 sec 5.95 MBytes 49.9 Mbits/sec 6096
[ 4] 18.01-19.01 sec 5.97 MBytes 50.1 Mbits/sec 6116
[ 4] 19.01-20.01 sec 5.95 MBytes 49.9 Mbits/sec 6092
[ 4] 20.01-21.01 sec 5.96 MBytes 50.0 Mbits/sec 6106
[ 4] 21.01-22.01 sec 5.96 MBytes 50.0 Mbits/sec 6104
[ 4] 22.01-23.01 sec 5.97 MBytes 50.1 Mbits/sec 6115
[ 4] 23.01-24.01 sec 5.96 MBytes 50.0 Mbits/sec 6099
[ 4] 24.01-25.01 sec 5.96 MBytes 50.0 Mbits/sec 6098
[ 4] 25.01-26.01 sec 5.96 MBytes 50.0 Mbits/sec 6105
[ 4] 26.01-27.01 sec 5.96 MBytes 50.0 Mbits/sec 6103
[ 4] 27.01-28.01 sec 5.96 MBytes 50.0 Mbits/sec 6101
[ 4] 28.01-29.01 sec 5.96 MBytes 50.0 Mbits/sec 6106
[ 4] 29.01-30.01 sec 5.96 MBytes 50.0 Mbits/sec 6103
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-30.01 sec 178 MBytes 49.9 Mbits/sec 0.159 ms 0/182501 (0%)
[ 4] Sent 182501 datagrams
CPU Utilization: local/sender 9.3% (2.6%u/6.7%s), remote/receiver 5.1% (1.2%u/3.9%s)

Server output:
iperf 3.0.7
-----------------------------------------------------------
Time: Wed, 24 May 2017 13:51:48 GMT
Accepted connection from 2607:xxxx:xxx:xx:xx:xxxx:xxxx:xxxx, port 60848
Cookie: CC2.
[ 5] local 2001:470:0:238::2 port 5201 connected to 2607:xxxx:xxx:xx:xx:xxxx:xxxx:xxxx port 52214
Starting Test: protocol: UDP, 1 streams, 1024 byte blocks, omitting 0 seconds, 30 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 5] 0.00-1.00 sec 4.69 MBytes 39.4 Mbits/sec 0.152 ms 0/4806 (0%)
[ 5] 1.00-2.00 sec 6.00 MBytes 50.3 Mbits/sec 0.131 ms 0/6139 (0%)
[ 5] 2.00-3.00 sec 5.94 MBytes 49.8 Mbits/sec 0.140 ms 0/6080 (0%)
[ 5] 3.00-4.00 sec 5.99 MBytes 50.3 Mbits/sec 0.126 ms 0/6138 (0%)
[ 5] 4.00-5.00 sec 5.94 MBytes 49.8 Mbits/sec 0.142 ms 0/6079 (0%)
[ 5] 5.00-6.00 sec 6.03 MBytes 50.6 Mbits/sec 0.118 ms 0/6171 (0%)
[ 5] 6.00-7.00 sec 5.90 MBytes 49.5 Mbits/sec 0.112 ms 0/6044 (0%)
[ 5] 7.00-8.00 sec 5.96 MBytes 50.0 Mbits/sec 0.139 ms 0/6104 (0%)
[ 5] 8.00-9.00 sec 5.96 MBytes 50.0 Mbits/sec 0.128 ms 0/6107 (0%)
[ 5] 9.00-10.00 sec 5.98 MBytes 50.2 Mbits/sec 0.125 ms 0/6128 (0%)
[ 5] 10.00-11.00 sec 6.00 MBytes 50.3 Mbits/sec 0.188 ms 0/6146 (0%)
[ 5] 11.00-12.00 sec 5.89 MBytes 49.4 Mbits/sec 0.168 ms 0/6033 (0%)
[ 5] 12.00-13.00 sec 5.96 MBytes 50.0 Mbits/sec 0.120 ms 0/6102 (0%)
[ 5] 13.00-14.00 sec 5.92 MBytes 49.6 Mbits/sec 0.149 ms 0/6057 (0%)
[ 5] 14.00-15.00 sec 6.05 MBytes 50.7 Mbits/sec 0.159 ms 0/6194 (0%)
[ 5] 15.00-16.00 sec 5.91 MBytes 49.5 Mbits/sec 0.115 ms 0/6047 (0%)
[ 5] 16.00-17.00 sec 5.95 MBytes 49.9 Mbits/sec 0.126 ms 0/6091 (0%)
[ 5] 17.00-18.00 sec 5.97 MBytes 50.1 Mbits/sec 0.126 ms 0/6113 (0%)
[ 5] 18.00-19.00 sec 5.98 MBytes 50.1 Mbits/sec 0.128 ms 0/6119 (0%)
[ 5] 19.00-20.00 sec 5.94 MBytes 49.8 Mbits/sec 0.126 ms 0/6083 (0%)
[ 5] 20.00-21.00 sec 5.92 MBytes 49.7 Mbits/sec 0.123 ms 0/6063 (0%)
[ 5] 21.00-22.00 sec 6.01 MBytes 50.4 Mbits/sec 0.130 ms 0/6154 (0%)
[ 5] 22.00-23.00 sec 5.98 MBytes 50.2 Mbits/sec 0.122 ms 0/6122 (0%)
[ 5] 23.00-24.00 sec 5.97 MBytes 50.1 Mbits/sec 0.151 ms 0/6115 (0%)
[ 5] 24.00-25.00 sec 5.89 MBytes 49.4 Mbits/sec 0.123 ms 0/6035 (0%)
[ 5] 25.00-26.00 sec 5.98 MBytes 50.1 Mbits/sec 0.131 ms 0/6119 (0%)
[ 5] 26.00-27.00 sec 5.98 MBytes 50.1 Mbits/sec 0.126 ms 0/6120 (0%)
[ 5] 27.00-28.00 sec 5.93 MBytes 49.7 Mbits/sec 0.129 ms 0/6069 (0%)
[ 5] 28.00-29.00 sec 5.99 MBytes 50.3 Mbits/sec 0.116 ms 0/6136 (0%)
[ 5] 29.00-30.00 sec 5.99 MBytes 50.3 Mbits/sec 0.124 ms 0/6138 (0%)


iperf Done.