Blogathon 21/15 – humping

I have spent a large proportion of this morning humping.

My friend, the venerable Mr Rudder, has been helping me rack up servers.

We had a problem with the fixing screws for the front of the rails.

The problem being that the screws were fractionally too large for the fixing holes.

But a visit to B&Q sorted that.

And as a result, there are now two HP DL380 servers racked up and partially cabled.


All we need now is BT Openreach to sort itself out and get the bloody line connected.

As soon as that’s done, I can begin installing CentOS and building VMs.

Just stuff…

Very interesting day today in Westminster, with the London office of the people I’m currently working for.

Learned loads, and made progress on a big technical project.

Looks like I have to go down to the Cheltenham HQ for a few days, which would be a pain in the backside, and would mean having to stay down there, because commuting isn’t going to happen.

The trouble is, when one is dealing with complex information systems, there are a lot of pre-requisites that need to get lined up before the actual project delivery can commence.

And oh boy, am I dealing with a lot of pre-requisites.

On a broadly similar topic, I’ve been continuing to look at IP-related activity. I’ve switched from port-monitoring to IP-monitoring.

Speaking of travel, I have a potential short, sharp visit to make down south, which, despite the distance and the dodgy weather, I’m actually looking forward to. Maybe this weekend, if things pan out.


I got outbid on a bike on eBay last night. I am more disappointed than I thought.

But there’s another one…

And I’m viewing two houses tomorrow evening.

It’s all go, eh?

Any port (forwarding) in a storm

Here’s a frustrating little niggle.

I’m having to use a downgraded router (due to not having FTC, as previously moaned about).

To allow internet traffic to access any of the servers running on my LAN, I have to configure port forwarding on the above mentioned router.

In my last (FTC) house, I configured port forwarding through a nifty little utility that is installed on my NAS.

I don’t want to faff (technical word, there) with using the same utility to configure port forwarding, because the law of sod clearly dictates that whatever I do now, it will over-write port forwarding rules that I have previously configured for my FTC router.

And I don’t want to do that, because if Openreach (hey, I did say *if*) stick to their updated delivery, and have FTC installed here, by the middle of the month, then I plan on switching over to the previously configured router and hey presto, Robert’s your mother’s brother!

So I’ve had a bash at manually configuring port forwarding the Plusnet Technicolor (sic) Gateway.

And hit a wall.

No matter how much time I spend in the config menu/sub-menus, no matter which changes I make (then unmake, obv), I can’t get port forwarding fully enabled/configured.

Everytime I think I’ve done it correctly, I put the uri in the browser and…


I have no idea how to bypass this – the IP traffic should go straight to the domain I’m using as a test-site for all this experimenting – (except it isn’t that one, obv).

But it doesn’t, clearly, traffic is being routed to

I don’t want to spend too much time on it.

If the word of Openreach is good (sceptical face) I’m only going to have to endure the current setup for two more weeks.

But how frustrating, to get so near, and yet, so far.

Moving the second (part VI)

This is odd.

I have pointed a domain name registered with 123-reg to my NAS. I have done the usual stuff (created a MySQL database, created a database for it, installed the .php front end, put the database user details in the php.config file) and…

It all works.


And that’s a tricky ish.

When I go to (not the real name, obv), everything is peachy.

Through that URI I have access to the content and, using the correct address, also have access to the .php admin panel and the phpMyAdmin MySQL control panel.


But when I try and give the URI a very minor modification (such as changing the address to, the internet call is routed to the NAS control panel (


I’m too tired to get my head around it tonight.

But yeah.


Moving the second (part V)

It’s taken 24 hours, but I have finally learned how to migrate a self-hosted website from 123-Reg to my NAS.

It was more fiddly than the migration from GoDaddy last week, and the logic behind the way the core IP address and @ and A and nameservers hang together is very… individual.

But it’s there and the prototype website is up and running.

I’m off to bed now, to celebrate this success with a long line of Zs falling out of my mouth.

See ya tomoz.