Differences

This shows you the differences between two versions of the page.

--- pi:remote_access [2025/04/14 21:58] – m0mzf
+++ pi:remote_access [2025/04/14 22:08] (current) – [Remotely accessing your Pi - Roll your own!] m0mzf
@@ Line 1: / Line 1: @@
 ======= Remotely accessing your Pi - Roll your own!=======
-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 solution, what on the Pi do you want to access; all these questions and scenarios have different solutions. This guide is mostly geared towards packet operators running LinBPQ on a headless Pi, so let's get into it!
+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" is mostly geared towards packet operators with limited network / Linux / Pi experience running LinBPQ on a headless Pi, so let's get into it!
 =====IP addresses, ports, and the internet=====
@@ Line 40: / Line 40: @@
 =====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 tunnel end to access anything you'd normally access over the network, just as if it was plugged in at home. Wireguard can do much more, such as create a bridges between multiple networks, but that's outside the scope of these ramblings.
+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====
+< To do >
 Public / Private keys
 SOCKS proxying; browser / telnet
@@ Line 82: / Line 83: @@
 <code> ssh [email protected] </code>
-=======Remotely accessing your Pi - Commercial solutions=======
+=======Remotely accessing your Pi - Third party solutions=======
 To do!
   * Tailscale - wireguard made super easy
   * Anydesk - remote desktop made easy
   * Rustdesk - remote desktop made easy and open source