Groups | Search | Server Info | Login | Register
Groups > alt.comp.os.windows-11 > #19188
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Newsgroups | alt.comp.os.windows-11, alt.comp.os.windows-10, comp.mobile.android |
| Subject | Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry |
| Date | 2025-05-09 09:05 +0200 |
| Message-ID | <m85nqbFg731U2@mid.individual.net> (permalink) |
| References | <vve26p$6pf$1@nnrp.usenet.blueworldhosting.com> |
Cross-posted to 3 groups.
Marion, 2025-05-07 00:24: > Warning: If you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) on Windows, > and if you ever want to assign an outgoing port to any process (e.g., > stunnel, adb, etc.), then you will be a very unhappy person (for years!) if > you don't heed this warning outlined below. [...] > I never took a class in networking so I don't really know why you > have to do this - but all I know it not knowing this cost me zillions > of hours over the years of wasted debugging that knowing what is in this > one post would have saved me (and which is why I'm posting this for you). Well - since WSL2 provides the ability to access ports on the machine *inside* WSL2 as 127.0.0.1 from the *host*, this is the expected behaviour. If you don't like this - don't use WSL2 but instead Hyper-V only with a "real" virtual machine inside Hyper-V and a virtual network setup for Hyper-V which is shared with your host, for example 10.0.0.1/24 so you can access the virtual machines at 10.0.0.2 from your host with is 10.0.0.1 (in addition to its regular IP address in your network). Then the host won't have any blocked ports at all. To let the VM have access to the outside world, it can then also directly use the network card of the host as bridge and does not need NAT as well - so your host will then be visible as two machines, one is your host and the second one is the VM inside Hyper-V. -- Arno Welzel https://arnowelzel.de
Back to alt.comp.os.windows-11 | Previous | Next — Previous in thread | Next in thread | Find similar
Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Marion <marion@facts.com> - 2025-05-06 22:24 +0000
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Arno Welzel <usenet@arnowelzel.de> - 2025-05-09 09:05 +0200
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Marion <marion@facts.com> - 2025-05-09 10:12 +0000
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Arno Welzel <usenet@arnowelzel.de> - 2025-05-16 19:03 +0200
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Marion <marion@facts.com> - 2025-05-16 19:58 +0000
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Arno Welzel <usenet@arnowelzel.de> - 2025-05-17 08:54 +0200
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Marion <marion@facts.com> - 2025-05-18 00:25 +0000
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Arno Welzel <usenet@arnowelzel.de> - 2025-05-18 14:49 +0200
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Marion <marion@facts.com> - 2025-05-20 20:01 +0000
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Marion <marion@facts.com> - 2025-05-21 04:13 +0000
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Marion <marion@facts.com> - 2025-05-21 04:21 +0000
Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry Andy Burns <usenet@andyburns.uk> - 2025-05-21 07:57 +0100
csiph-web