Moving an ONT, EE no longer provide the service?

[TMaskell]

Hi

I would like to relocate my ONT to a different part of the house. I've invested heavily in some new Unifi Equipment and want to store it in a rack in a completely different part of the house as to where my old all in one smart hub was. I phoned up at the beginning of summer and was told there was a minimum fee of £150 and to phone back when I needed the work done. 

I phoned back today to be told that it is no longer a service that is provided by EE/Openreach and their advise was to find an electrician who could move it for me? 

Now I'm happy to go down this route (if I can find anyone skilled/willing) but I was always under the impression everything up to and including the mastersocket/ONT was Open reaches property and should only be touched by them?

Has anyone had experience of this?

To clarify running a CAT7+ ethernet lead from the old location to the new rack would be completely impractical, moving the ONT is the most logical solution.

Tom

[Chris_B]

@TMaskell  You don’t want an electrician you need a network engineer.    Anyone can move a network point the only thing that can not be done is a new line from the telegraph pole to your home and for that you need open reach. 

[Mustrum]

@TMaskell  not quite sure what you mean - would the fibre need to be extended along the same path as the Cat cable, or are you looking for it to enter the building at a new point?

Either way, an electrician is unlikely to be able to splice fibre, and if someone other than Openreach were to try you would be liable for the charge to fix any issues.

Were it me I would try another CS rep, it may be the last one you spoke did not know how to arrange this, you may get one who does know if you try again.

[TMaskell]

Hi

Just spoken to another CS advisor. Not sure if the news is better or worse. Apparently the previous information was incorrect as suspected.... No one should touch BT's cabling... Shock! 

They also said there is no way to request the move of an ONT/Master socket unless it's in an unsuitable location such as a bathroom. So apparently I'm stuck! 

What's even more frustrating was that the CS advisor I spoke to at the start of summer said it was a straightforward job and had a standard charge of £150, which I was happy to pay?!

So who knows!

[XRaySpeX]

The ONT does not need to be on the same wall as the outside box. It can be moved (by OR) by extending its fibre connection but that's not a job for an electrician.

[pip11]

If running an ethernet lead is impractical, how is running a fibre cable any better?

[mikeliuk]

Hi @TMaskell ,

If your latency requirements are not too demanding, have you considered a powerline adapter link between your server room and the ONT? This may add between 12 ms to 25 ms latency to the network path where the endpoints do not have WiFi functionality. For the powerline adapter I have with in-built WiFi AP, I find a higher latency of around 40 ms.

Below I show the ping first to a Devolo device in the server room, and then to a plain Devolo power line adapter with no WiFi functionality, and lastly to a Devolo powerline adapter with WiFi AP. The middle device has latency typically around 12 ms to 25 ms so the below is unusually good. The last two tests are between ring mains so if your hardware is on the same floor, your numbers may be better. You will see from the below, that there is a certain amount of jitter with power-saving mode enabled. It may be the same or a little better with power-saving disabled.

Depending on the network configuration of the ONT, you may need to isolate the PTP link from any other powerline network. In my case, I have a disconnected ONT (as I am with EE instead) downstairs which I believe I can just use a /30 or /31 to create a PTP link.

[x@x ~]$ for i in 192.168.4.{57,64,50}; do echo "= = = $i = = = "; ping -c 16 $i; done
= = = 192.168.4.57 = = = 
PING 192.168.4.57 (192.168.4.57) 56(84) bytes of data.
64 bytes from 192.168.4.57: icmp_seq=1 ttl=58 time=1.02 ms
64 bytes from 192.168.4.57: icmp_seq=2 ttl=58 time=1.06 ms
64 bytes from 192.168.4.57: icmp_seq=3 ttl=58 time=1.05 ms
64 bytes from 192.168.4.57: icmp_seq=4 ttl=58 time=1.04 ms
64 bytes from 192.168.4.57: icmp_seq=5 ttl=58 time=1.06 ms
64 bytes from 192.168.4.57: icmp_seq=6 ttl=58 time=1.87 ms
64 bytes from 192.168.4.57: icmp_seq=7 ttl=58 time=1.05 ms
64 bytes from 192.168.4.57: icmp_seq=8 ttl=58 time=0.943 ms
64 bytes from 192.168.4.57: icmp_seq=9 ttl=58 time=0.991 ms
64 bytes from 192.168.4.57: icmp_seq=10 ttl=58 time=0.984 ms
64 bytes from 192.168.4.57: icmp_seq=11 ttl=58 time=1.09 ms
64 bytes from 192.168.4.57: icmp_seq=12 ttl=58 time=0.981 ms
64 bytes from 192.168.4.57: icmp_seq=13 ttl=58 time=1.01 ms
64 bytes from 192.168.4.57: icmp_seq=14 ttl=58 time=1.12 ms
64 bytes from 192.168.4.57: icmp_seq=15 ttl=58 time=0.982 ms
64 bytes from 192.168.4.57: icmp_seq=16 ttl=58 time=1.07 ms

