A Remote access question.

[Jayson]

I am not familar with linux so when i get this i will have to start learning but can you do remote access of the RPi through its eithernet connection?

So that with the proper setup you can just boot it up and have no need to have anything connected to it other than a eithernet and power connection.

[ShiftPlusOne]

Yup, if you just need a shell, then SSH is perfect.

Also, the window system (x11) is designed to be used across the network, so you can run programs remotely without any problems. So you can use ssh with X forwarding.

There's also FreeNX, VNC and a whole lot of other remote desktop servers out there.

So yeah, doing something like this is pretty trivial with Linux.

[Jayson]

Nice that can be handy thanks for the info.

[jamesh]

I've been using SSH on the prototype over USB wireless with no problem (well, occasional typing latency!). Not tried remote X yet.

[crundy]

Quote from jamesh on September 14, 2011, 12:15
I've been using SSH on the prototype over USB wireless with no problem (well, occasional typing latency!). Not tried remote X yet.


That's interesting. Any idea what's causing the latency? Network, network interface, or the R-Pi processor being a bit slow?

[obarthelemy]

From my perspective (newbie, with a Windows main PC), there's 4 ways to do it, from simplest to install and barest functionality/comfort, to hardest to install but peachy once you've got it to run:

- get a text command line, via SSH and Putty on Windows

- do a kind-of Remote Desktop (Windows style) via a VNC server on the Pi, and a client on Windows. There's Ultra-, Tight-, True-, and plenty other VNCs for that, all with versions for windows, Linux (lots of flavours), and plenty other OSes, it is very standard. Be aware though that VNC does bitmaps, not vectors, so a lot more data needs to travel between the sever and client. Redraws are slowish and ugly.

- do a true Remote Desktop from Windows, using Windows RDP protocol, thanks to FreeNX server on the Linux machine. Vectorial, hence much faster and pleasant.

- take advantage of X11, which natively supports displaying one PC's stuff on another. Most Linuxes' user intefaces (lxde, gnome, KDE...) use X11. But Windows doesn't really have it, and getting it to run is a pain, the best solution I could find was actually install a Virtual Machine running Linux on my Windows PC, and do X11 remoting from there. Otherwise, there's a whole lot of hooplah involving Cygwin that's good for giving headaches, mainly.

Actually, a package and doc to enable good remoting to the Pi would be a very useful projects for those of us who do have a Windows PC.

[mahin]

Quote from Jayson on September 14, 2011, 11:19
So that with the proper setup you can just boot it up and have no need to have anything connected to it other than a eithernet and power connection.

What you are looking for is FreeNX [ lacking development will not work out of the box ] NoMachine [ Commercial nothing ready for R-Pi ] and x2go. X2GO is Free / Open Source and being actively developed. It is now used with Skolelinux doing just what you are seeking. Seeing the specs of R-Pi model 'A' it is suitable. With Debian working on R-Pi x2go will also work but not yet tested.

You need not learn any thing to use that x2go on R-Pi a simple log-in will do, unless you wish to contribute then do learn about Linux.

[jamesh]

Quote from crundy on September 14, 2011, 14:30
Quote from jamesh on September 14, 2011, 12:15
I've been using SSH on the prototype over USB wireless with no problem (well, occasional typing latency!). Not tried remote X yet.


That's interesting. Any idea what's causing the latency? Network, network interface, or the R-Pi processor being a bit slow?

Pretty sure it's the wireless. Just typing on the Raspi itself is fine, but I prefer the net link as it means I can have it in a window running on my desktop and cut and paste works etc.