On Mon, Dec 13, 2010 at 09:44:03PM +0000, steve-ALUG@hst.me.uk wrote:
On 11/12/10 09:32, Chris G wrote:
Does anyone have any experience of using any of these services, any recommendations?
I've used dyndns and no-ip.com before and both OK. no-ip.com used to regularly bug me with an email saying that as my configuration had not been updated in ages, unless I clicked the link on the email, my no-ip account would be closed. AFAIK the client was running perfectly well all the time, just that there were no changes of IP address. In the end, I coughed up for a subscription.
OK, thanks for all the advice - I think my problem is now lack of ability of the 3-G connection to allow incoming connections.
Is this because the router is unable to allow incoming connections, or that you just haven't set up port forwarding. I noticed you other posts about vpns etc. Previously, I've just set up port forwarding on the router to a specific machine. That machine's running a ssh server.
It's because there's effectively (as I understand it) a NAT router/firewall operated by the telephone company between my 3-G connection and the 'real' internet. The 3-G router on the boat has, as its WAN address, an RFC1918 'private' address, there is then the telecom provider's router (or whatever it may be) between that address and the public internet. Thus, even though I have port mapped *my* router connections from outside don't work because the telecom provider's 'router' doesn't map them to my router.
I've then tunnelled the ports I'm interested in over the ssh link, and bob's your uncle.
Not sure, but I think this may be easier to configure than a VPN. Depends why you want to talk to this machine?
Yes, it could well be easier, I've done it before and once you've got your mind round the ssh parameters it's easy enough. The difficulty though is how to make it restart automatically if the connection dies (which I guarantee it will at intervals). I get the feeling that a VPN may have ready made tools for keeping itself alive.