Aaron Klotz 659e7837c6 health, ipn/ipnlocal: when -no-logs-no-support is enabled, deny access to tailnets that have network logging enabled ...

We want users to have the freedom to start tailscaled with `-no-logs-no-support`,
but that is obviously in direct conflict with tailnets that have network logging
enabled.

When we detect that condition, we record the issue in health, notify the client,
set WantRunning=false, and bail.

We clear the item in health when a profile switch occurs, since it is a
per-tailnet condition that should not propagate across profiles.

Signed-off-by: Aaron Klotz <aaron@tailscale.com>

2022-11-29 11:42:20 -06:00

..

healthmsg

cmd/tailscale: make "up", "status" warn if routes and --accept-routes off

2022-11-11 10:56:50 -08:00

health_test.go

health: add Warnable, move ownership of warnable items to callers

2022-11-13 08:00:27 -08:00

health.go

health, ipn/ipnlocal: when -no-logs-no-support is enabled, deny access to tailnets that have network logging enabled

2022-11-29 11:42:20 -06:00