Denton Gentry
Denton Gentry
Unfortunately the CLI utility like `tailscale` on Linux doesn't exist in the Android app, and the Android equivalent of `tailscaled` doesn't listen on the interfaces it would need in order...
I can reproduce this (not using the Chrome extension, just seeing what https://cloudflare-quic.com/ says). With exit node enabled it is always HTTP/2. Without an exit node, after the first reload...
I think this happens because of the MTU: https://groups.google.com/a/chromium.org/g/proto-quic/c/uKWLRh9JPCo?pli=1 QUIC handshake is 1350 bytes with no-fragment set. An MTU of less than 1350 bytes results in the QUIC handshake being...
Using Firefox with no exit node, after a few refreshes I see it using HTTP/3. Using Firefox with an exit node, the first several refreshes after enabling the exit node...
Use of an exit node doesn't appear to be material to the issue, it is just the way to be able to use https://cloudflare-quic.com/ to test it.
Following up about MTU: we've added a TS_DEBUG_MTU environment variable. If set before starting tailscaled, such as in /etc/default/tailscaled on Linux systems, the tailscale0 MTU will be set to this...
https://github.com/tailscale/tailscale/pull/5915 first appeared in 1.34, released last week. Did it make a difference? MTU discovery is one of the factors in network throughput, likely to be following on after https://tailscale.com/blog/throughput-improvements/...
> should I even be explicitly adding tail74a3.ts.net and 100.100.100.100 to my search domains and nameservers, respectively? No, the Tailscale-provided search domain and resolver will be handled automatically and should...
The subnet routes are added to table 52 to avoid the risk of a local network, like a public Wi-Fi network, using the same IP addresses as an exported subnet...
There are two intertwined issues: - for tailnets which wish to allow it, permit nodes to communicate directly on the LAN without going through the advertised route from a subnet...