F39-TS: Yes
Rationale
The standard Linux TUN client assigns the node a stable tailnet address independently of its physical network address. A socket service at that virtual address and port can be reached locally through host routing or remotely through Tailscale using the same endpoint reference and socket interface.
Assessment method
Primary specifications, pinned source and explicit local-delivery composition; no runtime test
Source context
NET/ROM local dispatch, LISP EID separation and Tailscale Linux address assignment
Outstanding qualification
Documentary and pinned-source composition for the selected standard Linux TUN mode, not tsnet. router_linux.go reconciles LocalAddrs and assigns them to the TUN interface; normal local IP delivery supplies the co-resident path. The service must bind the virtual address or wildcard. Address stability lasts while registration is retained and the administrator does not change it. Node-plus-port naming is credited, not per-process cryptographic identity, local WireGuard traversal, grant enforcement equivalence, zero-copy or runtime certification.
Public sources
- https://tailscale.com/kb/1033/ip-and-dns-addresses
- https://github.com/tailscale/tailscale/blob/566f89e0fb2aa4b2f1ebf98761e45e62aa5ef225/wgengine/router/osrouter/router_linux.go
- https://man7.org/linux/man-pages/man8/ip-route.8.html
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round693.html