I Wail, for My Tailscale Fails: How My Packets Got Dropped Beyond the Pale
1–4 of 4 posts
Re: I Wail, for My Tailscale Fails: How My Packets Got Dropped Beyond the Pale
#2Hey, anything other than your domain to submit?
> Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity.
Re: I Wail, for My Tailscale Fails: How My Packets Got Dropped Beyond the Pale
#3Hey, anything other than your domain to submit? > Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity. https://news.ycombinator.com/newsguidelines.html
I'll edit this and add more info. I'm not promoting anything here, I'm just detailing a chronicle with debugging tailscale and dropped packets, which I thought people would find interesting. I'll add more context in a sec.
Re: I Wail, for My Tailscale Fails: How My Packets Got Dropped Beyond the Pale
#4More context: Hi all! I ran into an issue with getting tailscale to work for larger payloads from my WSL (windows) box, and I detailed my journey on debugging what the issue was, in a pretty roundabout way. Towards the bottom I hit a huge wall in my investigation where I basically actually had to look up stuff and really learn beyond the abstraction I already knew, and then I try to explain it all. Would welcome any feedback here on the correctness specifically, just so I'm not internalizing any _wrong_ learnings. Thanks!