Skip to content

Conversation

@istathar
Copy link

If we are on a machine where OpenVPN has brought an interface up we want to explicitly use it by preference to Tailscale identifying the system's idea of the default route.

We identify OpenVPN by the combination of a utunN device being present, and it having routes 0.0.0.0/1 and 128.0.0.0/1, being the two def1 half routes that the OpenVPN client installs on Macs. This allows Tailscale to reach the internet in a situation where the OpenVPN interface is the only actual viable pathway to the outside, so that Tailscale can then function as an overlay network as intended.

Closes #16652

If we are  on a machine where OpenVPN has brought an interface up we
want to explicitly use it by preference to identifying the system's idea
of the default route.

We identify OpenVPN by the combination of a utunN device being present,
and it having routes 0.0.0.0/1 and 128.0.0.0/1, being the two `def1`
half routes that the OpenVPN client installs on Macs. This allows
Tailscale to reach the internet and then function as an overlay
network.

Closes tailscale#16652

Signed-off-by: Andrew Cowie <andrew.cowie@apkudo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FR: Tailscale needs to work on MacOS when connected over OpenVPN

1 participant