Tailscale - Revision history

Nick: Added Taildrop section

2026-04-09T09:00:30Z

Added Taildrop section

Nick at 11:41, 4 April 2026

2026-04-04T11:41:14Z

Nick: /* Tags */

2026-04-04T11:39:35Z

Nick: /* Autogroups */

2026-04-04T11:17:40Z

Autogroups

Nick: /* Autogroups */

2026-04-04T10:59:41Z

Autogroups

Nick at 10:46, 4 April 2026

2026-04-04T10:46:29Z

Nick: /* Tailscale SSH */

2026-04-04T10:40:40Z

Tailscale SSH

Nick: /* Groups */

2026-04-04T10:38:22Z

Groups

Nick: /* Access Controls */

2026-04-04T10:31:31Z

Access Controls

Nick at 10:22, 4 April 2026

2026-04-04T10:22:25Z

← Older revision		Revision as of 09:00, 9 April 2026
Line 202:		Line 202:
	],</nowiki>		],</nowiki>

		+
		+
		+	= Taildrop (File Sharing Over Tailscale)=
		+	As of writing, this feature is in pre-1.0, but allows for the encrypted transfer of files via the nodes in your tailnet.
		+
		+
		+	== Sending Files ==
		+	To send files using Taildrop:
		+	<nowiki>tailscale file cp FILE_NAME(S) TARGET_HOSTNAME:
		+	NOTE: the ':' trailing at the end of the line is intentional and should be appended to the desired hostname.</nowiki>
		+
		+	i.e.
		+
		+	If you wanted to copy a file (./accounting/2026/budget-report.xlsx) from the localhost to a file server on your tailnet (finance-archive-server):
		+	<nowiki>tailscale file cp ./accounting/2026/budget-report.xlsx finance-archive-server:</nowiki>
		+
		+
		+	== Receiving Files ==
		+	To receive files from the tailnet, you would use the command:
		+	<nowiki>sudo tailscale file get /path/to/desired/file/destination/</nowiki>
		+
		+	Files are (as of writing) received as root, because the assocated daemon process is running as root, therefore 'sudo' is required for this command to function.

@@ Line 1: / Line 1: @@
 = Installing Tailscale =
@@ Line 45: / Line 46: @@
 === User Roles ===
 More information regarding user roles can be found [https://tailscale.com/docs/reference/user-roles here.]
@@ Line 72: / Line 74: @@
 autogroup:owner -- All the members with the Owner role, which is the default role the account holder has
 == Tags ==
@@ Line 105: / Line 109: @@
 Then these tag(s) would need to be approved from within the Admin console before they are created/applied to the machine.
 == Examples ==
@@ Line 141: / Line 147: @@
   <nowiki>sudo tailscale set --ssh</nowiki>
 This should almost immediately reflect on the Admin console as well with an SSH label.
@@ Line 146: / Line 153: @@
 To connect to a host that is already configured for SSH and that has the ACL configuration for SSH already in place, looks like this:
   <nowiki>tailscale ssh USER@MACHINE_NAME</nowiki>
@@ Line 154: / Line 162: @@
 To restrict which users/hosts can access other hosts (via SSH specifically), the ACL needs to be updated.
 === Restricting SSH Via Users ===
@@ Line 167: / Line 176: @@
 ],</nowiki>
 This restricts access to the 'production-db' machine to only 'janedoe@example.com', and they would NOT need to re-authenticate when connecting.
 === Restricting SSH Via Groups ===
@@ Line 178: / Line 188: @@
      },
 ],</nowiki>
 === Restricting SSH Via Tags ===
@@ Line 205: / Line 216: @@
 Or using the command:
   <nowiki>sudo tailscale set --no-logs-no-support</nowiki>

