MatthewHannah's profile

New Poster

 • 

3 Messages

Wednesday, June 3rd, 2020

Closed

Large Packet SIze Loss between Some Hosts

I'm experiencing high packet loss with large packets (~1400 bytes) to particular hosts (i.e. not everyone but consistently the same group).  I have a few wireshark captures showing a lot of TCP retransmissions and missing packets to sites like news.ycombinator.com and dmtf.org for example as well as a DigitalOcean VPS that I have.

Here's an example traceroute and ping demonstrating the packet loss between my VPS and home network as well as  working and non-working website traffic from wireshark

 

From VPS:

 

root@host:~# ping 76.122.108.97 -s 1400
PING 76.122.108.97 (76.122.108.97) 1400(1428) bytes of data.
1408 bytes from 76.122.108.97: icmp_seq=4 ttl=51 time=68.8 ms
1408 bytes from 76.122.108.97: icmp_seq=5 ttl=51 time=68.8 ms
1408 bytes from 76.122.108.97: icmp_seq=8 ttl=51 time=68.3 ms
1408 bytes from 76.122.108.97: icmp_seq=11 ttl=51 time=68.7 ms
1408 bytes from 76.122.108.97: icmp_seq=13 ttl=51 time=69.0 ms
^C
--- 76.122.108.97 ping statistics ---
17 packets transmitted, 5 received, 70% packet loss, time 16201ms
rtt min/avg/max/mdev = 68.331/68.768/69.044/0.237 ms
root@host:~# traceroute 76.122.108.97
traceroute to 76.122.108.97 (76.122.108.97), 30 hops max, 60 byte packets
1 64.227.48.253 (64.227.48.253) 1.646 ms 1.783 ms 64.227.48.254 (64.227.48.254) 1.064 ms
2 138.197.249.146 (138.197.249.146) 19.528 ms 138.197.249.156 (138.197.249.156) 1.251 ms 138.197.249.150 (138.197.249.150) 1.237 ms
3 138.197.249.188 (138.197.249.188) 2.327 ms 138.197.249.176 (138.197.249.176) 1.046 ms 1.040 ms
4 * * *
5 ae-2-3601.edge6.Atlanta2.Level3.net (4.69.219.150) 59.759 ms 59.765 ms 59.755 ms
6 ComcastRegional-level3-200G.Atlanta2.Level3.net (4.68.38.110) 60.462 ms 60.186 ms 60.098 ms
7 96.108.116.46 (96.108.116.46) 61.103 ms 61.122 ms 61.109 ms
8 ae2-acr11.a2atlanta.ga.atlanta.comcast.net (96.110.204.158) 60.488 ms 60.269 ms 60.490 ms
9 c-76-122-108-97.hsd1.ga.comcast.net (76.122.108.97) 72.564 ms 68.640 ms 68.649 ms
root@host:~# ping 76.122.108.97 -s 50
PING 76.122.108.97 (76.122.108.97) 50(78) bytes of data.
58 bytes from 76.122.108.97: icmp_seq=3 ttl=51 time=67.7 ms
58 bytes from 76.122.108.97: icmp_seq=4 ttl=51 time=75.5 ms
58 bytes from 76.122.108.97: icmp_seq=6 ttl=51 time=77.2 ms
58 bytes from 76.122.108.97: icmp_seq=7 ttl=51 time=67.6 ms
58 bytes from 76.122.108.97: icmp_seq=8 ttl=51 time=67.3 ms
58 bytes from 76.122.108.97: icmp_seq=9 ttl=51 time=67.2 ms
58 bytes from 76.122.108.97: icmp_seq=10 ttl=51 time=67.1 ms
58 bytes from 76.122.108.97: icmp_seq=11 ttl=51 time=68.6 ms
58 bytes from 76.122.108.97: icmp_seq=12 ttl=51 time=67.2 ms
58 bytes from 76.122.108.97: icmp_seq=13 ttl=51 time=68.2 ms
58 bytes from 76.122.108.97: icmp_seq=14 ttl=51 time=67.5 ms
58 bytes from 76.122.108.97: icmp_seq=15 ttl=51 time=67.6 ms
58 bytes from 76.122.108.97: icmp_seq=16 ttl=51 time=67.5 ms
58 bytes from 76.122.108.97: icmp_seq=17 ttl=51 time=67.9 ms
58 bytes from 76.122.108.97: icmp_seq=18 ttl=51 time=67.3 ms
^C
--- 76.122.108.97 ping statistics ---
18 packets transmitted, 15 received, 16% packet loss, time 17050ms
rtt min/avg/max/mdev = 67.159/68.817/77.250/3.032 ms

 

From Home

PS C:\Users\matth> ping 64.227.53.198 -l 1400 -t

Pinging 64.227.53.198 with 1400 bytes of data:
Request timed out.
Reply from 64.227.53.198: bytes=1400 time=71ms TTL=55
Request timed out.
Request timed out.
Reply from 64.227.53.198: bytes=1400 time=70ms TTL=55
Request timed out.
Reply from 64.227.53.198: bytes=1400 time=70ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.227.53.198: bytes=1400 time=70ms TTL=55
Request timed out.

Ping statistics for 64.227.53.198:
Packets: Sent = 13, Received = 4, Lost = 9 (69% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 71ms, Average = 70ms
Control-C
PS C:\Users\matth> tracert 64.227.53.198

Tracing route to 64.227.53.198 over a maximum of 30 hops

1 2 ms 1 ms 1 ms LEDE.lan [192.168.1.1]
2 10 ms 8 ms 8 ms 96.120.4.225
3 34 ms 9 ms * ae44-rur102.a2atlanta.ga.atlanta.comcast.net [96.110.204.157]
4 10 ms 9 ms 10 ms 96.108.150.213
5 13 ms 12 ms 11 ms 96.108.116.41
6 13 ms 11 ms 9 ms be-33041-cs04.56marietta.ga.ibone.comcast.net [96.110.43.77]
7 9 ms 9 ms 9 ms be-2401-pe01.56marietta.ga.ibone.comcast.net [96.110.32.98]
8 * * * Request timed out.
9 29 ms 27 ms 27 ms dls-b22-link.telia.net [62.115.120.113]
10 56 ms 57 ms 54 ms las-b24-link.telia.net [62.115.118.247]
11 86 ms 80 ms 63 ms palo-b22-link.telia.net [62.115.119.90]
12 69 ms 69 ms 69 ms digitalocean-ic-336107-palo-b22.c.telia.net [213.248.99.163]
13 * * * Request timed out.
14 * * * Request timed out.
15 71 ms 68 ms 68 ms 64.227.53.198

Trace complete.

 

Wireshark Capture of working website (gatech.edu) then of non-working website (news.ycombinator.com)gatech_wireshark.PNGhn_wireshark.PNG

 

 

 

This conversation is no longer open for comments or replies and is no longer visible to community members.

Oldest First
Selected Oldest First
No Responses!
forum icon

New to the Community?

Start Here