Connecting to the Cyber@UC Network with Tailscale Client
This guide will walk you through connecting your Windows, macOS, and Linux machines to Cyber@UC's internal network using the provided Tailscale command.
Prerequisites
- Tailscale Installed: Ensure that the Tailscale client is installed on your Windows, macOS, or Linux machine. You can download it from the official Tailscale website: https://tailscale.com/download/
- Authentication Key: You have a valid authentication key for the Cyber@UC coordination server. Replace
<KEYHERE>in the command with your actual key.
Auth keys expire after 1hr
Auth Key Generation
The authentication keys used to connect to the subnet automatically generated as part of our infrastructure deployment process using CI/CD Pipelines and Terraform.
Connecting from Windows
- Open PowerShell as Administrator: Search for "PowerShell" in the Start Menu, right-click on it, and select "Run as administrator".
- Execute the Tailscale Command: Copy and paste the following command into the PowerShell window, replacing
<KEYHERE>with your actual authentication key: - Verify Connection:
- Check the Tailscale system tray icon (it should show as connected).
- Run the command:
Connecting from macOS
- Verify Tailscale Installation:
- Execute the Tailscale Command: Replace
<KEYHERE>with your actual authentication key: - Enter Password (If Prompted): Enter your user password for the
sudocommand. - Verify Connection:
- Check the Tailscale menu bar icon (should show as connected).
- Run:
Connecting from Linux
- Open your Terminal
- Execute the Tailscale Command: Replace
<KEYHERE>with your actual authentication key: - Enter Sudo Password (If Prompted).
-
Verify Connection:
- Run:
Understanding the Command
sudo tailscale up→ Starts or connects to the Cyber@UC Tailscale network.--auth-key=<KEYHERE>→ Specifies the authentication key. Replace<KEYHERE>with your actual key.--login-server=https://headscale.cyberatuc.org→ Tells Tailscale to use the Cyber@UC coordination server.--accept-routes→ Accepts routes advertised by other nodes.--accept-dns=false→ Prevents overwriting DNS settings. (Important: Setting this to true can break DNS).--reset→ Clears any previous Tailscale state before reconnecting.
Important Considerations
- Firewall: Ensure that your firewall is not blocking Tailscale’s required ports.
- Troubleshooting: If issues occur, check logs with
tailscale bugreportand review the Tailscale documentation for guidance.