Slow FTTP: Difference between revisions
Appearance
Content deleted Content added
| Line 80: | Line 80: | ||
These are tests you can from your computer, some of them (eg the ping) will need you to use a command prompt or terminal to enter the commands. Do gen in touch if you need help with how to do that. |
These are tests you can from your computer, some of them (eg the ping) will need you to use a command prompt or terminal to enter the commands. Do gen in touch if you need help with how to do that. |
||
#'''Ping tests:''' <br> running ping tests from the 'command line' can help see if there is any strange loss or latency. |
#'''Ping tests:''' <br> running ping tests from the 'command line' can help see if there is any strange loss or latency. <br> ''Expected results'': The ping results should show 0% loss and the latency should be below 20ms, any thing else would need further investigation. |
||
## '''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> |
## '''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 --- |
--- 192.168.0.1 ping statistics --- |
||
| Line 87: | Line 87: | ||
## '''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 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> |
##'''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. That said, ''Expected results:'' The speeds tests should show around 900Mb/s download speed |
||
## ''Expected results'': The ping results should show 0% loss and the latency should be below 20ms, any thing else would need further investigation. |
|||
| ⚫ | #'''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 |
||
## https://speedtest.aa.net.uk |
## https://speedtest.aa.net.uk |
||
## https://www.fast.com |
## https://www.fast.com |
||
## ''Expected results:'' The speeds tests should show around 900Mb/s download speed |
|||
# '''iperf''' <br> Ask us about testing with ''''iperf'''' - as this is generally better than http speed test websites. See: https://support.aa.net.uk/Windows_iperf3 |
# '''iperf''' <br> Ask us about testing with ''''iperf'''' - as this is generally better than http speed test websites. See: https://support.aa.net.uk/Windows_iperf3 |
||
# ...'''get in touch'''. |
# ...'''get in touch'''. |
||