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?
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 ---------------------------------------------------------------------
On Sat, Dec 11, 2010 at 02:44:35PM +0000, mick wrote:
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).
That's not the problem, I know how to get inward connections through a router that does NAT.
The problem is that the 3-G internet connection doesn't allow inward connections.
Set up a VPN server on ur home machine and install the client on your eeePC. As long as you have it set to auto reconnect when there is a drop then your eeePC will dial in anytime it has connectivity.
--James. (This email was sent from a mobile device, this is not secure)
On 11 Dec 09:37, Chris G 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?
*if* you've got a vm/permanently connected machine/server somewhere (I'd guess you have otherwise where would you terminate the ssh connection...) then I'd suggest using vpn software like OpenVPN instead to that box. Then you're not limited to just the ssh port.
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?
Surely that should just be handled by the 3G router? ;)
On Sat, Dec 11, 2010 at 03:06:07PM +0000, Brett Parker wrote:
On 11 Dec 09:37, Chris G 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?
*if* you've got a vm/permanently connected machine/server somewhere (I'd guess you have otherwise where would you terminate the ssh connection...) then I'd suggest using vpn software like OpenVPN instead to that box. Then you're not limited to just the ssh port.
OK, I'll take a look, I hope it's not too big, the eeePC is getting a bit tight for space now.
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?
Surely that should just be handled by the 3G router? ;)
Yes, it does seem to manage quite well actually. The connection disappears at intervals but does also always seem to come back.
On 11/12/10 15:06, Brett Parker wrote:
On 11 Dec 09:37, Chris G wrote:
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?
*if* you've got a vm/permanently connected machine/server somewhere (I'd guess you have otherwise where would you terminate the ssh connection...) then I'd suggest using vpn software like OpenVPN instead to that box. Then you're not limited to just the ssh port.
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?
Surely that should just be handled by the 3G router? ;)
Are you suggesting VPN just because it will restart the connection when the 3G comes up? If not, is it not overkill just for command line access?
(no offence intended, trying to learn, not yet set up my own vpn)
Steve
On 13 Dec 22:02, steve-ALUG@hst.me.uk wrote:
On 11/12/10 15:06, Brett Parker wrote:
On 11 Dec 09:37, Chris G wrote:
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?
*if* you've got a vm/permanently connected machine/server somewhere (I'd guess you have otherwise where would you terminate the ssh connection...) then I'd suggest using vpn software like OpenVPN instead to that box. Then you're not limited to just the ssh port.
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?
Surely that should just be handled by the 3G router? ;)
Are you suggesting VPN just because it will restart the connection when the 3G comes up? If not, is it not overkill just for command line access?
(no offence intended, trying to learn, not yet set up my own vpn)
I'm suggesting it because it makes a lot of problems go away, will autoreconnect, and means that you don't actually have to think as much about what you actually *need* access to.
As for using ssh reverse tunnels, we do that a *lot* at work, and it's not that reliable - the closest you can get to something that is almost reliable is using autossh, and that's not that great at it.
-
Brett Parker -
Chris G -
James Bensley -
mick -
steve-ALUG＠hst.me.uk