therealkenc

NTFS is a little more Linuxy now that Microsoft has come to a point of acceptance (after 20 [years](https://groups.google.com/forum/#!msg/comp.os.ms-windows.programmer.win32/D9JL39oEl-Q/wVOvLL0oQTgJ)) that symlinks [are a thing](https://blogs.windows.com/buildingapps/2016/12/02/symlinks-windows-10/#PL58s3SqvKTl0Me8.97). I'm holding out hope this continues...

Turns out (as with most things WSL) someone [already has](http://www.linuxtopia.org/online_books/network_administration_guides/samba_reference_guide/35_pam_12.html) for native. It would probably need some adaptation to feel at home on Windows, and I haven't made the effort...

> Try to connect to nc, on Windows with any browser, at the address 127.0.0.1:8080. Right; you aren't listening on ipv4 `127.0.0.1` in your repro.  If you try to...

> I wasn't sure if it was the same root cause as #4353 Your OP is fair game. #4353 was actually deemed addressed [in August](https://github.com/microsoft/WSL/issues/4353#issuecomment-526363584). I just don't have the...

Tag needs-investigation in the sense this needs a ruling on whether the current (circa 19640) behavior of the magic WSL localhost tunnel is by-design (by fiat), or should route ipv4...

> Would it be reasonable for WSL2 to route ipv4 127.0.0.1 to ipv6 ::1 automatically like Linux? Yes. RFC 6052 (...or something)

> Listening on http://127.0.0.1:3000 Get the server (by whatever means) to listen on `0.0.0.0:3000`. If that doesn't help, try WSL's IPv4 address instead of `localhost` in the Windows-side browser.

Very probably a recent(ish) regress because there'd be more screeching when WSL2 was released to Insiders last Spring, and these two (w/ #4780) came in back-to-back. > Windows Feedback Hub...

> is that the case for you @therealkenc or are you not able to boot with Hyper-V feature alone? I'm personally able to boot no problem. Haven't touched the Windows...

> I don't know what this means Me either. Mine looks like this FWIW.