• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Remote Access to Sheeva (like teamviewer) through Command Line  (Read 6225 times)
PlugMeIn
Newbie
*

Karma: 0
Posts: 3


View Profile
« on: June 10, 2010, 06:54:12 PM »

Hi All.

I am new to Linux but have successfully set up my Sheeva to do the tasks I need.

I have my router port forwarded so I can use putty to access the Sheeva via the internet.

I would like to be able to access it without opening that port. Eg: if I plug into my office network.

I have used teamviewer with windows and I see there is a Linux version, but I believe it needs a GUI.

Does anyone have any alternatives or info on how to install Teamviewer (and Gui) on my Sheeva?

TIA.

PMI
Logged

Mimoza
Newbie
*

Karma: 0
Posts: 16



View Profile
« Reply #1 on: June 11, 2010, 12:54:22 AM »

Yuo can install  X.org on your plug ....
And you connect to your plug with "ssh -X" to obtain the Gui of the software  Grin
Logged

PlugMeIn
Newbie
*

Karma: 0
Posts: 3


View Profile
« Reply #2 on: June 13, 2010, 10:03:51 PM »

Thanks for your suggestion, I managed to install X and VNC, however Teamviewer Linux did not work (not compiles for ARM or some similar message).

Any other suggestions?
Logged

chaotix
Newbie
*

Karma: 2
Posts: 11


View Profile
« Reply #3 on: June 18, 2010, 08:11:45 PM »

I have no experience with teamviewer, as I don't like third parties to have access to my data.

But if you have a computer available that is always on (or at least when you want to access your plug) and it either directly accessible or you have control over the NAT router, you can use some ssh tunneling magic. Let's call this computer 'middleman'.

sheeva# ssh -R 2222:localhost:22 user@middleman
(Leave this running all the time. This opens a tunnel from middleman port 2222 to sheeva 22 (ssh port).

If you want to access your plug:
client# ssh -L 2222:localhost:2222 user@middleman
(This opens a tunnel from your client port 2222 to middleman port 2222.)
Now you can ssh into your plug:
client# ssh -p 2222 user@localhost
(Where 'user' is the username on your plug.)

Port 2222 is just some arbitrary number. Actually it's two arbitrary numbers as you could put the second tunnel on a different port.

The second tunnel is necessary as ssh is configured to only permit access to ssh tunnels from localhost. If you configure your middleman server to permit remote computers to access ssh tunnel you can skip the second step and ssh directly into your plug:
client# ssh -p 2222 user@middleman
(Where 'user' is again the username of your plug.)
But getting your ssh-daemon on middleman to allow this is not trivial IIRC. I tried this once although I don't remember which direction I wanted to tunnel and at least on Debian I would have had to recompile ssh.

Another possibility is to use 'grunt' or something similar if your plug is receiving emails. (See http://www.debian-administration.org/articles/515)

Good luck,
Lars
Logged

Pages: [1]
Print
Jump to: