New FTTP install

Had FTTP installed with BT this morning

Speedtest from http://www.speedtest.bbmax.co.uk via wired

18th May 2012 14:03:13 14693 Kbps 96698 Kbps
Any tips?

Engineer screwed up my internal wiring so extensions currently not working and is affecting the BE sync, so have had to raise a complaint with BT

http://www.speedtest.bbmax.co.uk/results.php?t=13373...

In reply to a post by nredwood:

http://www.speedtest.bbmax.co.uk/results.php?t=13373...

Some people get all the luck.

In reply to a post by nredwood:

Had FTTP installed with BT this morning

Speedtest from http://www.speedtest.bbmax.co.uk via wired

18th May 2012 14:03:13 14693 Kbps 96698 Kbps
Any tips?

Engineer screwed up my internal wiring so extensions currently not working and is affecting the BE sync, so have had to raise a complaint with BT

How has the technician screwed up your internal wiring. All he would do is move the three wires from one faceplate to another and nothing else.

In reply to a post by MHC:

How has the technician screwed up your internal wiring. All he would do is move the three wires from one faceplate to another and nothing else.

You'd think with FTTP he wouldn't need to touch any wiring at all !

If there was ADSL present he may (as I have already heard of) remove the existing filtered face plate and replace it with a standard. And that is the only change I would expect.

In reply to a post by MHC:

If there was ADSL present he may (as I have already heard of) remove the existing filtered face plate and replace it with a standard. And that is the only change I would expect.

Which seems ludicrous since FTTP and ADSL can coexist... As in the OP's case he still has BE ADSL 2+...

They fit a service specific faceplate with a copper to fibre switch

They wired the extensions to the faceplate wrong in the process - I wouldn't mind too much but my BE sync is down 5Mbps if I use the face plate socket, so currently have the BeBox and hpone plugged into the test socket

Not too shabby.

Is the upload on FTTP supposed to be about the same (maybe a little lower) than FTTC?
http://www.speedtest.bbmax.co.uk/results.php?t=13376...

Very nice results! When you start hitting these sorts of speeds then gigabit router, switch and NIC is required!

http://www.speedtest.bbmax.co.uk/results.php?t=13373...

I suspect that is the issue with my poor 6 year old PC

That test was done with a 1 year old laptop, plugged into the Gigabit port of the HH3

15Mbps upstream and I pretty much hit the max every time

The downstream seems a bit more variable, but it's early days yet

I've already decided I don't like the HH3 though, but not worth the purchase of yet another router until I'm on BE FTTP

lol

GLWT

See if you can get on the 330Mb/s trial.

What's latency like? A traceroute to bbc.co.uk and maybe qw.foppa.dk would be great!

In reply to a post by driz:

What's latency like? A traceroute to bbc.co.uk and maybe qw.foppa.dk would be great!

