Just performed a wanton reboot of my Modem/Router.

The modem/router which I use for my LAN is a Bell Hub 3000, which I still hold to be a good modem. But lately, I discovered a slight glitch in the way it works. I have given it numerous specialized settings, such as, for example, a “Reserved IP Address” for my new Chromebook.

The problem I ran in to was, that the modem was executing all my settings without the slightest flaw, but was failing to commit changes to certain settings to non-volatile memory. Apparently, the way the modem is organized internally is, that it has volatile as well as non-volatile memory, which mimic the RAM and the Storage of other, modern devices.

In certain cases, even a full-blown PC could be running some version of an operating system, in which a user-initiated change is accepted and enacted, but only saved to non-volatile storage, when the user logs out successfully.

Well, earlier this evening I had a power failure, after which the modem restarted, but restarted with settings, that predated the most recent settings which I had given it. This was its only offence.

Now, I could go through the ritual of changing all my special settings again, after every power failure, but in reality, that would not do. And so, what I did was to soft-boot the modem, which, just like that poorly programmed desktop manager would, saved all my settings to non-volatile memory. After the reboot, those settings have stuck.

But what it also means is twofold:

  1. This blog went down again, from 20h15 until 20h25, in other words, for an extra 10 minutes.
  2. And, if there are any readers who examine the IP address log in the side-bar of my blog, they will notice an additional IP address change, simply due to the modem reboot. This will be, between 20h10 and 21h10. This one was not due to any malfunction, but was deliberately triggered by my action.

The process was short but painful, and had to be done. :-)

Dirk

 

My Experiences with the Bell Home Hub 3000

My ISP is Bell Canada, and my LAN connects to a service of theirs called ‘Fibe 50′, which stands for a 50 Mbps, DSL connection, to a Local Node, which in turn is connected to Bell via Fibre Optics. And this connection of my LAN is accomplished through a Home Hub 3000 Modem / Router.

The fact that I use my home PC as my Web-server, also means that a stable Internet connection is especially important to me, even though officially, I’m just a Home User. Just recently, my site experienced some down-time, due to problems with my DSL. And I’d like to weigh in on how good or bad the Home Hub 3000 might be, based on personal experiences.

First off, this Modem / Router once had a very bad reputation, when it was first released for public use, in the year 2016. But because that release of the modem preceded my personal range of experiences, I’m going to ignore this piece of History for the moment. It could very well be that in the year 2016 the modem was not ready to be released yet, but that in the year 2019, it is. This would be one example, where the service provider did their best to patch the behaviour of the modem, with many firmware updates, but without any actual modifications to the circuitry being possible.

Continue reading My Experiences with the Bell Home Hub 3000