Brad Fitzpatrick

@danderson recently added some host IPv6 probing in c1cb3efbba1f4bf854110e26df900b102357bd6a. If we wanted, we could only conditionally provide AAAA records in MagicDNS if it looks like the host would support it.

@danderson, yeah, I was just thinking about that. One option is we do it per-user, not per-tailnet, more like sharing.

API stuff, from their curl-to-bash script https://mullvad.net/media/files/mullvad-wg.sh .... ``` $ curl -LsS https://api.mullvad.net/public/relays/wireguard/v1/ | jq . { "countries": [ { "name": "Australia", "code": "au", "cities": [ { "name": "Melbourne", "code":...

/cc @danderson

I'm not sure what this bug was about. @12nick12, what did you expect to happen? What does "would make it start automatically" mean? Connect to a tailnet? Which? Did you...

Unlike our general policy of assuming nothing, on Android (at least Google Android) we can assume Google public DNS as the fallback even on old versions.

`advertise-routes` should work fine on DSM7 (for TCP and UDP, but not ICMP). It's `accept-routes` that doesn't work on DSM7.

Update: we've published https://tailscale.com/kb/1152/synology-outbound/ for instructions with how to do outbound connections from Synology (with DSM7).

@Ciechom, we're waiting for Synology to release it.

We've (mostly @twitchyliquid64) fixed a bunch of DNS stuff recently since 1.22.x. 1.26.0 is coming out soon. Perhaps Monday. This sounds a lot like something that was recently fixed.