connection – James Batchelor

My FTTP Journey

Unexpectedly and to much excitement, my home internet is now provided via FTTP.

For background, I was previously in a FTTC environment getting average speeds due to my distance from the cab, however good enough to assumably be overlooked for the next phase of the Openreach Ultrafast rollout. Not that I’m complaining, 2020 is the year my speed gets a much-needed boost.

2020 also turns out to be the inaugural international work from home year, so had the opportunity to have a front seat view from my home office on the activity and timeline that brought FTTP home.

I’d like to share my observations and timeline as an example of what you can expect should you get the inkling of fibre coming to your street soon.

Before we get started, as my expectations rose, I found this post by Andy’s World invaluable for identifying activity and helping me confirm that FTTP was on its way.

Testing Draytek WAN2 Throughput

In a series of events that I thought wouldn’t have happened for many years, FTTP (Fibre To The Premises) has just become available to my home. With available speeds of 1000/330Mbps available the temptation is to go for the maximum, but will my current infrastructure actually deliver what’s on offer?

My current router is a Draytek 2862ac, which has an advertised 400Mbps throughput at the WAN, but what can it actually achieve in the real world? This will be the basis on choosing a FTTP speed profile.

Speed testing a router can be setup with a couple of laptops…

Net killing RPi – Getting Somewhere…

In my last post I was a confussled mess, failing to get my head around how a network device (The Raspberry Pi) could cripple an exclusive function of my router.

I decided to troubleshoot the issue further, I set up a basic ping to help me pinpoint when the internet was going down

After performing some basic troubleshooting, it transpired that the fault was happening whenever the HDMI cable was connected to the Pi and my Television (Sony Bravia EX4-32).

Ping results after HDMI cable connected.

Thinking it was a bad HDMI cable, I bought another, but to no avail. My next brainwave was that the Pi was emitting EMI (or RFI) which drove me to buy a 10 metre HDMI cable to get the Pi as far away from my router and other networking equipment, alas this didn’t work either.

Troubleshooting further, it turned out that the HDMI cable didn’t need to be properly connected, mealy touching the Pi on any metallic part will cause the internet to cease.

So in essence I am still no closer to solving my Pi/Internet mystery, if you can help me please comment!

All other HDMI works fine as I am now using the 10m HDMI cable as a screen extender on my laptop.

Bootnote:

In my previous post I signed off by stating that that the Pi and my internet were working in harmony. However it turned out that my modem had dialled back my downstream internet speed to 1.5Mbps instead of the usual 3Mbps, normally a result of the modem trying to obtain a more stable internet connection due to, lets say, interference on the line!