Skip to content

Your Android phone and your Windows PC, working as one. Local-first, end-to-end encrypted, no account.

2.4 KB
Raw Blame

Connecting over Tailscale

Why it failed

Pairing links already carry the PC's tailnet address (pairing.rs, link_addrs keeps 100.x). But with Connect over mobile data (away mode) off, every address filter in the core used session::is_lan_ip, which rejected 100.64.0.0/10 as carrier CGNAT. So:

  • at node start and when away mode is turned off, stored tailnet addresses were purged from each peer's last_addrs (node.rs, Node::start, set_away_mode);
  • remember_addrs never fed them to the dialer, and direct_addrs never advertised them;
  • a session that did arrive over a tailnet path was refused (is_connection_allowed → "refusing session on non-LAN path").

mDNS doesn't cross Tailscale (no multicast), so with the address dropped there was nothing to dial. Tailscale's IPv6 range (fd7a:115c:a1e0::/48) is already a unique-local address and passed; most setups only route IPv4 by default. On Windows, the installer's firewall rule covers Private and Domain networks only; the Tailscale adapter is often a Public network.

Change

  • is_lan_ip also accepts tailnet ranges (is_tailnet_ip: 100.64.0.0/10, fd7a:115c:a1e0::/48). Every LAN-only filter now keeps tailnet addresses, so the PC's tailnet address from pairing (or learned from a session) is stored, dialed and allowed, with away mode off.

  • No new firewall rule. A Public-profile rule for 100.64.0.0/10 would also open the port to carrier and hotspot networks that use that range. Instead, mark the Tailscale network Private once, in an administrator PowerShell:

    Set-NetConnectionProfile -InterfaceAlias Tailscale -NetworkCategory Private
    

    The installer's existing rule (Private and Domain) then covers it.

Unchanged: pairing, device keys, QUIC end-to-end encryption, relays (still off unless away mode is on), mDNS.

Limits and follow-ups

  • Carrier CGNAT shares 100.64.0.0/10; such a direct path is now allowed too. It still needs the paired device's key and is rarely reachable.
  • A device paired before its tailnet address existed has no tailnet address stored. Re-pair once while Tailscale is up on both, or connect once on the LAN with Tailscale up so the session learns the path.
  • Follow-up: a "Connect by address" field (IP or MagicDNS name) in the apps, calling the existing Node::add_known_addrs; MagicDNS names need a resolve step before it.
  • The PC's QUIC port must stay stable (the node already reuses its last port).