New FTTP

[Madhatter]

Hi, I've had FTTP installed and using a Fritzbox 7530. Changed it to use modem and it's connected, the DL speeds are a 6th of what they should be. I am getting 83MB down and 57 up, package is 500 DL and 68 UL. Will it improve or is there a fault?

[Madhatter]

Hi Ripshod,

Ever since they updated the router, I don't have quite a few menu options that I had before.

I have gone through everything and other pinhole, there is nothing to disable IP6.

[Jayach]

It's on the LAN menu. 

[Madhatter]

These are the pings with IP^ turned off, did it for both LN and wifi

C:\>ping www.google.com

Pinging www.google.com [142.250.180.4] with 32 bytes of data:
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=10ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=14ms TTL=60

Ping statistics for 142.250.180.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 14ms, Average = 11ms

C:\>ping www.google.com

Pinging www.google.com [142.250.180.4] with 32 bytes of data:
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60

Ping statistics for 142.250.180.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms

C:\>ping www.google.com

Pinging www.google.com [142.250.180.4] with 32 bytes of data:
Reply from 142.250.180.4: bytes=32 time=12ms TTL=60
Reply from 142.250.180.4: bytes=32 time=14ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60

Ping statistics for 142.250.180.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 14ms, Average = 12ms

C:\>ping www.google.com

Pinging www.google.com [142.250.180.4] with 32 bytes of data:
Reply from 142.250.180.4: bytes=32 time=91ms TTL=60
Reply from 142.250.180.4: bytes=32 time=55ms TTL=60
Reply from 142.250.180.4: bytes=32 time=79ms TTL=60
Reply from 142.250.180.4: bytes=32 time=107ms TTL=60

Ping statistics for 142.250.180.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 107ms, Average = 83ms

C:\>ping www.google.com

Pinging www.google.com [142.250.180.4] with 32 bytes of data:
Reply from 142.250.180.4: bytes=32 time=241ms TTL=60
Reply from 142.250.180.4: bytes=32 time=168ms TTL=60
Reply from 142.250.180.4: bytes=32 time=211ms TTL=60
Reply from 142.250.180.4: bytes=32 time=213ms TTL=60

Ping statistics for 142.250.180.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 241ms, Average = 208ms

C:\>ping www.google.com

Pinging www.google.com [142.250.180.4] with 32 bytes of data:
Reply from 142.250.180.4: bytes=32 time=12ms TTL=60
Reply from 142.250.180.4: bytes=32 time=13ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60

Ping statistics for 142.250.180.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 13ms, Average = 11ms

C:\>ping www.google.com

Pinging www.google.com [142.250.180.4] with 32 bytes of data:
Reply from 142.250.180.4: bytes=32 time=14ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60

Ping statistics for 142.250.180.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 14ms, Average = 11ms

C:\>ping www.google.com

Pinging www.google.com [142.250.180.4] with 32 bytes of data:
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60
Reply from 142.250.180.4: bytes=32 time=11ms TTL=60

Ping statistics for 142.250.180.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms

C:\>

[Madhatter]

This is the tracert, few time out errors. Convinced them to replace the router, so lets see how that goes, is this down to network or VF. I am home alone so only thing consuming the bandwidth was youtube paused and work laptop.

C:\>tracrt www.google.com
'tracrt' is not recognized as an internal or external command,
operable program or batch file.

C:\>tracert www.google.com

Tracing route to www.google.com [142.250.178.4]
over a maximum of 30 hops:

1 4 ms 4 ms 4 ms vodafone.broadband [XXX.XXX.X.X]
2 10 ms 9 ms 10 ms 100.68.0.1
3 10 ms 10 ms 10 ms 63.130.172.27
4 * * * Request timed out.
5 13 ms 17 ms 14 ms 216.239.62.75
6 10 ms 11 ms 9 ms 142.250.215.127
7 13 ms 12 ms 11 ms lhr48s27-in-f4.1e100.net [142.250.178.4]

Trace complete.

C:\>tracert www.google.com

Tracing route to www.google.com [142.250.178.4]
over a maximum of 30 hops:

1 4 ms 4 ms 4 ms vodafone.broadband [XXX.XXX.X.X]
2 9 ms 17 ms 9 ms 100.68.0.1
3 11 ms 10 ms 10 ms 63.130.172.27
4 * * * Request timed out.
5 14 ms 14 ms 13 ms 216.239.62.75
6 12 ms 11 ms 11 ms 142.250.215.127
7 13 ms 14 ms 11 ms lhr48s27-in-f4.1e100.net [142.250.178.4]

Trace complete.

C:\>tracert www.google.com

Tracing route to www.google.com [142.250.178.4]
over a maximum of 30 hops:

1 920 ms 645 ms 7 ms vodafone.broadband [XXX.XXX.X.X]
2 9 ms 14 ms 12 ms 100.68.0.1
3 14 ms 15 ms 11 ms 63.130.172.27
4 * * * Request timed out.
5 * * 546 ms 216.239.62.75
6 678 ms 715 ms 688 ms 142.250.215.127
7 19 ms 10 ms 12 ms lhr48s27-in-f4.1e100.net [142.250.178.4]

Trace complete.

