mirrors/Axis_Cam_Tailscale
1
0
Fork 0
mirror of https://github.com/Mo3he/Axis_Cam_Tailscale.git synced 2026-09-19 14:24:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify reverse-SSH tunnel requirements in README

Browse Source 
Updated the section on reverse-SSH tunnel to clarify root requirements and added details about using a non-root SSH user.
This commit is contained in:
Weston Blieden
2026-06-10 13:12:21 +02:00
committed by GitHub
parent fd5cec50bb
commit c4ac8ab601
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -3
View File
@@ -117,7 +117,8 @@ There is an important asymmetry to understand. Making the camera **reachable fro
In short: on non-root builds the proxies cover apps that know how to use a proxy, but a system feature like "add network share" opens a raw socket that never touches the tunnel. The ROOT build is the clean way to let the camera *consume* tailnet services.
### Plan B: reverse-SSH tunnel (works even on non-root)
### Plan B: reverse-SSH tunnel
> **Requires root on the camera.** Port 445 is privileged, so binding it needs a root-capable build (e.g. developer certificates installed).
If you cannot use the ROOT build but still need the camera to mount a share on a machine that is on your tailnet, you can make the remote share appear **local** to the camera with a reverse SSH tunnel. Because the destination becomes `127.0.0.1`, the proxy-unaware SMB client never has to route over the tailnet.
@@ -130,8 +131,6 @@ ssh -R 445:localhost:445 root@<camera-tailscale-ip>
Then, in the camera's **System → Storage → Add network share** dialog, use `127.0.0.1` as the share host and connect.
> **Requires root on the camera.** Port 445 is privileged, so binding it needs a root-capable build (e.g. developer certificates installed, or the ROOT variant). If the share dialog ever supports a custom (unprivileged) SMB port, the same trick works as a non-root SSH user.
---
## Updating Tailscale