2025-03-14 21:59:59 -06:00
|
|
|
# tailscale
|
|
|
|
|
|
|
|
|
|
> A private WireGuard network service.
|
|
|
|
|
> Some subcommands such as `up` have their own usage documentation.
|
2025-03-19 19:23:44 -06:00
|
|
|
> More information: <https://tailscale.com/kb/1080/cli>.
|
|
|
|
|
|
|
|
|
|
- Allow the current user to operate on the Tailscale daemon:
|
|
|
|
|
|
|
|
|
|
`sudo tailscale set --operator $USER`
|
2025-03-14 21:59:59 -06:00
|
|
|
|
2026-08-06 22:19:46 -06:00
|
|
|
- Handle connection to Tailscale (connect, disconnect, check status):
|
2025-03-14 21:59:59 -06:00
|
|
|
|
2026-08-06 22:19:46 -06:00
|
|
|
`tailscale {{up|down|status}}`
|
2025-03-14 21:59:59 -06:00
|
|
|
|
2026-08-06 22:19:46 -06:00
|
|
|
- Offer the current machine to be an exit node for internet traffic:
|
2025-03-14 21:59:59 -06:00
|
|
|
|
2026-08-06 22:19:46 -06:00
|
|
|
`tailscale set --advertise-exit-node`
|
2025-03-14 21:59:59 -06:00
|
|
|
|
2026-08-06 22:19:46 -06:00
|
|
|
- Use a specific exit node for internet traffic:
|
2025-03-14 21:59:59 -06:00
|
|
|
|
2026-08-06 22:19:46 -06:00
|
|
|
`tailscale set --exit-node {{ip_address|hostname}}`
|
2025-03-14 21:59:59 -06:00
|
|
|
|
|
|
|
|
- Ping a peer node at the Tailscale layer and display which route it took for each response:
|
|
|
|
|
|
2026-08-06 22:19:46 -06:00
|
|
|
`tailscale ping {{ip_address|hostname}}`
|
2025-03-14 21:59:59 -06:00
|
|
|
|
|
|
|
|
- Analyze the local network conditions and display the result:
|
|
|
|
|
|
|
|
|
|
`tailscale netcheck`
|
|
|
|
|
|
2025-03-19 19:23:44 -06:00
|
|
|
- Start a web server for controlling the Tailscale daemon:
|
2025-03-14 21:59:59 -06:00
|
|
|
|
|
|
|
|
`tailscale web`
|
|
|
|
|
|
|
|
|
|
- Display a shareable identifier to help diagnose issues:
|
|
|
|
|
|
|
|
|
|
`tailscale bugreport`
|
