pi:remote_access
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pi:remote_access [2025/04/14 21:50] – [Wireguard] m0mzf | pi:remote_access [2025/04/14 22:08] (current) – [Remotely accessing your Pi - Roll your own!] m0mzf | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======= | + | ======= |
- | Unsurprisingly there are many solutions to this particular cat; is the client Windows or Linux, do you have an internet connection with a public-facing IP address, do you want to roll your own or use / purchase a commercial | + | Unsurprisingly there are many solutions to this particular cat; is the client Windows or Linux, do you have an internet connection with a public-facing IP address, do you want to roll your own or use / purchase a third party solution, what on the Pi do you want to access; all these questions and scenarios have different solutions. This "guide" |
- | =====Roll your own===== | + | =====IP addresses, ports, and the internet===== |
- | ====IP addresses, ports, and the internet==== | + | |
To set up remote access without using a third party provider, save of course whichever ISPs you have chosen, you will need what is known as a //globally routable IP//, or //Public IP// This is a unique address on the internet which your ISP provides to you, and from this address you connect out, or indeed people connect in. There are two address spaces, IPv4 (which look like 173.194.203.102) and IPv6 (which look like 2607: | To set up remote access without using a third party provider, save of course whichever ISPs you have chosen, you will need what is known as a //globally routable IP//, or //Public IP// This is a unique address on the internet which your ISP provides to you, and from this address you connect out, or indeed people connect in. There are two address spaces, IPv4 (which look like 173.194.203.102) and IPv6 (which look like 2607: | ||
Line 38: | Line 37: | ||
Probably the best service is [[https:// | Probably the best service is [[https:// | ||
+ | |||
+ | =====Remote access tools===== | ||
+ | |||
+ | By far and away the most secure, flexible and modern way of doing this is using wireguard. Wireguard creates a tunnel between two points, perhaps your Pi and your favourite home PC, and from there you can just use the IP address of the Pi's end of the tunnel to access anything you'd normally do over the network, just as if it was plugged in at home. Wireguard can do much more, but that's outside the scope of these ramblings. | ||
====SSH==== | ====SSH==== | ||
+ | < To do > | ||
Public / Private keys | Public / Private keys | ||
SOCKS proxying; browser / telnet | SOCKS proxying; browser / telnet | ||
Line 79: | Line 83: | ||
< | < | ||
- | =====Commercial | + | =======Remotely accessing your Pi - Third party solutions======= |
To do! | To do! | ||
- | * Tailscale | + | * Tailscale |
- | * Anydesk | + | * Anydesk |
- | * Rustdesk | + | * Rustdesk |
pi/remote_access.1744667453.txt.gz · Last modified: 2025/04/14 21:50 by m0mzf