Allow bridged networking for WSL 2

[cerebrate]

• Your Windows build number: 18970

Please allow the WSL 2 networking infrastructure to be configured for bridged mode, as well as the current NAT system.

Here are my reasons:

1. Simplicity. In my little home-office network here, I've got VMs, containers, a cluster, and an Azure virtual network; as such, I use bridging a lot, because what there's only one of is me. The flatter the network structure, the less time I have to spend playing network admin.

While the workaround to publish WSL 2-hosted services to the wider network (per #4150) does work for most protocols, it's also more overhead to keep track of, as is managing source/destination IP addresses in configurations with ever-shifting IP ranges (per #4467).

And since I have a /16 to play with, burning another IP address on WSL 2 isn't going to hurt.

2. IPv6, which at the moment the WSL Hyper-V infrastructure doesn't support, and which I'm using as the primary protocol on my network for everything that supports it. The reason I ask for it by this method and not a request for specific IPv6 support is because bridging also supports whatever other non-IPv4 protocols turn up tomorrow.

3. Incidentally fixes the other WSL IP address & Subnet is never deterministic (Constantly changing) #4467 problem; I too have had the problem of the WSL interface happening upon a choice of private IP range in use elsewhere on the network.

[therealkenc]

#4150 is the landing zone.

[colemar]

See my equivalent solution
#11632

[4-FLOSS-Free-Libre-Open-Source-Software]

Please allow the WSL 2 networking infrastructure to be configured for bridged mode, as well as the current NAT system.

Sad news from just released WSL v2.4.5 changelog:

Add user warning letting users know bridged networking will be deprecated

Bridged mode works very well as it is now in WSL-Version: 2.4.5.0