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

Harry Harpham 3c1be083a4 tsnet: ensure funnel listener cleans up after itself when closed ... Previously the funnel listener would leave artifacts in the serve config. This caused weird out-of-sync effects like the admin panel showing that funnel was enabled for a node, but the node rejecting packets because the listener was closed. This change resolves these synchronization issues by ensuring that funnel listeners clean up the serve config when closed. See also: e109cf9fdd Updates #cleanup Signed-off-by: Harry Harpham <harry@tailscale.com>		3 months ago
..
example	tsnet: split user facing and backend logging	2 years ago
depaware.txt	net/portmapper, go.mod: unfork our goupnp dependency	3 months 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	5 months ago
tsnet.go	tsnet: ensure funnel listener cleans up after itself when closed	3 months ago
tsnet_test.go	tsnet: ensure funnel listener cleans up after itself when closed	3 months ago