More trouble with the home network today. We had a smart electricity meter installed a few days ago. Though without the “smart” part, because they couldn’t get a good enough signal down in our basement. You’d think they’d have considered that possibility in designing them, since that’s the kind of place where a lot of people’s meters are. Anyway, I think it was interfering with our powerline connection.
We have a BT HomeHub as our main router and connection out to the fibre. But the wifi was a bit crap up at the top of house. So about a year back I got a couple of powerline connectors and used them to extend the 5GHz network upstairs, using another router that we had accidentally acquired as the other access point.
It worked fine, until just the other day. The first symptom was that the Sonos app couldn’t connect to the speaker. I did some diagnosis, and everything was just weird. We could mostly connect to the outside world without any trouble, but I couldn’t connect to the HomeHub’s web interface by name. Nor, I think, by IP address. And then in one of my experiments I tried a slightly different IP address (one that shouldn’t have existed on our network), and I found myself at… a Sky box.
Now you know my dislike for that bunch. There’s no way I’d let their networking hardware on my LAN, any more than I’d subscribe to their channels. and in any case, just, what?
I wondered if our network could somehow have got crossed with one of the neighbours’. But it seemed so improbable. The neighbouring network would need to be using the same SSID, at the very least.
As you’d imagine, I started taking components out to try to isolate the problem. With just the BT HomeHub in place, things were back to normal. But as soon as I began adding parts, everything went weird.
Eventually I concluded — guessed, really — that the smart meter might be using powerline itself. We’re supposed to get a screen-based device for monitoring usage, and maybe that communicates with the meter over powerline. And the meter could have an embedded sky router? That seems unlikely, but maybe Sky have the contract to do the phoning home for EDF.
Anyway, since the root of the problem seemed to be at least partly to do with IP address conflicts, I decided to factory-reset everything and rebuild with a different IP address range (I’ve never used
172.16.0.0 before). Along with a new wifi SSID and password.
And so far so good. But I’m having trouble getting the second router to route properly via the first, so upstairs is going to be problematic till I can solve that.
All this is doing, of course, is making me wish that we could get Eeros in the UK. A self-configuring mesh network is exactly what we need, and not all this jerry-rigged nonsense.
I didn’t write a post tonight because I spent most of the evening struggling with wifi configuration. And the less said about that, the better.
When the original Unix designers (or, as it turns out, Mike Muuss) chose
ping as the name for the command for checking the status of a network host, it was a moment of inspired genius. The word is almost onomatopoeic in its appropriateness.
But nowadays people are pinging each other all over the place: emails, IMs, even phone calls are “pinged” at each other. “I’ll ping you an email,” they say.
The purist in me cringes a little each time I hear it. But it shouldn’t. The word that was so apposite for those early savants is just as suitable today: it communicates a needed concept. And English, of course, is a living, thriving language. So let people get on with it
Just don’t expect me to use it myself.