Groups | Search | Server Info | Login | Register


Groups > comp.mobile.android > #148491

Re: Warning: If you use adb or stunnel & if you enable Hyper-V (e.g., WSL, Docker, VMs, etc.) you will be sorry

From Marion <marion@facts.com>
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-18 00:25 +0000
Organization BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID <100b9e7$2upp$1@nnrp.usenet.blueworldhosting.com> (permalink)
References (1 earlier) <m85nqbFg731U2@mid.individual.net> <vvkkel$i6v$1@nnrp.usenet.blueworldhosting.com> <m8p9faFl317U2@mid.individual.net> <10085cf$g9p$1@nnrp.usenet.blueworldhosting.com> <m8qq4qFsg3dU1@mid.individual.net>

Cross-posted to 3 groups.

Show all headers | View raw


On Sat, 17 May 2025 08:54:23 +0200, Arno Welzel wrote :


>> If people need to use Hyper-V, then they *must* reserve ports they want to
>> use *ahead* of time since Winnat reservation is essentially random (AFAIK).
> 
> You can also just disable the NAT and only use direct connections in the
> virtual machines in Hyper-V. This is why I suggested this *instead* of
> using WSL2 if you need a Linux VM in Windows - because WSL2 does not
> work without NAT.

I thank you for that information which will help others. 

Personally, I can't even spell Hyper-V as I have no idea what it is. 
All I know is I have to enable it whenever a program asks me to do that.

Looking up what you said (which requires more understanding than I own),
apparently Hyper-V is Microsoft's name for its virtual machine platform.

For that virtual machine to connect to the Internet, apparently it needs a
port to go through in order to get outside to the Internet. NAT takes care
of the pipe of the virtual machine port on one end and the real machine
port on the other end, apparently. 

Apparently your reference to "direct connections" is a bridge of some sort. 
That bridge has its own IP address, apparently, just like another computer.

So, I guess, the VM traffic goes out that bridge directly to the router.
Apparently that bridge isn't a physical device but a software construct.

Apparently that bridge is set up in the "Hyper-V Manager" (which I only
heard of for the first time at this moment in my search). 
 Hyper-V > Virtual Switch Manager > New virtual network > External > 
 Create Virtual Switch > {Name,Adapter,Sharing,VLAN ID,etc.}

 PS> Get-NetAdapter

 PS> New-VMSwitch -Name "<MySwitchName>" -NetAdapterName "<MyPhysicalAdapterName>" -AllowManagementOS $true

To validate:
  PS> Get-VMSwitch

Given there isn't a single concept above that I was aware of before you
posted your suggestion, am I correct in assuming the "software bridge" you
speak of is this External Virtual Switch I just created in Hyper-V
configured to bind to my physical network adapter?

If so, is my understanding correct that this virtual switch then handles
the task of bridging the network traffic between my VM and the physical
network?

Back to comp.mobile.android | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

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