4 ms·
Last I heard[0] they were experimenting but hadn't shipped it. AFAIK their client still requires root, no? Running on wasm sounds awesome. This[1] looks like i
by anderspitman 5y ago
Last I heard[0] they were experimenting but hadn't shipped it. AFAIK their client still requires root, no?
Running on wasm sounds awesome. This[1] looks like it. Do you know how they're doing the actual networking? WebRTC tunnel?
[0]: https://news.ycombinator.com/item?id=24483173 https://news.ycombinator.com/item?id=24483173
[1]: https://twitter.com/bradfitz/status/1451423386777751561?lang=en https://twitter.com/bradfitz/status/1451423386777751561?lang...
- tptacek 5y agoYeah, their client is always going to require privileges, because it needs to enable every other program on the system to interact directly with remote hosts transparently. User-mode TCP/IP works for us because we own the client-side program that our users run to talk to stuff on Fly.io.
- bradfitz 5y ago> Last I heard[0] they were experimenting but hadn't shipped it. AFAIK their client still requires root, no? Tailscale's gvisor/netstack-based userspace networking mode has been supported and in wide use for quite some time. It's the default on Synology DSM7, for instance. You don't need root when you run tailscaled with `--tun=userspace-networking`. Peers can still connect inbound to the non-root tailscaled, but to connect _out_ to other peers, you need to use tailscaled's HTTP or SOCKS5 proxy, which are also flags to tailscaled, to specify what port they listen on.
- anderspitman 5y agoThanks for the update! Do you have any links that talk more about how the wasm stuff works? I'd love to read more about that.