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 – experiment.co.uk (except it isn’t that one, obv).
But it doesn’t, clearly, traffic is being routed to experiment.co.uk/login.lp
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.
It may actually be working, are you testing from somewhere outside your home network? Testing from inside may well not trigger the translation.
PS – Openreach delay is almost certainly down to civils issue of some sort – problems getting power to the cabinet or a blockage in the duct (normally caused by tree roots) stopping the blown fibre being deployed to it. It’s not some pre-ordaned scheme to keep you on standard ADSL, honest!
I had tried from external points (have a very reasonable high-speed mobile signal here). It’s an interesting conundrum, but not, as I’ve said, one I’m going to spend too long trying to crack. I’ll file it until I have time – and by the time I have time (IYSWIM), I hope to be on FTC
Tip: Look at your postcode on roadworks.org and see what street openings are coming up around the cabinet or on the route to it from the exchange. That will be the source of the delay…
Thank you for that, Daniel, that’s very handy. Unfortunately the only thing it shows is that Centrica will be doing some work to the gas main in a couple of weeks. I half wonder if the fibre has been blown through, but not enabled at the cabinet. Don’t ask me why, I just do.
🙂