← Older revision		Revision as of 11:39, 4 April 2026
Line 74:		Line 74:

	== Tags ==		== Tags ==
		+	Tags can be created manually within the Admin console or via the command line from the machines on the tailnet (with approval from the Admin console).

		+	Tags are applied to various machines to label them as a service, an operating system, etc.
		+
		+	i.e. Applying the 'Prod' tag to all the production machines and 'Dev' tag to development machines, or 'Local'/'Cloud' for machines that are located locally or in the cloud.
		+
		+
		+	=== Admin Console ===
		+	To create tags from the Admin console, you can find the GUI editor under 'Access Controls'>'Visual Editor'>'Tags' using the 'Create Tag' button and filling out the provided form.
		+
		+	Tags can also be created in the Admin console from directly within the ACL file like so:
		+	<nowiki>
		+	"tagOwners": {
		+	// Description of the tag below this line
		+	"tag:TAG_NAME": ["OWNER OF THIS TAG"], // The owner can be a user, a group, an autogroup, etc
		+	}
		+	</nowiki>
		+	i.e.
		+	<nowiki>
		+	"tagOwners": {
		+	// Tag for machines in the production environment
		+	"tag:prod": ["group:production"],
		+	}</nowiki>
		+	This would create the tag 'prod' that is owned by the 'production' group.
		+
		+
		+	=== Command Line ===
		+	To submit tags to the Admin console for approval (from the Owner/Admin) from the command line of a machine:
		+	<nowiki>sudo tailscale up --advertise-tags=tag:TAG_NAME,tag:TAG_NAME_2</nowiki>
		+
		+	Then these tag(s) would need to be approved from within the Admin console before they are created/applied to the machine.

	== Examples ==		== Examples ==

@@ Line 67: / Line 67: @@
 ==== Commonly Used Autogroups ====
-autogroup:self --
+autogroup:self -- All the devices that are owned by same user
-autogroup:member --
+autogroup:member -- All the members of the tailnet
-autogroup:
+autogroup:owner -- All the members with the Owner role, which is the default role the account holder has
 == Tags ==

← Older revision		Revision as of 10:59, 4 April 2026
Line 64:		Line 64:

	=== Autogroups ===		=== Autogroups ===
		+	"An autogroup is a type of built-in target that automatically groups devices, users, or IP addresses based on specific criteria. They let you select dynamic sets of users, devices, or routes that might be challenging or even impossible to select by other means." [https://tailscale.com/docs/reference/targets-and-selectors?q=autogroups Source] and [https://tailscale.com/docs/reference/syntax/policy-file#autogroups Breakdown of Autogroups]

		+	==== Commonly Used Autogroups ====
		+	autogroup:self --
		+
		+	autogroup:member --
		+
		+	autogroup:

	== Tags ==		== Tags ==

@@ Line 1: / Line 1: @@
 = Installing Tailscale =
 == Linux ==
@@ Line 31: / Line 32: @@
 Once authenticated, the host should appear in your Machines page on the Admin console within your TailNet (Tailscale Network)
@@ Line 38: / Line 40: @@
 [[Tailscale#Tailscale_SSH|Tailscale SSH]] is also not configured by default and needs to be enabled on a host by host basis and then permitted in the ACL file from the admin console.
 == Users ==
 === User Roles ===
 More information regarding user roles can be found [https://tailscale.com/docs/reference/user-roles here.]
 == Groups ==
@@ Line 60: / Line 64: @@
 === Autogroups ===
 == Tags ==
@@ Line 92: / Line 97: @@
+}
 </nowiki>
 = Tailscale SSH =
@@ Line 97: / Line 104: @@
   <nowiki>sudo tailscale set --ssh</nowiki>
 This should almost immediately reflect on the Admin console as well with an SSH label.
 == Connecting Via Tailscale SSH ==
 To connect to a host that is already configured for SSH and that has the ACL configuration for SSH already in place, looks like this:
   <nowiki>tailscale ssh USER@MACHINE_NAME</nowiki>
 == ACL Configuration ==
@@ Line 144: / Line 153: @@
      },
 ],</nowiki>
 = Disable Logging =