willphule Posted January 22, 2016 Posted January 22, 2016 I was implementing some suggestions from Fraser tonight, and in the midst of everything I ran into a new (not netduma related) issue. The ps4 reported that I didn't have a DNS connection. I noticed I had left the custom setting for google dns in my wired internet setting. I do this every time there is a large update to download on ps4 (and yes, I know DNS doesn't affect speed - however I've used this trick more times then I care to count and for large downloads, for whatever unknown reason (maybe just path routing?), it has a massive & measureable effect) Anyway, I blew that out and it connected just fine with my isp's dns. However, being the curious type I ran the internet diagnostic on the netduma as I know they ping the google dns server. Last night everything was fine - tonight's results are below along with ping plotter results. This is the first of many test I've run over the past week since I received the netduma in which I've seen packet loss, let alone the weird google dns results. Ping Jitter Spikes Packet Loss Good Exceptional Exceptional Lost 1 Show Details PingPING 8.8.8.8 (8.8.8.8): 56 data bytes64 bytes from 8.8.8.8: seq=0 ttl=42 time=26.807 ms64 bytes from 8.8.8.8: seq=1 ttl=42 time=25.947 ms64 bytes from 8.8.8.8: seq=2 ttl=42 time=26.165 ms64 bytes from 8.8.8.8: seq=3 ttl=42 time=26.105 ms64 bytes from 8.8.8.8: seq=5 ttl=42 time=25.959 ms64 bytes from 8.8.8.8: seq=6 ttl=42 time=26.125 ms64 bytes from 8.8.8.8: seq=7 ttl=42 time=26.138 ms64 bytes from 8.8.8.8: seq=8 ttl=42 time=25.913 ms64 bytes from 8.8.8.8: seq=9 ttl=42 time=25.900 ms64 bytes from 8.8.8.8: seq=10 ttl=42 time=25.982 ms64 bytes from 8.8.8.8: seq=11 ttl=42 time=25.929 ms64 bytes from 8.8.8.8: seq=12 ttl=42 time=25.942 ms64 bytes from 8.8.8.8: seq=13 ttl=42 time=26.071 ms64 bytes from 8.8.8.8: seq=14 ttl=42 time=25.901 ms64 bytes from 8.8.8.8: seq=15 ttl=42 time=26.005 ms64 bytes from 8.8.8.8: seq=16 ttl=42 time=25.958 ms64 bytes from 8.8.8.8: seq=17 ttl=42 time=25.975 ms64 bytes from 8.8.8.8: seq=18 ttl=42 time=26.029 ms64 bytes from 8.8.8.8: seq=19 ttl=42 time=25.951 ms64 bytes from 8.8.8.8: seq=20 ttl=42 time=25.932 ms--- 8.8.8.8 ping statistics ---21 packets transmitted, 20 packets received, 4% packet lossround-trip min/avg/max = 25.900/26.036/26.807 ms Tracetraceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets1 69.18.43.41 0.330 ms 0.265 ms 0.268 ms2 69.18.32.1 0.585 ms 0.320 ms 0.407 ms3 38.108.132.169 4.958 ms 4.738 ms 4.890 ms4 154.54.47.133 5.037 ms 154.54.47.129 5.026 ms 154.54.47.133 5.001 ms5 154.54.29.125 12.027 ms 12.183 ms 154.54.29.49 14.673 ms6 154.54.46.178 12.411 ms 12.213 ms 154.54.45.18 12.075 ms7 38.88.204.78 38.094 ms 16.485 ms 18.036 ms8 209.85.254.128 16.442 ms 209.85.143.154 16.014 ms 209.85.254.120 16.562 ms9 72.14.238.89 16.508 ms 216.239.50.234 16.117 ms 209.85.241.47 16.654 ms10 216.239.47.45 26.152 ms 209.85.244.209 57.136 ms 216.239.47.103 72.058 ms11 216.239.43.217 26.404 ms 216.239.46.191 25.918 ms 216.239.43.219 25.966 ms12 * * *13 8.8.8.8 25.969 ms 25.916 ms 25.874 ms Target Name: google-public-dns-a.google.com IP: 8.8.8.8 Date/Time: 1/21/2016 11:05:04 PM to 1/21/2016 11:05:44 PM Hop Sent Err PL% Min Max Avg Host Name / [iP] 1 16 0 0.0 0 2 0 [192.168.88.1] 2 16 0 0.0 1 11 2 69-18-43-41.lisco.net [69.18.43.41] 3 16 0 0.0 1 3 1 lisco-gw.lisco.com [69.18.32.1] 4 16 0 0.0 5 36 7 gi0-0-0-1.agr12.dsm01.atlas.cogentco.com [38.108.132.169] 5 16 0 0.0 5 9 5 te0-0-1-3.rcr12.dsm01.atlas.cogentco.com [154.54.47.133] 6 16 0 0.0 12 13 12 be2640.ccr42.ord01.atlas.cogentco.com [154.54.29.125] 7 16 0 0.0 12 14 12 be2766.ccr41.ord03.atlas.cogentco.com [154.54.46.178] 8 16 0 0.0 17 33 18 [38.88.204.78] 9 16 0 0.0 17 21 17 [209.85.143.186] 10 16 0 0.0 17 27 18 [72.14.238.89] 11 16 0 0.0 26 73 33 [216.239.47.121] 12 16 0 0.0 26 37 27 [216.239.46.191] 13 15 15 100 0 0 0 [-] 14 16 0 0.0 26 31 26 google-public-dns-a.google.com [8.8.8.8]
Administrators Netduma Fraser Posted January 22, 2016 Administrators Posted January 22, 2016 It looks okay to me, you are getting a little bit of packet loss. This may be to do with your line. I'd keep an eye on it and see if it persists. Perhaps download Ping Plotter and run some tests over different times/days to see if it carries on
Recommended Posts
Archived
This topic is now archived and is closed to further replies.