3 ms·
Still no ipv6 support with WSL2 in windows. So, if you’re a Microsoft Windows dev in an ipv6 environment, you won’t make it too far.
by withinboredom 4y ago
Still no ipv6 support with WSL2 in windows. So, if you’re a Microsoft Windows dev in an ipv6 environment, you won’t make it too far.
- jeroenhd 4y agoQuite a strange limitation in my opinion. I understand that dealing with subnetting/host network rebinding to allow full IPv6 can be a challenge (especially if you're on DHCPv6 or some other manually managed thing instead of normal SLAAC) but surely Microsoft could use whatever NAT solution they use for IPv4 to work on IPv6 as well? Apparently support for the protocol can already be enabled (https://github.com/nathanchance/WSL2-Linux-Kernel/issues/25 https://github.com/nathanchance/WSL2-Linux-Kernel/issues/25). This makes it technically possible to use a WireGuard tunnel for IPv6 support, at least...
- withinboredom 4y agoHeh, yeah, I opened that issue. Nathan is awesome for maintaining that kernel.
- jeroenhd 4y agoHaha, I didn't even notice. I should clean my glasses!
- kavalg 4y agogot bitten by this recently. Another nail in the Microsoft Windows' coffin. It is such a fundamental thing and the fact that the issue has been open for ~2years is nothing short of pure shame.