On Wed, Apr 2, 2025 at 6:17 AM <fge...@gmail.com> wrote: > On Tue, Apr 1, 2025 at 7:57 PM Brad Fitzpatrick <b...@danga.com> wrote: > > > > > > > > On Tue, Apr 1, 2025 at 9:52 AM Jacob Moody <mo...@posixcafe.org> wrote: > >> > >> On 4/1/25 10:28, b...@danga.com wrote: > >> > Skip asked me to make Tailscale work on Plan 9. > >> > > >> > I tried, but ran into problems so I asked Russ for some help. > Together, we just got it all mostly working. > >> > > >> > Blog post 1 of 2 is now at > https://tailscale.com/blog/tailscale-enterprise-plan-9-support < > https://tailscale.com/blog/tailscale-enterprise-plan-9-support> > >> > >> Your post this morning was quite a present surprise. Got a couple > chuckles out of me as well. > >> I realize the date, but seeming that there was some code written for > this I suspect there's some truth to this > > > > > > Oh, it very much works. ;) > > > > And I was able to run it in a wasm emulator on the web ( > https://copy.sh/v86/?profile=9legacy&nojoke) and SSH into it. Tailscale > includes an optional built-in SSH server (tailscale up '--ssh'), so the SSH > server runs in tailscaled in Plan 9 in wasm in the browser and it all works > if you SSH from another machine running Tailscale on the same tailnet (a > private Tailscale network). > Truly a nojoke, thanks to all! > > It's probably only me, though I'd like to confirm, besides Brad who > could get this working in the copy.sh/v86 wasm emulator and what did > you do exactly? >
tailscaled in one rio window, and then `tailscale up '-ssh'` in another. term% ip/ping google.com > hangs and dns dies with > XX dns: checked 85 page table entries > dns XX: suicide: sys: trap: fault read addr=0x30382e pc=0x00014752 > so tailscale netcheck fails as well. > # ip/ping 8.8.8.8 works. The default internet relay run by somebody in the community for v86 is extremely throttled and restricted on how many concurrent connections you can do. I added some code to detect running in v86 and do fewer TCP connections (e.g. no racing various backends to see which connects faster) to try to stay within the limits, but some stuff is still buggy, like DNS .... I don't know what the Plan 9 DNS client code is doing. It doesn't seem to like the responses. But tailscaled has a fallback path to connect to the control plane for when DNS is down, so I often see that trigger and find its way to controlplane.tailscale.com that way. Once that's up, it gets all the IP addresses it needs via that controlplane TCP connection. It all works a lot better in qemu or with a dedicated wsproxy/WISP relay, but I ran out of time when getting one of those online for the blog post. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T4cecdedbabdedc00-M8ebd062b933fc65a35668162 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
