You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Go to file

James Tucker e1e22785b4 net/netcheck: ensure prior preferred DERP is always in netchecks In an environment with unstable latency, such as upstream bufferbloat, there are cases where a full netcheck could drop the prior preferred DERP (likely home DERP) from future netcheck probe plans. This will then likely result in a home DERP having a missing sample on the next incremental netcheck, ultimately resulting in a home DERP move. This change does not fix our overall response to highly unstable latency, but it is an incremental improvement to prevent single spurious samples during a full netcheck from alone triggering a flapping condition, as now the prior changes to include historical latency will still provide the desired resistance, and the home DERP should not move unless latency is consistently worse over a 5 minute period. Note that there is a nomenclature and semantics issue remaining in the difference between a report preferred DERP and a home DERP. A report preferred DERP is aspirational, it is what will be picked as a home DERP if a home DERP connection needs to be established. A nodes home DERP may be different than a recent preferred DERP, in which case a lot of netcheck logic is fallible. In future enhancements much of the DERP move logic should move to consider the home DERP, rather than recent report preferred DERP. Updates #8603 Updates #13969 Signed-off-by: James Tucker <james@tailscale.com>		2 days ago
.bencher	…
.github	…
appc	…
atomicfile	…
chirp	…
client	…
clientupdate	…
cmd	…
control	…
derp	…
disco	…
docs	…
doctor	…
drive	…
envknob	…
gokrazy	…
health	…
hostinfo	…
internal	…
ipn	…
jsondb	…
k8s-operator	…
kube	…
licenses	…
log	…
logpolicy	…
logtail	…
metrics	…
net	…
omit	…
packages/deb	…
paths	…
portlist	…
posture	…
prober	…
proxymap	…
release	…
safesocket	…
safeweb	…
scripts	…
sessionrecording	…
smallzstd	…
ssh/tailssh	…
syncs	…
tailcfg	…
taildrop	…
tempfork	…
tka	…
tool	…
tsconst	…
tsd	…
tsnet	…
tstest	…
tstime	…
tsweb	…
types	…
util	…
version	…
wf	…
wgengine	…
words	…
.gitattributes	…
.gitignore	…
.golangci.yml	…
ALPINE.txt	…
AUTHORS	…
CODEOWNERS	…
CODE_OF_CONDUCT.md	…
Dockerfile	…
Dockerfile.base	…
LICENSE	…
Makefile	…
PATENTS	…
README.md	…
SECURITY.md	…
VERSION.txt	…
api.md	…
assert_ts_toolchain_match.go	…
build_dist.sh	…
build_docker.sh	…
flake.lock	…
flake.nix	…
go.mod	…
go.mod.sri	…
go.sum	…
go.toolchain.branch	…
go.toolchain.rev	…
gomod_test.go	…
header.txt	…
pkgdoc_test.go	…
pull-toolchain.sh	…
shell.nix	…
staticcheck.conf	…
update-flake.sh	…
version-embed.go	…
version_tailscale_test.go	…
version_test.go	…

README.md

Tailscale

https://tailscale.com

Private WireGuard® networks made easy

Overview

This repository contains the majority of Tailscale's open source code. Notably, it includes the tailscaled daemon and the tailscale CLI tool. The tailscaled daemon runs on Linux, Windows, macOS, and to varying degrees on FreeBSD and OpenBSD. The Tailscale iOS and Android apps use this repo's code, but this repo doesn't contain the mobile GUI code.

Other Tailscale repos of note:

the Android app is at https://github.com/tailscale/tailscale-android
the Synology package is at https://github.com/tailscale/tailscale-synology
the QNAP package is at https://github.com/tailscale/tailscale-qpkg
the Chocolatey packaging is at https://github.com/tailscale/tailscale-chocolatey

For background on which parts of Tailscale are open source and why, see https://tailscale.com/opensource/.

Using

We serve packages for a variety of distros and platforms at https://pkgs.tailscale.com.

Other clients

The macOS, iOS, and Windows clients use the code in this repository but additionally include small GUI wrappers. The GUI wrappers on non-open source platforms are themselves not open source.

Building

We always require the latest Go release, currently Go 1.23. (While we build releases with our Go fork, its use is not required.)

go install tailscale.com/cmd/tailscale{,d}

If you're packaging Tailscale for distribution, use build_dist.sh instead, to burn commit IDs and version info into the binaries:

./build_dist.sh tailscale.com/cmd/tailscale
./build_dist.sh tailscale.com/cmd/tailscaled

If your distro has conventions that preclude the use of build_dist.sh, please do the equivalent of what it does in your distro's way, so that bug reports contain useful version information.

Bugs

Please file any issues about this code or the hosted service on the issue tracker.

Contributing

PRs welcome! But please file bugs. Commit messages should reference bugs.

We require Developer Certificate of Origin Signed-off-by lines in commits.

See git log for our commit message style. It's basically the same as Go's style.

About Us

Tailscale is primarily developed by the people at https://github.com/orgs/tailscale/people. For other contributors, see:

Legal

WireGuard is a registered trademark of Jason A. Donenfeld.