New Contributor III
•
17 Messages
Severe packet loss (Upload) to amazon web services (Fortnite) - UPDATE 1/9
UPDATE - I suspect this packet loss issue may be fixed very soon. Maybe within the next week. That's all I'll say for now - I'll update again soon
Yep, another AWS packet loss post. Have none of the past customers with this issue had their problems actually resolved?
I'm consistently getting 0-10% packet loss to Amazon web services (both west and east servers) making fortnite unplayable. No, I do not have this problem with other games I play as they do not use Amazon web services to host their servers. This seems to be an issue with the path cox routing takes to AWS servers.
my cox tracert to AWS west (oregon): https://textuploader.com/dzw7o
my cox tracert to AWS west (52.42.109.244) :https://textuploader.com/dzw7g
my cox tracert to AWS east: https://textuploader.com/dzw70
my tethered AT&T iphone to AWS west: https://textuploader.com/dzw76 - interesting how AT&T LTE is a legitimately better connection to AWS than vegas's "best" ISP
No I'm not using a puma 6 modem. I have the cisco DPQ3212.
puma 6 test anyway: https://imgur.com/a/iKR9PYY
I've already troubleshot by hardwiring to modem directly with the same results. I've unplugged the power on router and modem (although it stays on) numerous times, as well as coax.
Here's a tracert of another cox customer with the same exact problems: https://pastebin.com/index/ehaQBYEd
and another: https://pastebin.com/Qqfxa5UN (there are many more tracerts exactly like these; it also seems like we're all dropping packets at the exact same servers)
now here's a tracert of a cox customer in phoenix (to AWS west) who has 0% packet loss: https://pastebin.com/MX1GfGPC
A reddit thread furthering the evidence that this is explicitly a cox issue and not a personal one: www.reddit.com/.../
I would appreciate real effort in getting this resolved - I know I'm going to be told this is a personal issue when it obviously simply is not. Thanks in advance
Related Content
Closed
1
0
Closed
2
0
Closed
8
Accepted Solution
Closed
15
0
Closed
1
0
pd91
New Contributor III
•
17 Messages
I've gotten in touch with an employee at Epic Games with access to fortnite servers and he was kind enough to run a traceroute to my IP address.
"This is from a NAW FNBR server that's located in northern California. All the traceroutes I ran stopped at that last gateway and then timed out after that.
Hope this helps - I can say with some certainty that the issue is on Cox's end, not ours." - https://pastebin.com/rM03cvBq (removed my personal IP)
Finally, my reddit thread showing quite a few more people with the exact same issue - www.reddit.com/.../
0
Becky
Moderator
•
4.3K Messages
5
0
BooPacketLoss
New Contributor III
•
34 Messages
Yes, this is real, yes I just contacted Cox about it for the thousandth time. Packet loss to Amazon Web Services servers is just absolutely brutal for me in the Phoenix area. I forwarded your Reddit post to them and sent my own PingPlotter tracert of the packet loss, there had better be some serious steps taken by COX soon.
1
Packet_Loss_Ass
New Contributor
•
1 Message
Funny, I'm here for the exact same issue that I've been researching for over a month now and it's odd I stumble across the same reddit post that I commented in.
I had a Cox tech come out last week. He 'reset' everything in my house and when he was done he said he fixed my issue. He handed me a small metal device that he called a packet capture and said it was used to provision data for uplink. I bought it for about a day and a half since it seemed to fix my issue. Before he left I verified my uplink had 4 locked channels instead of 1 and I played a few games of Fortnite throughout the day with almost 0 packet loss. It was glorious! There was 1-2 instances where I saw packet loss go to 2% but only for a second or 2. Next day, internet went out, I cycled the modem and the packet loss was back with a vengeance.
Pretty safe to say the tech gave me some nonsense and went about his day. If there were another ISP alternative in my area I'd have already switched but Cox is just short of a monopoly in my area and apparently that entitles them to sell a 'premium' service built on a sub-par infrastructure.
I'd post my tracert output as well but it's nearly identical to what's already linked above.
1
megamatt0
New Contributor
•
2 Messages
Hello, I have been having the same exact issue at my home for the past 2 months as well. Southeast Arizona area. It has been very frustrating and I do not want to switch to CenturyLink as they only offer 40Mbps. I had a tech come out earlier this week and he said my speeds and signal levels are fine. I hope this can get figured out very soon.
0
BooPacketLoss
New Contributor III
•
34 Messages
Keeping all of these threads at the top for anyone thinking of dropping COX as an isp. You would be justified.
0
jasl
New Contributor II
•
14 Messages
Having the exact same issue. West side of Phoenix. Had two techs out and they were still unable to resolve the issue. Their solution is to check the signal to my home and ping the cox.net servers. Fortnite and Rocket League are unplayable and it's so *** frustrating.
0
gjett1
New Contributor III
•
11 Messages
Same Problem. Cox fix this!
BUMP.
0
BrianM
Moderator
•
868 Messages
If anyone is still having trouble, please provide a current trace route in this thread and we will forward to our network operations team for further review. Thanks!
Brian
Cox Support Forum Moderator
11
jrdn
New Contributor II
•
16 Messages
Came across this post. I created a similar issue regarding fortnite & packet loss. Also, other users are seeing this same thing:
https://www.epicgames.com/fortnite/forums/bug-reports/battle-royale-aa/681327-fortnite-packet-loss-and-ping-lag-spikes-as-of-recently-9-04-2018
This is exceptionally frustrating to me that Cox doesn't look into this and forces users to do this. It's as if they want to do service calls on purpose to make $75 for a visit when it's CLEAR that SO MANY other people are having this same issue with COX services only. My brother & friends are a half mile away from me on Spectrum playing on the same game without packet loss while I'm experiencing 30-40%. Other users of Netflix are complaining about packet loss as well, so something might be wrong with EC2 West coast routing. IMO, my blame wants to be with Cox. I'm ditching Cox the minute another provider can provide me with Gigabyte speeds.
2
0
jrdn
New Contributor II
•
16 Messages
brianm Here are 3 trace routes for various locations:
1. tracert 52.42.109.244
Tracing route to ec2-52-42-109-244.us-west-2.compute.amazonaws.com [52.42.109.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 5 ms 7 ms 10.162.0.1
3 7 ms 8 ms 7 ms 68.6.14.76
4 7 ms 7 ms 8 ms 100.120.108.6
5 13 ms 12 ms 13 ms 68.1.1.167
6 11 ms 11 ms 12 ms ip70-167-151-90.at.at.cox.net [70.167.151.90]
7 14 ms 31 ms 21 ms 54.239.102.20
8 12 ms 11 ms 12 ms 54.239.102.27
9 37 ms 45 ms 37 ms 54.239.42.120
10 * * * Request timed out.
11 61 ms 72 ms 47 ms 52.93.12.124
12 36 ms 36 ms 35 ms 52.93.12.111
13 39 ms 37 ms 39 ms 52.93.12.182
14 38 ms 36 ms 36 ms 52.93.12.209
15 61 ms 37 ms 38 ms 52.93.15.217
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
2. tracert 52.15.247.160
Tracing route to ec2-52-15-247-160.us-east-2.compute.amazonaws.com [52.15.247.160]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 6 ms 7 ms 10.162.0.1
3 6 ms 8 ms 9 ms 68.6.14.78
4 7 ms 8 ms 8 ms 100.120.108.8
5 37 ms 37 ms 36 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
6 38 ms 40 ms 39 ms 72.21.221.204
7 93 ms 88 ms 103 ms 176.32.125.200
8 79 ms 89 ms 77 ms 176.32.125.243
9 * * * Request timed out.
10 76 ms 81 ms 79 ms 178.236.3.187
11 77 ms 79 ms 98 ms 52.93.128.186
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 83 ms 86 ms 85 ms 52.95.1.150
16 76 ms 76 ms 77 ms 52.95.1.161
17 82 ms 83 ms 79 ms 52.95.1.244
18 77 ms 78 ms 77 ms 52.95.1.225
19 77 ms 77 ms 76 ms 52.95.3.138
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
3. tracert ec2-54-70-204-128.us-west-2.compute.amazonaws.com
Tracing route to ec2-54-70-204-128.us-west-2.compute.amazonaws.com [54.70.204.128]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 10.162.0.1
3 8 ms 7 ms 13 ms 68.6.14.76
4 7 ms 7 ms 21 ms 100.120.108.6
5 12 ms 12 ms 11 ms 68.1.1.167
6 12 ms 11 ms 13 ms ip70-167-151-90.at.at.cox.net [70.167.151.90]
7 * 43 ms 29 ms 54.239.102.56
8 12 ms 10 ms 12 ms 54.239.102.63
9 36 ms 37 ms 36 ms 54.239.42.120
10 * * * Request timed out.
11 54 ms 54 ms 54 ms 52.93.12.88
12 35 ms 38 ms 41 ms 52.93.12.75
13 38 ms 48 ms 39 ms 52.93.12.182
14 56 ms 53 ms * 52.93.12.203
15 37 ms 35 ms 39 ms 52.93.240.51
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
22
0
Morten
New Contributor
•
1 Message
One more user here with most likely the same faulty router (what else could possibly be the problem? (sc)). While every other server works fine, Fortnite connection shows a beautiful, up to 70+% packet loss on the upload side.
6
0
SufferingFromPa
New Contributor II
•
3 Messages
Same problem here. Constant packet loss. If I switch my ISP to Verizon through tethering I get 0% packet loss! How is that AWS's problem? Many other ISP's have 0% packet loss to AWS!
https://www.youtube.com/watch?v=l8B3URQu8EI
1-6 % packet loss is on a GOOD day!
0
SpectreRT
New Contributor
•
5 Messages
Just created a reply on this, I'm also getting significant packet loss with gaming and accessing AWS / Azure services. It's been bouncing between 6 - 12% loss on upstream today.
Is Cox really not going to help with this?
1
0
SufferingFromPa
New Contributor II
•
3 Messages
The only two games I play online, Fortnite and Player Unknown's Battlegrounds have constant packet loss. They both use AWS as far as I know. Not sure who is at fault but you guys should work with AWS, Epic Games (Fortnite) and Player Unknown's Battlegrounds to resolve this mess.
I setup an AWS EC2 Linux instance just to test UDP with iperf3. Here are the results: 21% packet loss.
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 68.x.x.x, port 55263
[ 6] local x.x.x.x port 5201 connected to 68.x.x.x port 62720
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 6] 0.00-1.00 sec 88.0 KBytes 721 Kbits/sec 17.420 ms 4/15 (27%)
[ 6] 1.00-2.00 sec 96.0 KBytes 786 Kbits/sec 9.554 ms 4/16 (25%)
[ 6] 2.00-3.00 sec 112 KBytes 917 Kbits/sec 5.416 ms 2/16 (12%)
[ 6] 3.00-4.00 sec 112 KBytes 918 Kbits/sec 3.207 ms 2/16 (12%)
[ 6] 4.00-5.00 sec 96.0 KBytes 786 Kbits/sec 2.406 ms 5/17 (29%)
[ 6] 5.00-6.00 sec 72.0 KBytes 590 Kbits/sec 2.627 ms 6/15 (40%)
[ 6] 6.00-7.00 sec 96.0 KBytes 786 Kbits/sec 2.518 ms 4/16 (25%)
[ 6] 7.00-8.00 sec 104 KBytes 852 Kbits/sec 2.797 ms 3/16 (19%)
[ 6] 8.00-9.00 sec 64.0 KBytes 524 Kbits/sec 3.988 ms 8/16 (50%)
[ 6] 9.00-10.00 sec 48.0 KBytes 393 Kbits/sec 3.271 ms 8/14 (57%)
[ 6] 10.00-11.00 sec 72.0 KBytes 590 Kbits/sec 2.750 ms 9/18 (50%)
[ 6] 11.00-12.00 sec 88.0 KBytes 721 Kbits/sec 2.615 ms 4/15 (27%)
[ 6] 12.00-13.00 sec 72.0 KBytes 590 Kbits/sec 2.800 ms 7/16 (44%)
[ 6] 13.00-14.00 sec 88.0 KBytes 721 Kbits/sec 2.964 ms 6/17 (35%)
[ 6] 14.00-15.00 sec 104 KBytes 852 Kbits/sec 2.846 ms 3/16 (19%)
[ 6] 15.00-16.00 sec 88.0 KBytes 721 Kbits/sec 2.035 ms 5/16 (31%)
[ 6] 16.00-17.00 sec 104 KBytes 852 Kbits/sec 2.137 ms 2/15 (13%)
[ 6] 17.00-18.00 sec 112 KBytes 918 Kbits/sec 2.919 ms 3/17 (18%)
[ 6] 18.00-19.00 sec 120 KBytes 983 Kbits/sec 3.075 ms 1/16 (6.2%)
[ 6] 19.00-20.00 sec 120 KBytes 983 Kbits/sec 3.002 ms 1/16 (6.2%)
[ 6] 20.00-21.00 sec 128 KBytes 1.05 Mbits/sec 3.422 ms 0/16 (0%)
[ 6] 21.00-22.00 sec 120 KBytes 983 Kbits/sec 2.645 ms 1/16 (6.2%)
[ 6] 22.00-23.00 sec 112 KBytes 918 Kbits/sec 3.005 ms 2/16 (12%)
[ 6] 23.00-24.00 sec 128 KBytes 1.05 Mbits/sec 2.907 ms 1/17 (5.9%)
[ 6] 24.00-25.00 sec 112 KBytes 917 Kbits/sec 3.063 ms 1/15 (6.7%)
[ 6] 25.00-26.00 sec 128 KBytes 1.05 Mbits/sec 2.634 ms 0/16 (0%)
[ 6] 26.00-27.00 sec 112 KBytes 917 Kbits/sec 2.444 ms 3/17 (18%)
[ 6] 27.00-28.00 sec 112 KBytes 918 Kbits/sec 3.426 ms 1/15 (6.7%)
[ 6] 28.00-29.00 sec 128 KBytes 1.05 Mbits/sec 3.109 ms 0/16 (0%)
[ 6] 29.00-30.00 sec 120 KBytes 983 Kbits/sec 2.962 ms 1/16 (6.2%)
[ 6] 30.00-31.00 sec 112 KBytes 917 Kbits/sec 3.048 ms 2/16 (12%)
[ 6] 31.00-32.00 sec 128 KBytes 1.05 Mbits/sec 3.492 ms 0/16 (0%)
[ 6] 32.00-33.00 sec 104 KBytes 852 Kbits/sec 3.251 ms 2/15 (13%)
[ 6] 33.00-34.00 sec 104 KBytes 852 Kbits/sec 2.271 ms 4/17 (24%)
[ 6] 34.00-35.00 sec 112 KBytes 917 Kbits/sec 2.034 ms 2/16 (12%)
[ 6] 35.00-36.00 sec 112 KBytes 918 Kbits/sec 2.483 ms 2/16 (12%)
[ 6] 36.00-37.00 sec 112 KBytes 917 Kbits/sec 2.645 ms 2/16 (12%)
[ 6] 37.00-38.00 sec 112 KBytes 917 Kbits/sec 2.536 ms 2/16 (12%)
[ 6] 38.00-39.00 sec 128 KBytes 1.05 Mbits/sec 2.528 ms 0/16 (0%)
[ 6] 39.00-40.00 sec 104 KBytes 852 Kbits/sec 2.638 ms 2/15 (13%)
[ 6] 40.00-41.00 sec 104 KBytes 852 Kbits/sec 2.698 ms 4/17 (24%)
[ 6] 41.00-42.00 sec 104 KBytes 852 Kbits/sec 3.032 ms 3/16 (19%)
[ 6] 42.00-43.00 sec 96.0 KBytes 786 Kbits/sec 2.152 ms 4/16 (25%)
[ 6] 43.00-44.00 sec 120 KBytes 983 Kbits/sec 1.542 ms 1/16 (6.2%)
[ 6] 44.00-45.00 sec 112 KBytes 917 Kbits/sec 2.382 ms 3/17 (18%)
[ 6] 45.00-46.00 sec 72.0 KBytes 590 Kbits/sec 2.276 ms 6/15 (40%)
[ 6] 46.00-47.00 sec 120 KBytes 983 Kbits/sec 2.426 ms 1/16 (6.2%)
[ 6] 47.00-48.00 sec 120 KBytes 983 Kbits/sec 2.867 ms 1/16 (6.2%)
[ 6] 48.00-49.00 sec 96.0 KBytes 786 Kbits/sec 3.072 ms 3/15 (20%)
[ 6] 49.00-50.00 sec 112 KBytes 917 Kbits/sec 2.655 ms 3/17 (18%)
[ 6] 50.00-51.00 sec 96.0 KBytes 787 Kbits/sec 2.251 ms 4/16 (25%)
[ 6] 51.00-52.00 sec 64.0 KBytes 524 Kbits/sec 3.056 ms 8/16 (50%)
[ 6] 52.00-53.00 sec 80.0 KBytes 655 Kbits/sec 2.864 ms 5/15 (33%)
[ 6] 53.00-54.00 sec 112 KBytes 918 Kbits/sec 2.456 ms 4/18 (22%)
[ 6] 54.00-55.00 sec 88.0 KBytes 721 Kbits/sec 2.957 ms 4/15 (27%)
[ 6] 55.00-56.00 sec 72.0 KBytes 590 Kbits/sec 2.581 ms 7/16 (44%)
[ 6] 56.00-57.00 sec 72.0 KBytes 590 Kbits/sec 2.722 ms 8/17 (47%)
[ 6] 57.00-58.00 sec 40.0 KBytes 328 Kbits/sec 2.656 ms 11/16 (69%)
[ 6] 58.00-59.00 sec 72.0 KBytes 590 Kbits/sec 2.980 ms 5/14 (36%)
[ 6] 59.00-60.00 sec 80.0 KBytes 655 Kbits/sec 3.039 ms 7/17 (41%)
[ 6] 60.00-61.00 sec 64.0 KBytes 524 Kbits/sec 2.866 ms 9/17 (53%)
[ 6] 61.00-62.00 sec 40.0 KBytes 328 Kbits/sec 3.395 ms 10/15 (67%)
[ 6] 62.00-63.00 sec 96.0 KBytes 786 Kbits/sec 2.760 ms 4/16 (25%)
[ 6] 63.00-64.00 sec 120 KBytes 983 Kbits/sec 2.528 ms 1/16 (6.2%)
[ 6] 64.00-65.00 sec 120 KBytes 983 Kbits/sec 2.819 ms 1/16 (6.2%)
[ 6] 65.00-66.00 sec 128 KBytes 1.05 Mbits/sec 2.580 ms 0/16 (0%)
[ 6] 66.00-67.00 sec 128 KBytes 1.05 Mbits/sec 2.338 ms 0/16 (0%)
[ 6] 67.00-68.00 sec 128 KBytes 1.05 Mbits/sec 3.216 ms 0/16 (0%)
[ 6] 68.00-69.00 sec 120 KBytes 983 Kbits/sec 3.406 ms 1/16 (6.2%)
[ 6] 69.00-70.00 sec 120 KBytes 983 Kbits/sec 3.222 ms 2/17 (12%)
[ 6] 70.00-71.00 sec 96.0 KBytes 786 Kbits/sec 2.446 ms 3/15 (20%)
[ 6] 71.00-72.00 sec 112 KBytes 918 Kbits/sec 2.335 ms 2/16 (12%)
[ 6] 72.00-73.00 sec 112 KBytes 917 Kbits/sec 2.272 ms 1/15 (6.7%)
[ 6] 73.00-74.00 sec 112 KBytes 918 Kbits/sec 2.429 ms 3/17 (18%)
[ 6] 74.00-75.00 sec 96.0 KBytes 786 Kbits/sec 2.136 ms 4/16 (25%)
[ 6] 75.00-76.00 sec 104 KBytes 852 Kbits/sec 1.990 ms 3/16 (19%)
[ 6] 76.00-77.00 sec 112 KBytes 918 Kbits/sec 2.740 ms 2/16 (12%)
[ 6] 77.00-78.00 sec 112 KBytes 918 Kbits/sec 2.549 ms 2/16 (12%)
[ 6] 78.00-79.00 sec 104 KBytes 852 Kbits/sec 2.237 ms 2/15 (13%)
[ 6] 79.00-80.00 sec 96.0 KBytes 786 Kbits/sec 4.430 ms 4/16 (25%)
[ 6] 80.00-81.00 sec 96.0 KBytes 786 Kbits/sec 3.335 ms 5/17 (29%)
[ 6] 81.00-82.00 sec 104 KBytes 852 Kbits/sec 3.003 ms 2/15 (13%)
[ 6] 82.00-83.00 sec 80.0 KBytes 655 Kbits/sec 4.371 ms 6/16 (38%)
[ 6] 83.00-84.00 sec 96.0 KBytes 786 Kbits/sec 3.812 ms 3/15 (20%)
[ 6] 84.00-85.00 sec 112 KBytes 918 Kbits/sec 2.792 ms 3/17 (18%)
[ 6] 85.00-86.00 sec 112 KBytes 918 Kbits/sec 2.377 ms 3/17 (18%)
[ 6] 86.00-87.00 sec 96.0 KBytes 786 Kbits/sec 2.668 ms 4/16 (25%)
[ 6] 87.00-88.00 sec 112 KBytes 918 Kbits/sec 2.592 ms 2/16 (12%)
[ 6] 88.00-89.00 sec 104 KBytes 852 Kbits/sec 2.643 ms 3/16 (19%)
[ 6] 89.00-90.00 sec 96.0 KBytes 786 Kbits/sec 2.411 ms 4/16 (25%)
[ 6] 90.00-91.00 sec 112 KBytes 918 Kbits/sec 2.253 ms 3/17 (18%)
[ 6] 91.00-92.00 sec 112 KBytes 917 Kbits/sec 3.056 ms 1/15 (6.7%)
[ 6] 92.00-93.00 sec 104 KBytes 852 Kbits/sec 5.049 ms 3/16 (19%)
[ 6] 93.00-94.00 sec 112 KBytes 918 Kbits/sec 2.995 ms 3/17 (18%)
[ 6] 94.00-95.00 sec 96.0 KBytes 786 Kbits/sec 2.978 ms 3/15 (20%)
[ 6] 95.00-96.00 sec 96.0 KBytes 786 Kbits/sec 3.705 ms 3/15 (20%)
[ 6] 96.00-97.00 sec 112 KBytes 918 Kbits/sec 3.610 ms 4/18 (22%)
[ 6] 97.00-98.00 sec 96.0 KBytes 786 Kbits/sec 3.086 ms 4/16 (25%)
[ 6] 98.00-99.00 sec 80.0 KBytes 655 Kbits/sec 3.046 ms 4/14 (29%)
[ 6] 99.00-100.00 sec 104 KBytes 852 Kbits/sec 2.643 ms 5/18 (28%)
[ 6] 100.00-100.08 sec 0.00 Bytes 0.00 bits/sec 2.643 ms 0/0 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 6] 0.00-100.08 sec 0.00 Bytes 0.00 bits/sec 2.643 ms 329/1600 (21%)
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
2
0