Relationships
#4924 Tailnet: developer machines can reach each other's tailscale serve by default
Opened by zack · 11/19/2026
Problem
Developer machines on the tailnet can't reach each other by default. If you run swamp serve, swamp dashboard or swamp start --host behind tailscale serve on your laptop, a teammate can't open it until someone changes the policy by hand. Sharing a running serve with a teammate should just work.
The infrastructure handoff doc says the grants are "still allow-all", which doesn't match what we see. Before changing anything, read the live policy with tailnet-policy get from ops to find out which is true.
Options
- Members reach all of each other's ports. One grant,
autogroup:member→autogroup:member,ip: ["*"]. It's the simplest, but it exposes everything a laptop listens on (sshd, dev servers bound to 0.0.0.0, local databases). One compromised laptop could then reach every other developer machine. - Members reach only each other's
tailscale serve(recommended).tailscale servelistens on tcp:443 (HTTPS, with a MagicDNS cert), so we grant just that port between members. Each user keeps full access to their own devices throughautogroup:self.
Proposal: option 2
"grants": [
// full access to your own devices
{"src": ["autogroup:member"], "dst": ["autogroup:self"], "ip": ["*"]},
// teammates reach what you publish with `tailscale serve`
{"src": ["autogroup:member"], "dst": ["autogroup:member"], "ip": ["tcp:443"]},
]Why:
- Publishing something becomes an explicit act (
tailscale serve). Binding to 0.0.0.0 by accident exposes nothing. - Serve gives you TLS and a stable
<host>.<tailnet>.ts.netname, which is what swamp serve and dashboard clients expect anyway. autogroup:memberleaves out users from other tailnets who were shared in, so external guests don't get this.- It doesn't widen dev → infra access. Tagged GCP nodes keep their own grants, and this is a step toward the per-role grants the handoff doc already plans.
Out of scope: serve on ports other than 443 (--https=8443, etc.). We can add ports later if needed, or move to Tailscale Services (svc:) for named shared endpoints.
Acceptance
- The live policy is confirmed with
tailnet-policy get, and the handoff doc is corrected if it's out of date. - The policy above is applied through the
tailnet-policymodel (validate, thenapply). - A dev machine can open another member's
https://<host>.<tailnet>.ts.netserved throughtailscale serve. - A dev machine cannot reach another member's non-serve ports (e.g. tcp:22, or a dev server on :3000).
- A user still reaches all ports on their own devices.
Closed
No activity in this phase yet.
zack commented 11/20/2026, 12:03:13 AM
this is a bit wrong since tailscale serve will choose other ports. so i don't know if we can support just it without exposing all ports
swamp_lord commented 11/20/2026, 6:05:09 PM
Shipped: option 1, not the proposal. By decision, members reach each other's own machines on every port, not just 443 (PR #537, applied from ops with tailnet-policy get + apply on 2026-11-20; the read-back shows the rule and its test live).
- Grant
autogroup:member→autogroup:member,ip: ["*"]. The destination is people's own devices only: tagged nodes (servers, routers, ops, Grafana, sales' VMs) and subnet routes (prod, crm) are not included. Tailscale SSH between people is unchanged (still denied). - Sharing is one command:
tailscale serve --bg --tcp=<port> <port>(any protocol, works for localhost-only apps);tailscale serve resetto stop. HTTPS with a cert:tailscale serve --bg 3000(443/8443/10000). - Trade-off accepted: anything listening on all interfaces on a laptop is reachable by other members too; the "only 443" deny in the acceptance list therefore doesn't apply.
- Live policy confirmed default deny (no allow-all).
- Docs: new
docs/tailscale-usage-guide.htmlandtailscale-usageskill;tailnet-policyskill updated.
Not done: an end-to-end check from a second machine (zack is serving on 7443; someone else opening it confirms); the infrastructure handoff doc's backlog still says "replace the allow-all grant" and needs a one-line fix. Possible follow-up: share with your own group only (port ranges per audience), discussed but not built.
Sign in to post a ripple.