12,270
edits
Slow FTTP: Difference between revisions
m
→Diagnostics you can run from a computer:
|
#'''Ping tests:''' <br> running ping tests from the 'command line' can help see if there is any strange loss or latency.
## '''ping your router:''' <br> This will test your local connection. eg, if your router (gateway) is 192.168.0.1 then run this to send 100 pings: <syntaxhighlight>(on windows) ping -n 100 192.168.0.1</syntaxhighlight> <syntaxhighlight>(on Mac) ping -c 100 192.168.0.1</syntaxhighlight> and let us know the last few lines containing the results, which show any loss, the latency and jitter, eg:<syntaxhighlight>
--- 192.168.0.1 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 100970ms
rtt min/avg/max/mdev = 0.137/0.172/0.736/0.068 ms</syntaxhighlight>
## '''Ping our network:''' <br>This will ping 100 times through your router to us, and therefore tests your connection to our network <syntaxhighlight>(on windows) ping -n 100 81.18781.187</syntaxhighlight> <syntaxhighlight>(on Mac) ping -c 100 81.18781.187</syntaxhighlight>
##'''Ping with larger packet sizes''' <br> normal pings send small packets, sometimes a problem can affect large packets, so try these two pings, and send in the results: <syntaxhighlight>(on windows) ping -n 100 -f -l 1400 81.18781.187</syntaxhighlight> <syntaxhighlight>(on windows) ping -n 100 -f -l 1472 81.18781.187</syntaxhighlight> <syntaxhighlight>(on Mac) ping -c 100 -D -s 1400 81.18781.187</syntaxhighlight> <syntaxhighlight>(on Mac) ping -c 100 -D -s 1472 81.18781.187</syntaxhighlight>
#'''Speed test web sites:''' <br>Use ours and some other 3rd party ones to check up and download speeds run these at different times of day as this can help track 'peak time congestion'. note - many http speed testers are not very good for testing 1G connections - always take results with a pinch of salt
| |||