tailscale/tsnet
shayne e109cf9fdd
tsnet/tsnet: clear ipn.ServeConfig on Up for tsnet apps (#7534)
We persist the ServeConfig, even for tsnet apps. It's quite possible for
the ServeConfig to be out of step with the code. Example: If you run
`ListenFunnel` then later turn it off, the ServeConfig will still show
it enabled, the admin console will show it enabled, but the packet
handler will reject the packets.

Workaround by clearing the ServeConfig in `tsnet.Up`

Signed-off-by: Shayne Sweeney <shayne@tailscale.com>
2023-03-11 16:07:22 -05:00
..
example ipn: add Funnel port check from nodeAttr 2023-03-11 11:20:52 -08:00
tsnet_test.go tsnet: only intercept TCP flows that have listeners 2023-03-07 15:48:49 -08:00
tsnet.go tsnet/tsnet: clear ipn.ServeConfig on Up for tsnet apps (#7534) 2023-03-11 16:07:22 -05:00