From a BT Infinity2 FTTC connection (can't imagine Infinity 100MB - i.e. FTTP would be significantly different)...

C:\Windows\system32>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BTHomeHub.home [192.168.1.254]
2 6 ms 6 ms 6 ms 217.32.140.67
3 7 ms 7 ms 6 ms 217.32.140.14
4 7 ms 6 ms 7 ms 213.120.161.26
5 7 ms 6 ms 6 ms 217.32.26.30
6 7 ms 6 ms 7 ms 217.32.26.178
7 7 ms 6 ms 6 ms acc1-10GigE-0-5-0-7.bm.21cn-ipp.bt.net [109.159.248.102]
8 14 ms 23 ms 23 ms core1-te0-3-0-3.ealing.ukcore.bt.net [109.159.248.20]
9 16 ms 16 ms 16 ms peer2-xe0-0-0.telehouse.ukcore.bt.net [109.159.254.102]
10 16 ms 16 ms 16 ms 194.74.65.42
11 * * * Request timed out.
12 16 ms 16 ms 16 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 17 ms 16 ms 16 ms 132.185.255.134
14 17 ms 16 ms 16 ms 212.58.241.131

Trace complete.

C:\Windows\system32>ping bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241

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

And

C:\Windows\system32>tracert qw.foppa.dk

Tracing route to qw.foppa.dk [89.104.194.146]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BTHomeHub.home [192.168.1.254]
2 6 ms 6 ms 6 ms 217.32.140.67
3 7 ms 6 ms 6 ms 217.32.140.30
4 7 ms 7 ms 6 ms 213.120.161.26
5 7 ms 6 ms 6 ms 217.32.26.30
6 7 ms 7 ms 6 ms 217.32.26.178
7 7 ms 7 ms 6 ms acc1-10GigE-0-7-0-5.bm.21cn-ipp.bt.net [109.159.248.78]
8 20 ms 23 ms 23 ms core1-te0-13-0-4.ealing.ukcore.bt.net [109.159.248.8]
9 63 ms 16 ms 16 ms peer1-xe1-0-0.telehouse.ukcore.bt.net [109.159.254.98]
10 14 ms 14 ms 14 ms xe-2-3-0-0.ldn1nqp1.uk.ip.tdc.net [195.66.236.64]
11 29 ms 29 ms 29 ms ae-1.boanqp7.dk.ip.tdc.net [83.88.23.199]
12 31 ms 31 ms 31 ms cpe.ge-1-1-0-257.boanxj1.customer.tele.dk [62.243.244.238]
13 31 ms 31 ms 31 ms klyden.foppa.dk [89.104.194.146]

Trace complete.

C:\Windows\system32>ping qw.foppa.dk

Pinging qw.foppa.dk [89.104.194.146] with 32 bytes of data:
Reply from 89.104.194.146: bytes=32 time=31ms TTL=52
Reply from 89.104.194.146: bytes=32 time=31ms TTL=52
Reply from 89.104.194.146: bytes=32 time=31ms TTL=52
Reply from 89.104.194.146: bytes=32 time=31ms TTL=52

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

Internal wiring got sorted eventually and now it appears that there may be another problem with either the phone side cabling to the NTE5 or the service-specific faceplate

Now they have ceased PSTN in error (confirmed this was not supposed to happen) and this has caused my BE line to be suspended

Should be interesting as the person I spoke to in the Fibre Home Phone trial team said there was no process in place for this scenario and therefore likely a manual process

I am in total despair at the moment and wish I'd never agreed to take part in the trial

Edited by nredwood (Fri 29-Jun-12 00:55:06)

Syuper !

C:\Documents and Settings\Owner>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BeBox [192.168.1.254]
2 2 ms 2 ms 2 ms 217.32.145.230
3 2 ms 2 ms 2 ms 217.32.145.254
4 7 ms 6 ms 6 ms 213.120.181.158
5 7 ms 7 ms 6 ms 217.41.169.211
6 7 ms 6 ms 6 ms 217.41.169.109
7 6 ms 6 ms 6 ms acc2-10GigE-10-3-0.sf.21cn-ipp.bt.net [109.159.251.225]
8 25 ms 21 ms 24 ms core1-te-0-0-0-14.ilford.ukcore.bt.net [109.159.251.161]
9 15 ms 15 ms 15 ms peer2-xe10-0-0.telehouse.ukcore.bt.net [109.159.254.128]
10 15 ms 17 ms 15 ms 194.74.65.42
11 * * * Request timed out.
12 14 ms 17 ms 13 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 19 ms 18 ms 17 ms 132.185.255.60
14 16 ms * 15 ms 212.58.241.131

Trace complete.

C:\Documents and Settings\Owner>tracert qw.foppa.dk

Tracing route to qw.foppa.dk [89.104.194.146]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BeBox [192.168.1.254]
2 2 ms 2 ms 2 ms 217.32.145.230
3 2 ms 2 ms 2 ms 217.32.146.14
4 6 ms 6 ms 6 ms 213.120.181.158
5 7 ms 6 ms 6 ms 217.41.169.211
6 7 ms 6 ms 6 ms 217.41.169.109
7 6 ms 6 ms 6 ms acc2-10GigE-1-3-0.sf.21cn-ipp.bt.net [109.159.251.214]
8 18 ms 19 ms 19 ms core2-te0-2-4-0.ealing.ukcore.bt.net [109.159.251.143]
9 30 ms 14 ms 17 ms peer1-xe3-3-1.telehouse.ukcore.bt.net [109.159.254.211]
10 14 ms 14 ms 14 ms xe-2-3-0-0.ldn1nqp1.uk.ip.tdc.net [195.66.236.64]
11 31 ms 31 ms 31 ms ae-0.boanqp7.dk.ip.tdc.net [83.88.23.196]
12 31 ms 32 ms 32 ms cpe.ge-1-1-0-257.boanxj1.customer.tele.dk [62.243.244.238]
13 32 ms 32 ms 31 ms klyden.foppa.dk [89.104.194.146]

Trace complete.

Phone now working on fibre via the service specific faceplate - wired incorrectly again!

The engineer was the same who did the external part of the install

Still no news on what is happening with the BE line though

Thanks!

Looks like you're being routed through sheffield too... Brilliant first hop latency, then it all goes wrong.

What are they doing!

In reply to a post by driz:

Thanks!

Looks like you're being routed through sheffield too... Brilliant first hop latency, then it all goes wrong.

What are they doing!

BT route a lot of people via some really lol worthy routing - I'm also routed via Sheffield despite being almost as South in the UK as you can get and relatively close to London... ~300miles of unnecessary routing and all the issues that brings (exposes my connection to issues all over the country).

Was hoping it would be fixed when we get FTTC soonish but guess it won't be the case

Before they stripped the names off some of the hops (which I'm sure wasn't an accident) I spotted days when I was routed via several major cities along the way including one crazy day where it went something like South Somerset->Birmingham->Cardiff->Sheffield->Milton Keynes->Illford.

Edited by deleted (Mon 02-Jul-12 20:48:54)