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.
tailscale/tsnet
Harry Harpham d0e2e366ef
tsnet: reset serve config only once
Prior to this change, we were resetting the tsnet's serve config every
time tsnet.Server.Up was run. This is important to do on startup, to
prevent messy interactions with stale configuration when the code has
changed.

However, Up is frequently run as a just-in-case step (for example, by
Server.ListenTLS/ListenFunnel and possibly by consumers of tsnet). When
the serve config is reset on each of these calls to Up, this creates
situations in which the serve config disappears unexpectedly. The
solution is to reset the serve config only on the first call to Up.

Fixes #8800
Updates tailscale/corp#27200
Signed-off-by: Harry Harpham <harry@tailscale.com>
3 days ago
..
example tsnet: split user facing and backend logging 2 years ago
depaware.txt net/portmapper, go.mod: unfork our goupnp dependency 4 days ago
example_tshello_test.go tsnet: add examples (#8289) 3 years ago
example_tsnet_test.go tsnet: split user facing and backend logging 2 years ago
packet_filter_test.go tsnet: add tstest.Shard on the slow tests 2 months ago
tsnet.go tsnet: reset serve config only once 3 days ago
tsnet_test.go tsnet: enable node registration via federated identity 1 month ago