Dave Anderson

IPv6 autoconfiguration depends on multicast, which WireGuard doesn't support. So, it's unlikely that any generic IPv6 autoconfiguration system will work over wireguard, unfortunately.

One important thing to note on the cryptography side, which may not be in the docs you got (it was a later implementation question and I'm not sure I backported...

Could you @ me when the PR is up, so I can see the AcceptHTTP changes you needed? I'm wondering if we can fix it upstream without importing all of...

FYI, late change to the Noise protocol: https://github.com/tailscale/tailscale/pull/4370 We now use the client capability version as the Noise handshake version, instead of having a separate version for Noise. That means...

A late testimony that this will make my life harder: inet.af/wf interacts with the windows filtering platform through cgo, which unusually requires that structs passed to it be allocated using...

> Thanks for the use case. To clarify: you're depending on `//go:notinheap` only as a safety aid during development? That is, if you were to strip out all the `//go:notinheap`...

I just came across KDL, and as it happens it's _exactly_ what I needed for a Go project of mine, for which I was in the middle of writing a...

@bradfitz remembers that Perkeep once hit something about maybe SOA records relating to custom DNS resolvers, and will add details here once dug up.

Also, disabling LLMNR globally didn't help, so it seems to be something else.

macOS only lets you have one VPN extension at a time, I believe. So, these are the symptoms of "we can't start IPNExtension because another one is already running". Unless...