any sources to support that fact?

In reply to a post by ionic:

any sources to support that fact?

Wouldn't it be nice if I were to provide a link to a BT Group / Openreach specification document . . . unfortunately that is not possible.

Now I shall invert your question and send it back to you. Any sources to deny that fact? (E.g. photographs that you have taken of the duct mouths from within the FTTC cabinet at install / commission time / etc.)

Edited by burakkucat (Thu 23-Feb-12 16:56:47)

He is being pedantic.

The compound is firestopping and can be easily drilled out. You will notice that Zarjaz didn't even bother to reply to this and he must know exactly what goes in. Why argue when someone knows what he knows even when he doesn't!

Ducts, holes, tunnels all have this done regularly it is merely to protect the end site and is not permanant in any way.

I recently received a brochure through the post from hyperoptic and from all accounts my building is up for it however there are some who want to consider Openreach. From my limited research, I understand they use different technologies GPON vs Point to Point. Does anyone have a view which is better?

All help will be appreciated.

G

We either use a pressurised bag at end user premises (grey - never used myself) - a rubber / foam bung at residential premise / base of pole when outside, and at cabinet a resin which is injected into only 3-5 inches of the duct (stuff a rag or blue roll to block duct first) - to stop gas / water etc - it is easily punctured with a screwdriver and then pulled out by hand. No civils required - and you can fit many hundred pair cables into the size of duct fitted to cabs (which usually have one entry per 100 eu's anyway). The ducts are otherwise unblocked (aside from exchange) unless there is a complaint / high risk of flooding from water running down ducts from the network into a lower property. But again - its always a 5min job to unblock, then 5 min re-seal after new cable works. Believe it or not we know what we are doing
-OE

In reply to a post by G4M3B0Y85:

I recently received a brochure through the post from hyperoptic and from all accounts my building is up for it however there are some who want to consider Openreach. From my limited research, I understand they use different technologies GPON vs Point to Point. Does anyone have a view which is better?

All help will be appreciated.

G

The first bit of advice would be to put this in a topic all of its own - it really doesn't belong here - particularly as the conversation here has long gone off topic.

In reply to a post by driz:

If you have a spare moment, I'd love a tracert to:

qw.foppa.dk

And if you have a second spare moment, to:

mattlantis.net

Otherwise, very very nice service you've got there.

Sorry, have been a bit busy. Here are the results:

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

1 <1 ms <1 ms <1 ms hyperhub.hyperlan [192.168.1.1]
2 3 ms 7 ms 3 ms 141.0.146.4.bcube.co.uk [141.0.146.4]
3 2 ms 2 ms 2 ms 172.16.16.13
4 3 ms 2 ms 2 ms 172.16.16.9
5 2 ms 1 ms 2 ms 94.31.34.41
6 3 ms 2 ms 2 ms xe-1-3-0.mpr1.lhr1.uk.above.net [64.125.28.201]
7 2 ms 2 ms 2 ms xe-7-1-0-0.ldn4nqp1.uk.ip.tdc.net [195.66.224.64]
8 17 ms 58 ms 17 ms ae-1.boanqp7.dk.ip.tdc.net [83.88.23.199]
9 17 ms 17 ms 17 ms cpe.ge-1-1-0-257.boanxj1.customer.tele.dk [62.243.244.238]
10 17 ms 17 ms 17 ms klyden.foppa.dk [89.104.194.146]
Trace complete.


Tracing route to mattlantis.net [109.74.195.224]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms hyperhub.hyperlan [192.168.1.1]
2 3 ms 3 ms 4 ms 141.0.146.4.bcube.co.uk [141.0.146.4]
3 2 ms 2 ms 2 ms 172.16.16.13
4 2 ms 2 ms 2 ms 172.16.16.9
5 2 ms * 2 ms linx.telecityredbus.net [195.66.224.82]
6 * 2 ms * 217.20.44.193
7 3 ms 2 ms 2 ms te4-1-dist65-01.lon10.telecity.net [217.20.44.218]
8 3 ms 2 ms 2 ms 212.111.33.234
9 3 ms 2 ms 3 ms mattlantis.net [109.74.195.224]
Trace complete.

Why are there 3 readings given for each hop?

Good thinking. Cheers for the advice.

Thank you very much for this - nice to see the first hop is around 2ms! The few BT FTTH traceroutes I've seen have the first hop at around 4-6ms, which is a bit [censored] for fibre really. But very very nice stuff there - 17ms to Denmark is phenomenal.

There's 3 readings to give you an idea of average I suppose, since latency can vary a bit from moment to moment.

FWIW, here are my Be traceroutes - fastpath in SW London. These are very good for ADSL.

Tracing route to mattlantis.net [109.74.195.224]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms the.internet [192.168.254.1]
2 8 ms 7 ms 6 ms 87-194-48-1.bethere.co.uk [87.194.48.1]
3 * * 6 ms 10.1.2.218
4 6 ms * 6 ms linx1.telecityredbus.net [195.66.226.82]
5 36 ms * * 85.90.226.205
6 62 ms 64 ms 64 ms te4-1-dist65-01.lon10.telecity.net [217.20.44.218]
7 8 ms 6 ms 6 ms 212.111.33.234
8 6 ms 6 ms 6 ms mattlantis.net [109.74.195.224]

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

1 <1 ms <1 ms <1 ms the.internet [192.168.254.1]
2 7 ms 6 ms 5 ms 87-194-48-1.bethere.co.uk [87.194.48.1]
3 * * * Request timed out.
4 5 ms 5 ms 5 ms 208.178.245.81
5 33 ms 35 ms 33 ms NIANET-A-S.TenGigabitEthernet2-3.ar3.CPH1.gblx.net [64.214.146.182]
6 23 ms 23 ms 22 ms ge5-2-taar.ip.comendo.com [93.176.69.54]
7 22 ms 23 ms 22 ms ge5-2-taar.ip.comendo.com [93.176.69.54]
8 22 ms 23 ms 22 ms crb11.hosting.comendo.com [89.104.192.66]
9 24 ms 22 ms 22 ms klyden.foppa.dk [89.104.194.146]

Thanks - a very interesting comparison!