Re: SSH, remote device connected via 3G
- From: Jer <jer@xxxxxxxxxx>
- Date: Sat, 29 Mar 2008 00:35:31 +0800
This is getting complex. Setting up of DYNDNS, openVPN/getting a VPN router, making vpn client work on Linux, configuration on auto-reconnect upon disconnection, and troubleshooting... All are not my cup of tea. Well, I just have to keep learning :)
Thanks for your suggestion! And have a good day ahead!
Jurgen Haan wrote:
Jer wrote:.
Am I missing out something? Or is this timeout failure caused by
possible NAT arrangement on the ISP side? Is there any way to overcome
this failure?
It's very likely that there's some way in the ISP infrastructure that
makes in 1-way.
Try opening a VPN between source and target.
Laptop as a VPN client and the other machine as a VPN server.
After that you can connect back to the Laptop through the VPN.
I can see the problem this is causing because it would mean initiating 2
client-server connections from both sides.
the VPN from laptop to workstation and the SSH from workstation to
laptop. If you're able to do both, you might aswell be able to sit
behind the laptop directly.
The only way this would work is when both machines would be up all the time.
-R-
- References:
- SSH, remote device connected via 3G
- From: Jer
- Re: SSH, remote device connected via 3G
- From: Jurgen Haan
- SSH, remote device connected via 3G
- Prev by Date: dhcp by mac address mask
- Next by Date: Re: VNC viewer is connected but blank screen
- Previous by thread: Re: SSH, remote device connected via 3G
- Next by thread: dhcp by mac address mask
- Index(es):
Relevant Pages
|