Remote access
I manage a network in Kenya from the UK. I have a couple of Pis on the network sending me back information. Because of ISP restrictions I cannot use port forwarding and therefore cannot use remote control products like VNC. However, on my PCs and Macs I can happily use the likes of TeamViewer, Logmein and the Google Chrome remote desktop. Currently I have to do a double terminal connect to access the Pi (one remote, one local via a Windows 7 server). Is there any equivalent app for the Pi ?
Re: Remote access
After I posted that, I came across this posting in the forum -
"I recommend a solution based on OpenVPN. Run OpenVPN as client on your PRI and connect it to a OpenVPN server running in your home or office.
Once established VPN you will be able to connect with your RPI using ssh or vnc."
Do people generally agree this is the best solution, or is there a stand alone app that does it ?
"I recommend a solution based on OpenVPN. Run OpenVPN as client on your PRI and connect it to a OpenVPN server running in your home or office.
Once established VPN you will be able to connect with your RPI using ssh or vnc."
Do people generally agree this is the best solution, or is there a stand alone app that does it ?
-
DougieLawson
- Posts: 39120
- Joined: Sun Jun 16, 2013 11:19 pm
- Location: A small cave in deepest darkest Basingstoke, UK
- Contact: Website Twitter
Re: Remote access
The only restriction on that is that you need port 1194 both TCP & UDP open and port forwarded on your home router. You also need the remote machine to be able to connect to the server's port 1194 without getting blocked by any firewall.
If that's not possible you can configure OpenVPN to use port 80 (so that it appears as http traffic as far as a network admin who controls a firewall is concerned). That is a bit of an ugly hack.
If that's not possible you can configure OpenVPN to use port 80 (so that it appears as http traffic as far as a network admin who controls a firewall is concerned). That is a bit of an ugly hack.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.
Criticising any questions is banned on this forum.
Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.
Criticising any questions is banned on this forum.
Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.
Re: Remote access
Hi
Awesome stuff about managing a Kenyan network. It is difficult to know what your restrictions are exactly, as I am not quite clear on where the port forwarding is being limited. VNC can be run over an ssh tunnel very effectively. I have desktops on Linux systems behind a firewall in which only port 22 (ssh) is open. I use Putty to make a tunnel from my windows desktop to the target machine, and all traffic goes through port 22 (not the default port for VNC, 5900). Sorry if that's irrelevant.
Jim
Awesome stuff about managing a Kenyan network. It is difficult to know what your restrictions are exactly, as I am not quite clear on where the port forwarding is being limited. VNC can be run over an ssh tunnel very effectively. I have desktops on Linux systems behind a firewall in which only port 22 (ssh) is open. I use Putty to make a tunnel from my windows desktop to the target machine, and all traffic goes through port 22 (not the default port for VNC, 5900). Sorry if that's irrelevant.
Jim
Unix engineer since 1989
Re: Remote access
Thanks for this, sorry about the delay in response.cpc464 wrote:Hi
Awesome stuff about managing a Kenyan network. It is difficult to know what your restrictions are exactly, as I am not quite clear on where the port forwarding is being limited. VNC can be run over an ssh tunnel very effectively. I have desktops on Linux systems behind a firewall in which only port 22 (ssh) is open. I use Putty to make a tunnel from my windows desktop to the target machine, and all traffic goes through port 22 (not the default port for VNC, 5900). Sorry if that's irrelevant.
Jim
As I understand it Orange Kenya, the ISP I am using, reuse external IP addresses for multiple customers simultaneously. As a result there is not a unique destination to communicate with over ip.
I already use Putty to ssh to my Pi from my Windows 7 server machine. However I'm not sure I understand how to use it to create an ssh tunnel.
-
FTrevorGowen
- Forum Moderator
- Posts: 5618
- Joined: Mon Mar 04, 2013 6:12 pm
- Location: Bristol, U.K.
- Contact: Website
Re: Remote access
Is what I do here:tdenson wrote: ...
I already use Putty to ssh to my Pi from my Windows 7 server machine. However I'm not sure I understand how to use it to create an ssh tunnel.
http://www.cpmspectrepi.webspace.virgin ... aspPi.html
of any help? (I'm not sure if it "quite fits" into your setup, since I'm running PuTTY on a Linux box in those examples. However, in the past**, IIRC, I used similar settings to remotely log into a "secure" Linux cluster from a Windows XP box)
Trev.
** before I retired.
Still running Raspbian Jessie or Stretch on some older Pi's (an A, B1, 2xB2, B+, P2B, 3xP0, P0W, 2xP3A+, P3B+, P3B, B+, and a A+) but Buster on the P4B's. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm
Re: Remote access
1.) LogMeIn has a working client for Raspberry Pi:
http://raspberrypi.stackexchange.com/q/10110/17815
This solves your problem if you're having enough budget.
2.) I'm having the same problem (and low budget) and I think about the following:
- install VNC on the RPI with autostart, so it connects to my pc without interaction
- let RPI check every 30 seconds the URL http://example.org/PleaseCallMe.txt
- if the URL is available RPI starts VNC (and connects to my PC)
What I need to know:
a) is it possible to setup VNC with an autostart connection?
b) is it possible to let VNC run only on port 80 and/or 443?
c) how to get/install such a script to check URL and start VNC?
EDIT: Hmm.. maybe it would be better to start an OpenVPN tunnel, instead of starting VNC. And kill the tunnel after the URL is not available anymore. I think this would be much more flexible and works with Port 443 only. What do you think?
http://raspberrypi.stackexchange.com/q/10110/17815
This solves your problem if you're having enough budget.
2.) I'm having the same problem (and low budget) and I think about the following:
- install VNC on the RPI with autostart, so it connects to my pc without interaction
- let RPI check every 30 seconds the URL http://example.org/PleaseCallMe.txt
- if the URL is available RPI starts VNC (and connects to my PC)
What I need to know:
a) is it possible to setup VNC with an autostart connection?
b) is it possible to let VNC run only on port 80 and/or 443?
c) how to get/install such a script to check URL and start VNC?
EDIT: Hmm.. maybe it would be better to start an OpenVPN tunnel, instead of starting VNC. And kill the tunnel after the URL is not available anymore. I think this would be much more flexible and works with Port 443 only. What do you think?