On Fri, Oct 05, 2012 at 11:43:50AM +0100, Laurie Brown wrote:
On 05/10/2012 11:24, Chris Green wrote:
On Thu, Oct 04, 2012 at 08:38:10PM +0100, Keith Edmunds wrote:
On Thu, 4 Oct 2012 10:44:57 +0100, cl@isbd.net said:
I don't want it to provide any sort of access from outside, I just want to be able to reverse tunnel down the connection to access port 80 on the system on the boat.
[SNIP]
I'm still confused; not so much as to what you're trying to do as to why.
Why are you trying to initiate all this from the boat, and especially via intermediaries? Why don't you secure the boat end, and connect directly to it?
Because it's totally inaccessible from the internet, it's behind a NAT firewall in the WiFi server (which isn't mine and to which I have no access).
Alternatively, using shorewall and OpenVPN, why not make a permanent tunnel between the boay and your intermediate host, secured on said host with regard to onward access, only opening up access to your home system as and when required.
Where do I install OpenVPN? The boat system certainly hasn't the space or processor power to do it and anyway isn't accessible from the internet. I doubt if I can install OpenVPN on my hosting service though it *might* be possible, I'll investigate that route.
For me, I'd secure the boat end, and go directly to it, but there must be a reason you haven't done that, because it's so obviously the simplest solution.
Re: my previous post: links, btw, is a "A fast and lightweight [CLI] web browser running in both graphics and text mode" which is far, far more capable than lynx (http://links.twibright.com/)
Yes, I've been using w3m actually as it's more capable of dealing with the quirks of router web GUIs, but even then one nearly always needs a GUI browser to configure a router.