C:\>tracert www.google.com

Tracing route to www.google.com [142.250.180.4]
over a maximum of 30 hops:

1 4 ms 3 ms 4 ms vodafone.broadband [XXX.XXX.X.X]
2 18 ms 9 ms 10 ms 100.68.0.1
3 * 11 ms 11 ms 63.130.172.27
4 * * * Request timed out.
5 13 ms 12 ms 13 ms 216.239.40.71
6 13 ms 12 ms 11 ms 142.251.54.31
7 11 ms 24 ms 15 ms lhr25s32-in-f4.1e100.net [142.250.180.4]

Trace complete.

C:\>

[Ripshod]

Your public IP is CG-NAT, which is commonly being used alongside the new ipv6 service. Normally this is not a concern unless you want to access your home network externally in which case you'd have to use Ipv6 or request a static ip (I don't recommend this).

I can't find a location for your gateway in my databases but other members have other resources.

We've seen all we need to see, you can enable Ipv6 again. 

[Ripshod]

Results for the 4th and 5th round do show inconsistencies we wouldn't expect unless you were being connected to USA servers.

Out of interest run a traceroute to bbc.com

[Madhatter]

This is to BBC, seems like same thing, could it be because am using cloudflare DNS? will change back to VF and see if any change

C:\>tracert www.bbc.co.uk

Tracing route to gtm-uk.www.bbc.co.uk.pri.bbc.co.uk [212.58.236.129]
over a maximum of 30 hops:

1 4 ms 3 ms 6 ms vodafone.broadband [XXX.XXX.X.X]
2 9 ms 10 ms 13 ms 100.68.0.1
3 * 11 ms * 63.130.172.39
4 11 ms 11 ms 39 ms 90.244.159.77
5 12 ms 12 ms 12 ms 132.185.249.90
6 11 ms 13 ms 11 ms 212.58.236.129

Trace complete.

C:\>tracert www.bbc.co.uk

Tracing route to gtm-uk.www.bbc.co.uk.pri.bbc.co.uk [212.58.236.129]
over a maximum of 30 hops:

1 4 ms 6 ms 3 ms vodafone.broadband [XXX.XXX.X.X]
2 10 ms 9 ms 9 ms 100.68.0.1
3 11 ms 11 ms * 63.130.172.39
4 11 ms 11 ms 13 ms 90.244.159.77
5 12 ms 12 ms 13 ms 132.185.249.90
6 10 ms 10 ms 10 ms 212.58.236.129

Trace complete.

C:\>tracert www.bbc.co.uk

Tracing route to gtm-uk.www.bbc.co.uk.pri.bbc.co.uk [212.58.236.129]
over a maximum of 30 hops:

1 4 ms 4 ms 4 ms vodafone.broadband [XXX.XXX.X.X]
2 10 ms 9 ms 9 ms 100.68.0.1
3 * * * Request timed out.
4 14 ms 14 ms 29 ms 90.244.159.77
5 12 ms 12 ms 16 ms 132.185.249.90
6 11 ms 11 ms 10 ms 212.58.236.129

Trace complete.

C:\>tracert www.bbc.co.uk

Tracing route to gtm-uk.www.bbc.co.uk.pri.bbc.co.uk [212.58.236.129]
over a maximum of 30 hops:

1 3 ms 4 ms 4 ms vodafone.broadband [XXX.XXX.X.X]
2 9 ms 9 ms 7 ms 100.68.0.1
3 * 10 ms * 63.130.172.39
4 12 ms 14 ms 12 ms 90.244.159.77
5 11 ms 12 ms 12 ms 132.185.249.90
6 180 ms 181 ms 138 ms 212.58.236.129

Trace complete.

[Ripshod]

That's much better other than the last hop on the last traceroute, but one-offs are not a concern. I still can't locate your gateway, it has an old cable and wireless ip that hasn't been updated since 2017 (vodafone bought old c&w infrastructure in the uk).

[Madhatter]

New router arrived and still getting some packet loss and funnily enough (not really😅) its connecting slower than t he old one so its not the router, left everything as is out of box.

C:\>ping www.google.com

Pinging www.google.com [2a00:1450:4009:827::2004] with 32 bytes of data:
Request timed out.
Reply from 2a00:1450:4009:827::2004: time=16ms
Reply from 2a00:1450:4009:827::2004: time=16ms
Reply from 2a00:1450:4009:827::2004: time=15ms

Ping statistics for 2a00:1450:4009:827::2004:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 16ms, Average = 15ms

C:\>ping www.google.com

Pinging www.google.com [2a00:1450:4009:827::2004] with 32 bytes of data:
Reply from 2a00:1450:4009:827::2004: time=15ms
Reply from 2a00:1450:4009:827::2004: time=15ms
Reply from 2a00:1450:4009:827::2004: time=15ms
Reply from 2a00:1450:4009:827::2004: time=15ms

Ping statistics for 2a00:1450:4009:827::2004:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 15ms, Average = 15ms

[Ripshod]

Those are great ping times for vodafone's fledgling Ipv6. I wouldn't worry too much about that one lost packet, it happens occasionally to the best routers for various reasons - remember ping is low priority compared to normal traffic.