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