On Sat, 11 Dec 2010 09:37:06 +0000 Chris G cl@isbd.net allegedly wrote:
So I don't seem to be able to make connections *to* my eeePc that's sitting connected to a 3-G router, so the alternative is to get it to connect 'outwards' using ssh and to tunnel through that ssh connection from outside to enable me to connect to the eeePc and do anything necessary remotely.
I really only need command line access. Are there any alternative ways of doing this or is ssh port-mapping the best way to do it?
The other issue is somehow to restart the connection if/when it goes down (which it does fairly frequently, this is a somewhat flakey area for 3-G) - any clever ideas?
The router is probably doing NAT so of course you can't connect in from the outside (and you probably have RFC 1918 addresses internally anyway).
So, assuming the router offers the options, you need to do one of two things:
- set up a port forwarding rule (or rules) to allow the requisite connection inbound; or more risky - put the EE on a DMZ so that /any/ inbound traffic can reach it.
The router configuration interface will probably call these options "applications and gaming" or something similar.
Mick
---------------------------------------------------------------------
The text file for RFC 854 contains exactly 854 lines. Do you think there is any cosmic significance in this?
Douglas E Comer - Internetworking with TCP/IP Volume 1
http://www.ietf.org/rfc/rfc854.txt ---------------------------------------------------------------------