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

 

Power Failure, Downtime

I take the unusual approach of hosting my site and this blog, on a PC at home, which acts as my Web server. I don’t recommend that everybody do it this way. This is only how I do it.

This has as side effect that the availability of this site is only as good, as the reliability of my PC, as well as that of my internet connection.

Today my neighbourhood experienced a power failure from 14h25 until 17h55, and, this site remained offline until about 18h55.

I apologize for any inconvenience to my readers.

Dirk

 

Power Failure Today, Downtime

I take the somewhat unusual approach of Hosting my Web-site and blog, on a PC at home. I’m not saying that this is what everybody should do; this is just how I do it. Unfortunately this means that the visibility of this blog is only as good as the reliability of the PC in question, and of my Internet connection.

Today, the city I live in experienced violent wind-gusts, which I’d estimate had wind-speeds of over 100 km/H. This caused a power failure around 9h00 this morning. And, even though that power failure only seemed to last about 15 minutes, I did not reboot my computers immediately, because of the possibility of yet another power failure. The winds continued to gust this way until about 17h00 today.

As a result, this site and blog were down from about 9h00 until about 17h50.

I apologize for any inconvenience to my readers.

Dirk

 

Power Failure Today, Downtime

I take the unusual approach, of Hosting this site and this blog, on a PC at home. I don’t say that other people should do this. This is only what I do.

This implies that the visibility of this blog is only as reliable, as the operation of my PC here at home.

Today we had a power failure, from approximately 16h15 until 17h35. As a result, this blog was also offline, until about 18h00.

I apologize for any inconvenience to my readers.

Dirk