--- 192.168.4.57 ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 32ms
rtt min/avg/max/mdev = 0.943/1.081/1.868/0.210 ms
= = = 192.168.4.64 = = = 
PING 192.168.4.64 (192.168.4.64) 56(84) bytes of data.
64 bytes from 192.168.4.64: icmp_seq=1 ttl=58 time=24.9 ms
64 bytes from 192.168.4.64: icmp_seq=2 ttl=58 time=24.4 ms
64 bytes from 192.168.4.64: icmp_seq=3 ttl=58 time=2.77 ms
64 bytes from 192.168.4.64: icmp_seq=4 ttl=58 time=2.11 ms
64 bytes from 192.168.4.64: icmp_seq=5 ttl=58 time=2.15 ms
64 bytes from 192.168.4.64: icmp_seq=6 ttl=58 time=2.03 ms
64 bytes from 192.168.4.64: icmp_seq=7 ttl=58 time=4.48 ms
64 bytes from 192.168.4.64: icmp_seq=8 ttl=58 time=3.97 ms
64 bytes from 192.168.4.64: icmp_seq=9 ttl=58 time=3.94 ms
64 bytes from 192.168.4.64: icmp_seq=10 ttl=58 time=3.44 ms
64 bytes from 192.168.4.64: icmp_seq=11 ttl=58 time=1.90 ms
64 bytes from 192.168.4.64: icmp_seq=12 ttl=58 time=1.94 ms
64 bytes from 192.168.4.64: icmp_seq=13 ttl=58 time=3.18 ms
64 bytes from 192.168.4.64: icmp_seq=14 ttl=58 time=3.76 ms
64 bytes from 192.168.4.64: icmp_seq=15 ttl=58 time=2.04 ms
64 bytes from 192.168.4.64: icmp_seq=16 ttl=58 time=2.07 ms

--- 192.168.4.64 ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 35ms
rtt min/avg/max/mdev = 1.902/5.564/24.891/7.256 ms
= = = 192.168.4.50 = = = 
PING 192.168.4.50 (192.168.4.50) 56(84) bytes of data.
64 bytes from 192.168.4.50: icmp_seq=1 ttl=62 time=6.95 ms
64 bytes from 192.168.4.50: icmp_seq=2 ttl=62 time=5.36 ms
64 bytes from 192.168.4.50: icmp_seq=3 ttl=62 time=4.36 ms
64 bytes from 192.168.4.50: icmp_seq=4 ttl=62 time=3.52 ms
64 bytes from 192.168.4.50: icmp_seq=5 ttl=62 time=3.20 ms
64 bytes from 192.168.4.50: icmp_seq=6 ttl=62 time=2.17 ms
64 bytes from 192.168.4.50: icmp_seq=7 ttl=62 time=40.0 ms
64 bytes from 192.168.4.50: icmp_seq=8 ttl=62 time=79.4 ms
64 bytes from 192.168.4.50: icmp_seq=9 ttl=62 time=40.5 ms
64 bytes from 192.168.4.50: icmp_seq=10 ttl=62 time=39.8 ms
64 bytes from 192.168.4.50: icmp_seq=11 ttl=62 time=38.9 ms
64 bytes from 192.168.4.50: icmp_seq=12 ttl=62 time=37.6 ms
64 bytes from 192.168.4.50: icmp_seq=13 ttl=62 time=35.3 ms
64 bytes from 192.168.4.50: icmp_seq=14 ttl=62 time=34.0 ms
64 bytes from 192.168.4.50: icmp_seq=15 ttl=62 time=33.8 ms
64 bytes from 192.168.4.50: icmp_seq=16 ttl=62 time=32.2 ms

--- 192.168.4.50 ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 34ms
rtt min/avg/max/mdev = 2.170/27.312/79.378/20.643 ms

[TMaskell]

Running the Ethernet internally impractical from the current ONT to the new location. Externally/ via the loft is a very easy run for an open reach engineer.

[TMaskell]

Hi, 

Unfortunately I've tried this option and it's not great. The living room and the cupboard are on separate rings. I know they say this shouldn't affect performance but it seems to... Drops from about 74mbps to 50mbps.

[TMaskell]

I think the outside box would need moving too as I would now like the service to enter the house into the first floor nor the ground floor.