12,270
edits
Slow FTTP: Difference between revisions
m
→Things to test and try
|
If your FTTP service is slow, eg a speed test is not reporting expected speeds, then try these:
# Use our '''speed test''' and some other 3rd party ones to check up and download speeds: https://speedtest.aa.net.uk https://www.fast.com- try tests at different times of the 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▼
===Checking the hardware and connections===
# Try a '''wired connection''' from your computer instead of WiFi to rule out any WiFi problems.
# Try a '''power cycle''' of the Openreach/CityFibre ONT - always worth a try!▼
# '''Check/swap the cable''' between the ONT (The Openreach/CityFibre unit that the fibre connects to) and your router - ensure it's a '''8-wire''' CAT5 or CAT6 cable - not one with 4 wires as these will run at 100M and not 1G.▼
# Connect your computer directly in to the router - so as to bypass any other switches you have - this will help eliminate other equipment in the path to your router
# '''Ensure the router is capable of the speed''' of the circuit - eg, maybe you have a 1G service but an older router? - let us know the model you are using
# Check the '''CQM Graphs''', via the Control Pages, to see if it is slow due to lots of traffic.▼
# Ask us about testing with ''''iperf'''' - as this is generally better than http speed test websites. See: https://support.aa.net.uk/Windows_iperf3▼
# Try a '''laptop/PC plugged directly in to the ONT''' instead of using your router - set up a new network connection of type PPPoE and use your xxx@a login and password to connect, and run a speed test. see: [[PPPoE_on_a_Computer]] for more help on this.
# Try a different computer/device
▲# Try a '''power cycle''' of the Openreach/CityFibre ONT
===Actual tests to run:===
#'''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: <syntaxhighlight>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 through your router to us, and therefore tests your connection to our network <syntaxhighlight>ping -c 100 81.18781.187</syntaxhighlight>
▲#
## https://speedtest.aa.net.uk
## https://www.fast.com
▲# '''Check/swap the cable''' between the ONT (The Openreach/CityFibre unit that the fibre connects to) and your router - ensure it's a '''8-wire''' CAT5 or CAT6 cable - not one with 4 wires as these will run at 100M and not 1G.
▲# Check the '''CQM Graphs''', via the Control Pages, to see if it is slow due to lots of traffic.
▲# Ask us about testing with ''''iperf'''' - as this is generally better than http speed test websites. See: https://support.aa.net.uk/Windows_iperf3
#Check for '''packet loss''' - see below.
# ...'''get in touch'''.
| |||