doozy:System: For the first night in a while i have had bad pings:
Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=863ms TTL=121
Reply from 146.171.18.242: bytes=32 time=525ms TTL=121
Reply from 146.171.18.242: bytes=32 time=454ms TTL=121
Reply from 146.171.18.242: bytes=32 time=542ms TTL=121
Ping statistics for 146.171.18.242:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 454ms, Maximum = 863ms, Average = 596ms
So if anything the solution to fix it has only made the problem bigger
I should have added the problem device is right on the edge of the network so pings to Telecom.co would not be affected, this is not related
So now there is a problem with national traffic? Lol get out the popcorn guys.
ping telecom.co.nz -t
Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=40ms TTL=120
Reply from 146.171.18.242: bytes=32 time=38ms TTL=120
Reply from 146.171.18.242: bytes=32 time=47ms TTL=120
Reply from 146.171.18.242: bytes=32 time=53ms TTL=120
Reply from 146.171.18.242: bytes=32 time=61ms TTL=120
Reply from 146.171.18.242: bytes=32 time=66ms TTL=120
Reply from 146.171.18.242: bytes=32 time=75ms TTL=120
Reply from 146.171.18.242: bytes=32 time=48ms TTL=120
Reply from 146.171.18.242: bytes=32 time=62ms TTL=120
Reply from 146.171.18.242: bytes=32 time=41ms TTL=120
Reply from 146.171.18.242: bytes=32 time=52ms TTL=120
Reply from 146.171.18.242: bytes=32 time=30ms TTL=120
Reply from 146.171.18.242: bytes=32 time=68ms TTL=120
Reply from 146.171.18.242: bytes=32 time=41ms TTL=120