There are a couple of more things you need to do to make it a reliable solution. From the client machine tunnel RDP traffic to an outside server.
SSH TUNNEL RASPBERRY PI WINDOWS
L flag specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side. This forwards all connections made to localhost on port 3000 to the Windows Server ( 192.168.1.10) using port 3389. External server -> Raspberry Pi -> Windows Serverįirst of all, I’m going to create a tunnel to forward RDP traffic from to the Windows Server. Two SSH tunnels are needed to forward traffic from the client machine to and from there to the Pi. Tunneling RDP trafficįor the sake of the example I’m going to assume the IP of the Windows Server at the office network is 192.168.1.10 and the server outside of the network can be accessed via. If you were able to connect to your Pi then the tunnel is working. We defined that all connections from our server to localhost on port 2222 should be forwarded to the Pi. Why connect to localhost on port 2222? Recall from part 1 that we created a reverse SSH tunnel from the Pi to the server. I’m going to create an SSH session to the VPS and from there I’m going to create another SSH session to the Pi.Ĭonnecting to the external server: $ ssh there let’s create another SSH session to our Pi which is inside the office network: $ ssh -p 2222 Testing SSH accessįirst, let’s make sure that the reverse SSH tunnel is working as expected.
SSH TUNNEL RASPBERRY PI HOW TO
In part 2 I promised to show an example use case on how to connect to a Windows Server over RDP via a reverse SSH tunnel. If you have not read part 1 then I strongly encourage you to do that. Last time we got a Raspberry Pi set up and a VPS ready and accessible via SSH. That requires some SSH tunneling.Notice! This post is more than a year old. In the next part let’s look at an example use case on how to connect to a Windows workstation via RDP. That means you have access to your work network. From there it is possible to access the Pi from wherever you have access to the external server. So far we’ve set up the Pi which connects out to an external server. For further reading about SSH tunnels, check out this StackExchange answer. The -N flag tells SSH to not execute a remote command. Meaning that all connections made to port 2222 on your server are forwarded to the Pi on port 22. The -R flag specifies that the given port on the remote (server) host is to be forwarded to the given host and port on the local side. $ ssh -N -R 2222:localhost:22 is connecting to your server using the username user. Now let’s create a tunnel from your Pi to the Linux server. Ubuntu help pages have a step-by-step guide on how to do that. It is needed so the Pi can ssh into your server without being prompted for a password. If you have not yet set up key-based authentication then this should be the next step. Then you should check if you can connect to your server via SSH. To begin with, plug in your Pi and connect it to your office network.
Additionally, read this post about further securing your SSH server. If not, then you could create a cheap VPS at DigitalOcean for example.
If you already have a box with a static IP and SSH running then you’re good to go. You’re going to need an outside server for your Pi to connect into. You could put that into use and create a connection to your work machine by creating a reverse SSH tunnel. But you have a spare Raspberry Pi lying around. Probably you don’t have a VPN which you could use to connect to your work network. You have a small office with no dedicated IT support. You need to access your work computer from your home. Notice! This post is more than a year old.
0 kommentar(er)
