You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using an exit node in linux, in this case fedora 41, connections to other nodes are not formed over ipv6 vs operating without an exit node. This is likely due to issues regarding gai.conf and the tailscale interface having a ULA. It seems that in later versions of glibc, gai.conf is removed?
This makes direct connections more difficult/impossible and makes latency far higher across continents.
Issue is not replicated across MacOS and I'm unsure about windows.
Steps to reproduce
Activate an exit node and run tailscale ping to nodes with dual stack. Compare this to without an exit node where connections are formed over v6.
Are there any recent changes that introduced the issue?
No response
OS
Linux
OS version
Fedora
Tailscale version
41
Other software
No response
Bug report
No response
The text was updated successfully, but these errors were encountered:
does not seem to happen on android either, I can't do tailscale ping with expliticit IP, but I have an exit node that has differing latency across ip versions
dolceAlka
changed the title
Tailscale does not use ipv6 in priority when using exit node
Tailscale does not use ipv6 to to other nodes when using exit node
Dec 30, 2024
What is the issue?
When using an exit node in linux, in this case fedora 41, connections to other nodes are not formed over ipv6 vs operating without an exit node. This is likely due to issues regarding gai.conf and the tailscale interface having a ULA. It seems that in later versions of glibc, gai.conf is removed?
This makes direct connections more difficult/impossible and makes latency far higher across continents.
Issue is not replicated across MacOS and I'm unsure about windows.
Steps to reproduce
Activate an exit node and run tailscale ping to nodes with dual stack. Compare this to without an exit node where connections are formed over v6.
Are there any recent changes that introduced the issue?
No response
OS
Linux
OS version
Fedora
Tailscale version
41
Other software
No response
Bug report
No response
The text was updated successfully, but these errors were encountered: