mirror of
https://github.com/tailscale/tailscale.git
synced 2025-05-19 16:58:31 +00:00
Updated Tailscale 1.6 (markdown)
parent
6ba1a00873
commit
5ecfe2d0b1
@ -1,17 +1,18 @@
|
|||||||
# Tailscale 1.6 Release Notes [DRAFT]
|
# Tailscale 1.6 Release Notes
|
||||||
|
|
||||||
## Headline Features
|
## Headline Features
|
||||||
|
|
||||||
* **Exit nodes**: route all your non-Tailscale internet traffic through another Tailscale node in your network; see https://tailscale.com/kb/1103/exit-nodes
|
* **Exit nodes**: route all your non-Tailscale internet traffic through another Tailscale node in your network; see https://tailscale.com/kb/1103/exit-nodes and https://www.youtube.com/watch?v=ETkqina913I
|
||||||
* **Tunneled IPv6**: Tailscale has been able to use IPv6 as a transport for the WireGuard traffic for some time, but now we also support IPv6 inside the tunnel. All nodes will have an IPv6 Tailscale address in addition to the normal 100.x.y.z Tailscale IPv4 (CGNAT) address.
|
* **Tunneled IPv6**: Tailscale has been able to use IPv6 as a transport for the WireGuard traffic for some time, but now we also support IPv6 inside the tunnel. All nodes that support IPv6 will have an IPv6 Tailscale address in addition to the normal 100.x.y.z Tailscale IPv4 (CGNAT) address.
|
||||||
* **Port mapping**: if your router supports NAT-PMP, Tailscale will now use it to make peer-to-peer connections. Many routers support this by default (such as Google Wifi). Others may require it be enabled (e.g. in pfSense/OPNsense or Unifi/Ubiquiti "Services"). For some routers it may be lumped together with a "UPnP" checkbox. For pfSense/OPNsense users in particular, enabling NAT-PMP is highly recommended to be able to get direct connections between Tailscale nodes.
|
* **Port mapping**: if your router supports NAT-PMP, Tailscale will now use it to make peer-to-peer connections. Many routers support this by default (such as Google Wifi). Others may require it be enabled (e.g. in pfSense/OPNsense or Unifi/Ubiquiti "Services"). For some routers it may be lumped together with a "UPnP" checkbox. For pfSense/OPNsense users in particular, enabling NAT-PMP is highly recommended to be able to get direct connections between Tailscale nodes.
|
||||||
* **Userspace networking** is now possible with `tailscaled` using `--tun=userspace-networking`, which doesn't require root.
|
* **Userspace networking** is now possible with `tailscaled` using `--tun=userspace-networking`, which doesn't require root.
|
||||||
|
* Known issue: userspace networking is not yet available on 32-bit CPUs, due to a bug in an upstream library. 32-bit support will be added in a future release.
|
||||||
* **SOCKS5 server**: the `tailscaled` binary now includes a SOCKS5 server. In particular, this allows a `tailscaled` using userspace networking to make outbound connections to other nodes in your Tailscale network, without your operating system's help.
|
* **SOCKS5 server**: the `tailscaled` binary now includes a SOCKS5 server. In particular, this allows a `tailscaled` using userspace networking to make outbound connections to other nodes in your Tailscale network, without your operating system's help.
|
||||||
* **Local API**: `tailscaled` has the start of a node-local API. Currently the only interesting call is the `whois` method, to look up the Tailscale owner of a `ip:port` that's hitting a local service. (which also works for incoming userspace-networking localhost-forwarded connections)
|
* **Local API**: `tailscaled` has the start of a node-local API. Currently the only interesting call is the `whois` method, to look up the Tailscale owner of a `ip:port` that's hitting a local service. (which also works for incoming userspace-networking localhost-forwarded connections)
|
||||||
|
|
||||||
## Bug fixes, improvements
|
## Bug fixes, improvements
|
||||||
|
|
||||||
* DNS fallback mechanism to let Tailscale start on systems with broken or unavailable DNS
|
* A DNS fallback mechanism lets Tailscale start on systems with broken or unavailable DNS (and potentially fix the DNS configuration, if you've configured Tailscale DNS settings).
|
||||||
|
|
||||||
## Platform-specific
|
## Platform-specific
|
||||||
|
|
||||||
@ -23,14 +24,14 @@
|
|||||||
- `tailscaled.exe` (the open source daemon that does all the networking)
|
- `tailscaled.exe` (the open source daemon that does all the networking)
|
||||||
- `tailscale.exe` (the open source CLI tool to control the daemon)
|
- `tailscale.exe` (the open source CLI tool to control the daemon)
|
||||||
- `tailscale-ipn.exe` (the GUI to control the daemon)
|
- `tailscale-ipn.exe` (the GUI to control the daemon)
|
||||||
* The Windows service is now named just "Tailscale" (previously it was "Tailscale IPN")
|
* The Windows service is now named just "Tailscale" (previously it was "Tailscale IPN").
|
||||||
* The installer & uninstaller have been cleaned up and should now work correctly on multi-user Windows machines.
|
* The installer & uninstaller have been cleaned up and should now work correctly on multi-user Windows machines.
|
||||||
|
|
||||||
### macOS
|
### macOS
|
||||||
|
|
||||||
* tailscaled now runs on macOS: https://github.com/tailscale/tailscale/wiki/Tailscaled-on-macOS
|
* tailscaled now runs on macOS: https://github.com/tailscale/tailscale/wiki/Tailscaled-on-macOS
|
||||||
* the network link monitor was rewritten on macOS and should now adapt to changes quicker and from more parts of Tailscale, notably when the network is entirely unavailable (e.g. wifi is off)
|
* the network link monitor was rewritten on macOS and should now adapt to changes quicker and from more parts of Tailscale, notably when the network is entirely unavailable (e.g. wifi is off).
|
||||||
* the Command-Q shortcut now works when the menu bar icon is open
|
* the Command-Q shortcut now works when the menu bar icon is open.
|
||||||
|
|
||||||
## Synology
|
## Synology
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user