Sign up with Google
gidzekse
Active Member
- Joined
- Feb 19, 2016
- Messages
- 82
hi all, anyone experience an issue whereby duplicate packets are being returned on their fibre?
started seeing this after some downtime we experienced the previous night:
PING google.com (172.217.170.46): 56 data bytes
64 bytes from 172.217.170.46: icmp_seq=0 ttl=55 time=7.737 ms
64 bytes from 172.217.170.46: icmp_seq=0 ttl=55 time=7.754 ms (DUP!)
64 bytes from 172.217.170.46: icmp_seq=1 ttl=55 time=4.143 ms
64 bytes from 172.217.170.46: icmp_seq=1 ttl=55 time=4.157 ms (DUP!)
64 bytes from 172.217.170.46: icmp_seq=2 ttl=55 time=4.282 ms
64 bytes from 172.217.170.46: icmp_seq=2 ttl=55 time=4.295 ms (DUP!)
anyone have any idea what it might be? I've tried pinging the devices within my network and I don't see the duplication so can only assume it's some bad routing between ISP and Fibre provider..
started seeing this after some downtime we experienced the previous night:
PING google.com (172.217.170.46): 56 data bytes
64 bytes from 172.217.170.46: icmp_seq=0 ttl=55 time=7.737 ms
64 bytes from 172.217.170.46: icmp_seq=0 ttl=55 time=7.754 ms (DUP!)
64 bytes from 172.217.170.46: icmp_seq=1 ttl=55 time=4.143 ms
64 bytes from 172.217.170.46: icmp_seq=1 ttl=55 time=4.157 ms (DUP!)
64 bytes from 172.217.170.46: icmp_seq=2 ttl=55 time=4.282 ms
64 bytes from 172.217.170.46: icmp_seq=2 ttl=55 time=4.295 ms (DUP!)
anyone have any idea what it might be? I've tried pinging the devices within my network and I don't see the duplication so can only assume it's some bad routing between ISP and Fibre provider..
