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.Exit nodes: route all your non-Tailscale internet traffic through another Tailscale node in your network see our documentation and the video demo.Is there a way to have one of these WSL2 Ubuntu Docker hosting systems on both my personal Tailscale network as well as the client's company Tailscale network? It is not super important, as both Tailscale networks have public Internet and I'll be synchronizing software via github, which will not use the Tailscale net anyway. Currently Docker is exposing the WSL2 Ubuntu hosted Docker container apps to different localhost:ports and the Tailscale IP address enables Tailscale network access fine. Perhaps these systems just need some configuration I'm lacking to get Tailscale to work on these other prompts? Any advise here?Ĭonsidering that the WSL2 instances are virtual machines, would I install tailscale on them to make them visible (as independent machines) on the Tailscale network? It does not seem like I need to. Also noticed that after installing on these Win10/11 systems, the two systems that also have WLS2 Ubuntu instances (for Docker) do not have the Tailscale command line available from their Ubuntu prompts. I've noticed the Tailscale command line (CL) does not work in the Windows Terminal running an ordinary command prompt - but an ordinary command prompt window does have the Tailscale command line. I also will have a server with software for that client that is currently on my Tailscale network, and I want to place it on their Tailscale network too. I'm a developer, and planning on placing a private client on a separate Tailscale network for their small company. I have a series of personal systems all using Tailscale.
0 kommentar(er)
