|
|
|
|
|
|
by ntauthority
1276 days ago
|
|
|
Using an issue reported (in a Linux compatibility layer, even!) with few to little root cause analysis as evidence a 'networking stack is bonkers' is a bit exaggerated - IPv6 in itself is also a bit wacky, and I've had similar issues exist in a variety of environments. As an opposite example, here's a Wine bug report of a Windows application failing to work in some network environments, but only if it in any way touches the Linux networking stack (such as using VirtualBox's soft NAT, or if running under Wine): https://bugs.winehq.org/show_bug.cgi?id=53346 I guess, in general, software (and networking) is 'bonkers'. |
|
|
It looks like its an issue with the bridge, nothing to do with WSL, but that is pretty much the only place on the internet to report it. The bridge is literally sending packets to the wrong interface (an interface that isn't even a part of the bridge!). Since it's closed source, no one except Microsoft can look into it.
But to figure out what was wrong took a really deep dive into Windows networking, and it is bonkers, absolutely bonkers. At least compared to every other networking stack I've ever deep dived into. Maybe if you spend enough time with it, everything else looks bonkers. So maybe you're correct:
> I guess, in general, software (and networking) is 'bonkers'.