From 947596ae15a129ab847bfeac177c3ef18ab4c62f Mon Sep 17 00:00:00 2001 From: Brad Fitzpatrick Date: Thu, 6 May 2021 07:52:38 -0700 Subject: [PATCH] Updated Tailscale 1.8 (markdown) --- Tailscale-1.8.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/Tailscale-1.8.md b/Tailscale-1.8.md index 5b07ea2..f1410bb 100644 --- a/Tailscale-1.8.md +++ b/Tailscale-1.8.md @@ -1,15 +1,15 @@ # Bug fixes, improvements + * Large effort to address DNS configuration issues and Magic DNS on all platforms. * allow client access to exit node's public IPs * Tailscale up command now warns when options are being changed by omission. For example if one had used `tailscale up --advertise-route=192.168.0.0/24` and then uses `tailscale up --advertise-exit-node` it will notice and warn that the advertise-route would be removed. * Support SCTP in port-based ACLs, in addition to TCP and UDP * In magicsock if IPv4 and IPv6 have similar latency, prefer IPv6 -* Add `tailscale ping -tsmp w.x.y.z`, which sends a ping at a layer which doesn’t involve the host IP stack. Only destinations running 1.8+ will respond. -* Add add `tailscale ip [-4] [-6]` command, suitable for use in shell scripts to retrieve the Tailscale IP addresses. -* add `tailscale bugreport` command to log a timestamp, use shortly after a problem occurs to make it easier for support@tailscale.com to find. Note that you do still need to send email or file a bug, the bugreport here just adds a known point in the logs. +* Add `tailscale ping --tsmp w.x.y.z`, which sends a ping at a layer which doesn’t involve the host IP stack. Only destinations running 1.8+ will respond. +* Add add `tailscale ip [-4] [-6]` command, suitable for use in shell scripts to retrieve Tailscale IP addresses of the local node or peers. +* add `tailscale bugreport` command to log a timestamp, use shortly after a problem occurs to make it easier for support@tailscale.com to find. Note that you do still need to send email or file a bug; the new `bugreport` just adds a known point in the logs so support can find it easily. * Add `tailscale logout` command -* When run with `--tun=userspace-networking --socks5-server=...` tailscaled can now be a SOCKS5 proxy for all addresses not just Tailscale addresses. -* fix `tailscale status --json` AuthURL field +* When run with `--tun=userspace-networking --socks5-server=...`, `tailscaled` can now be a SOCKS5 proxy for all addresses not just Tailscale addresses. # Platform-specific ## Linux @@ -17,7 +17,7 @@ ## Windows * Behavior change: ForceDaemon now off by default, use “tailscale up --unattended” to get previous behavior -* Windows systems can now serve as subnet routers and exit nodes. cmd.exe must be used to enable this: `tailscale up --advertise-exit-node` or `tailscale up --advertise-route=192.168.1.0/24` +* Windows systems can now serve as subnet routers and exit nodes. As this support is new, there's no GUI support yet and the CLI must be used to enable it. From `cmd.exe`, run `tailscale up --advertise-exit-node` or `tailscale up --advertise-route=192.168.1.0/24` ## MacOS * MacOS systems can now serve as subnet routers and exit nodes using https://github.com/tailscale/tailscale/wiki/Tailscaled-on-macOS @@ -29,7 +29,6 @@ * Synology systems can now serve as subnet routers and exit nodes. - # dgentry notes: * Not mentioning file transfer, will be in early access for a while * Not mentioning Split DNS, will introduce post 1.8.0