FTTP Install

Well all sorted. Was the Openreach engineers first install on his own so I was able to help out pulling cables etc. He took his time, after a few false starts with the connectorised FTTP he got it up and running.

2rdklu9.jpg

a1n2pj.jpg



It came with a BBU (battery backup) although we don't have FVA (voice over fibre) so he said if I wanted to I could just remove it. The ONT and BBU are contained in a small enclosure now, rather than being mounted on the wall separately.

156skfm.jpg
 
Caged said:
Nicely done. Did you get the cable routed how you wanted it?
Click to expand...

Yeah, I had buried some conduit a few weeks back, I just need to use some expanding foam/sealant now to block the tube.

nd4g2d.jpg



crinkleshoes said:
Weird to see such terrible speeds and ping from real fibre.

My Zen FTTC connection was better than that.
Click to expand...

I only went for the 76/19 package, so it's only going to be that, they do 150/30 and 300/50 but way overkill for my needs. BBC pings at 10ms average and google pings at 11ms which isn't too bad. Not sure why they chose FTTP here rather than FTTC, all the other local cabinets nearby are FTTC, just this is a new build.
 
Did you order direct with BT for this?

I am due to move to a new build soon which has FTTP however the postcode doesnt show anywhere for it to be installed
 
rah^ said:
Did you order direct with BT for this?

I am due to move to a new build soon which has FTTP however the postcode doesnt show anywhere for it to be installed
Click to expand...

Upgraded from ADSL with Zen, they were really good with communicating everything with the order. The order was placed 27th December, in mid January I got an update saying Openreach needed to do one last survey to make sure the network was installed and they had all details straight, then after that was confirmed the Openreach engineer came round today :)
 
That explains the speed but not the ping... are you on wireless maybe?

I’d expect an absolute maximum of 4ms ping to bbc, I get 2ms.

If you’re happy great - just might be some equipment getting in the way or an issue for it to be that high.
 
crinkleshoes said:
That explains the speed but not the ping... are you on wireless maybe?

I’d expect an absolute maximum of 4ms ping to bbc, I get 2ms.

If you’re happy great - just might be some equipment getting in the way or an issue for it to be that high.
Click to expand...

It’s Ethernet, but I am going :

ONT > Router > PC via internal Ethernet cabling. Would it be down to geographic location as well? Lancashire > London. Is there a way to determine latency on the LAN or at least at different stages of the connection?
 
Yes it does make a difference, we get pings of 11-13 to 8.8.8.8 in this area on fttp (similar distance to Manchester)
 
VaderDSL said:
It’s Ethernet, but I am going :

ONT > Router > PC via internal Ethernet cabling. Would it be down to geographic location as well? Lancashire > London. Is there a way to determine latency on the LAN or at least at different stages of the connection?
Click to expand...
bledd said:
Yes it does make a difference, we get pings of 11-13 to 8.8.8.8 in this area on fttp (similar distance to Manchester)
Click to expand...

Just did some testing from some client sites with leased lines in the Blackpool area & you're right... I'm seeing ~10ms ping to bbc & google.

I didn't think the variance would be so high within the same country... learnt something new :)

Sorry Vader, seems I was mistaken.

I'm getting 1ms to bbc today :/

zMjGuFf.png
 
crinkleshoes said:
Just did some testing from some client sites with leased lines in the Blackpool area & you're right... I'm seeing ~10ms ping to bbc & google.

I didn't think the variance would be so high within the same country... learnt something new :)

Sorry Vader, seems I was mistaken.

I'm getting 1ms to bbc today :/

zMjGuFf.png
Click to expand...

No problem! You have an awesome connection there! I wonder what the traceroute I have physically looks like, as in I'd love to be able to find out what route the data takes. I know where the cables roughly run to to get to the local exchange, but from there I have no idea where it goes.

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 11 ms 11 ms 11 ms vt1.cor2.lond1.ptn.zen.net.uk [51.148.72.22]
3 11 ms 11 ms 13 ms ae-9.agg2.lond1.ptn.zen.net.uk [51.148.73.16]
4 14 ms 12 ms 12 ms 51-148-73-55.dsl.zen.co.uk [51.148.73.55]
5 11 ms 11 ms 10 ms ip81-59.fastly-gw1.lonap.net [5.57.81.59]
6 11 ms 10 ms 11 ms 151.101.0.81

Is my traceroute to BBC.
 
It's likely an anycast address so the location will always return as the closest node to wherever the test is being run from.

A traceroute also won't show MPLS hops within a provider network, so the journey from your router back to the ISP via a third-party backhaul often doesn't show up. This is me on wireless:

Code: 
Tracing route to bbc.co.uk [2a04:4e42:600::81]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  broadband.bt.com
  2     *        *        *     Request timed out.
  3     8 ms     8 ms     8 ms  2a00:2302::100:1a
  4    13 ms     8 ms     8 ms  2a00:2302::100:23
  5     9 ms     8 ms     9 ms  2a00:2380:300c:b000::2
  6     9 ms     8 ms     8 ms  peer2-et0-1-3.slough.ukcore.bt.net [2a00:2380:c::301]
  7     9 ms     8 ms     8 ms  2620:11a:c000:140:fa57::
  8     8 ms     8 ms     8 ms  2a04:4e42:600::81

Trace complete.
 
Tracing route to bbc.co.uk [2a04:4e42::81]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 2a02:c7f:b200:5900::1
2 * * * Request timed out.
3 12 ms 14 ms 12 ms fastly-gw2.no-dns-yet.lonap.net [2001:7f8:17::d361:2]
4 12 ms 12 ms 13 ms fastly-gw2.no-dns-yet.lonap.net [2001:7f8:17::d361:2]
5 12 ms 11 ms 12 ms 2a04:4e42::81

Seems normal for me compared to the BT connection which is higher
 
You must log in or register to reply here.
Back
Top Bottom