Updated Tailscale 1.8 (markdown)

Brad Fitzpatrick 2021-05-06 07:52:38 -07:00
parent a43884ab55
commit 947596ae15

@ -1,15 +1,15 @@
# Bug fixes, improvements # Bug fixes, improvements
* Large effort to address DNS configuration issues and Magic DNS on all platforms. * Large effort to address DNS configuration issues and Magic DNS on all platforms.
* allow client access to exit node's public IPs * 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. * 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 * Support SCTP in port-based ACLs, in addition to TCP and UDP
* In magicsock if IPv4 and IPv6 have similar latency, prefer IPv6 * 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 doesnt involve the host IP stack. Only destinations running 1.8+ will respond. * Add `tailscale ping --tsmp w.x.y.z`, which sends a ping at a layer which doesnt 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 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 bugreport here just adds a known point in the logs. * 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 * 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. * 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
# Platform-specific # Platform-specific
## Linux ## Linux
@ -17,7 +17,7 @@
## Windows ## Windows
* Behavior change: ForceDaemon now off by default, use “tailscale up --unattended” to get previous behavior * 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
* MacOS systems can now serve as subnet routers and exit nodes using https://github.com/tailscale/tailscale/wiki/Tailscaled-on-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. * Synology systems can now serve as subnet routers and exit nodes.
# dgentry notes: # dgentry notes:
* Not mentioning file transfer, will be in early access for a while * Not mentioning file transfer, will be in early access for a while
* Not mentioning Split DNS, will introduce post 1.8.0 * Not mentioning Split DNS, will introduce post 1.8.0