Easiest WSL2 Bridge Network (without Hyper-V Virtual Network Manager)

Burning a Wireless Router - YouTube
Grilling a Linksys. Delicious…

I am testing certbot locally with Create-React-App, but I’m using WSL2. Little did I know, the networking for Ubuntu in WSL2 is a little strange when coming from your typical systemd-network, NetworkManager, ifupdown, <insert your favorite networking API>

Apparently, the networking is taken care of in the lxssManager service (you can reveal it / restart it, etc. in task manager – ctrl-shift-esc -> services). This is because WSL doesn’t have an init system, unless you get some kind of hack to give you a systemd-ish responsive system – I’ve heard of something called ‘genie’, but I haven’t wanted to try it, since I’m trying to do WSL the “right” way ๐Ÿ˜‚

Anywho, if you want an IP from your WSL installation that’s in the same subnet as your LAN, you’re out of luck, since the IP address supplied to your WSL instance is provided through NAT. Some threads I was scanning while looking for a solution talked about installing Hyper-V Virtual Network Manager, but wanting to keep things as light as possible, I have no interest in installing Hyper-V or any of its tools just to get a bridge network setup for WSL.

So I poked around the Network Connections in the Control Panel – this can be revealed by searching for Control in the start menu (it’s been getting progressively more hidden every release since the introduction of the UWP “Settings” app). Once you’re in there, go to Control Panel\Network and Internet\Network Connections (you can paste that line straight in the address bar) and look at what you’ve got. You should see something like this:

Control Panel Network Connections – quaint, isn’t it?

Although it’s likely you won’t have a “Network Bridge”… yet.

Here’s what to do:

Highlight your Ethernet (or WIFI) connection (or both) and the “vEthernet (WSL)” adapter (can select multiple by holding down CTRL while clicking on them), then right-click and select “Create Bridge” from the menu.

That’ll take a minute, but should leave you with this thing:

network bridge software adapter (Windows 10 control panel)

One of the threads I read said you have to restart after creating this thing, but that was not my experience. If you’re having weird networking issues you can’t figure out, you might want to give that a shot.

Then once you have it bridging your WSL adapter with your choice of wired-NIC or WIFI, head over to your bash prompt and set the adapter – note, my LAN’s subnet is, you’ll want to adjust that for whatever yours is:

 sudo ip addr flush dev eth0
 sudo ip addr add dev eth0
 ip addr show dev eth0
 sudo ip link set eth0 up
 sudo ip route add default via dev eth0
 ip route show
 ping google.com

So I’ll run through these real quick:

First you flush your old NAT ip settings, then you assign an address to your WSL adapter. I just picked one at random, but I’d definitely recommend checking to make sure you don’t have the IP address assigned first (try an IP scanner, like arp-scan, or something in Windows – note: I always get horribly paltry results with arp -a for some reason).

Give your WSL eth0 adapter the IP in CIDR notation, then set it to up so you can create a route for it. Create the route to your local gateway (e.g. or whatever yours is…)

Show that your address has been created, the default route has been created, then I like to ping a local machine like my gateway, then something that requires name resolution (here I used google).

Funny thing is, that actually worked before setting up the DNS resolver file, but you have to do that next. I don’t think it was pinging using ipv6, so that doesn’t explain why it worked – probably some weird Windows networking dichotomy, but sure enough, nothing else will really work in name resolution land beyond that, so it’s time to do the next step…

You’ll want to move the /etc/resolv.conf file to /etc/wsl.conf (unless you already have a wsl.conf file, of course – but it’s not created by default). I just invoked # mv /etc/resolv.conf /etc/wsl.conf since it already had the lines I had to add to wsl.conf in it, and I was about to replace it anyway…

Make your /etc/wsl.conf file look like this:

โ””โ”€ โ–ถ cat /etc/wsl.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
generateResolvConf = false

Then create an /etc/resolv.conf file using your favorite DNS servers (,,, etc.) I have local DNS, so here’s mine:

# echo 'nameserver
> nameserver
> search webtool.space' > /etc/resolv.conf

Run something like # apt update to make sure stuff’s resolving now. In my case it was all good.

Note: These ip commands are ephemeral, so you’ll probably want to do some research into how to making them more permenant. I literally put that first block of ip commands in a script to run for when I come back after a restart, because I’m almost 100% certain all this setup will be lost.

One really interesting caveat is that I noticed the Network Bridge in the Control Panel didn’t include the “vEthernet WSL” adapter when I restarted. The bridge was still there, but only had my Ethernet adapter in it, so I had to manually add the WSL adapter again manually in properties.

There’s apparently two config files – one’s the /etc/wsl.conf file we just created, the other is C:\Users\YourUserName\.wslconfig

Unfortunately, the /etc/wsl.conf file is pretty limited as to network config – I did add the generateHosts = false line in mine, because my /etc/hosts had a bunch of weird Windows-only subdomains created by programs that are totally unnecessary to have in Linux, but there’s a lot of other neat stuff in there related to selective case sensitivity, mounting different filesystems, etc. you might want to check out.

So I’m still searching for ways to make this permanent, but once I figure it out, I’ll come back and finish this post. Might have to send an issue to the devs over on GitHub, but I’ll get this working eventually. For now, adding WSL back in the bridge if I restart and running my script isn’t that big of a deal.

Update: This post is a small part of a comprehensive project I was working on. So far, I have posted my raw notes for others to scour if they want to try and re-create the environment: https://develmonk.com/2021/06/05/raw-notes-from-creating-a-local-dev-and-build-https-server-for-create-react-app-using-nginx-and-certbot/

Author: averyfreeman

Recovering zfs evangelist. Random tech tip disseminator. React/Next.JS site developer, but currently only in spare time. Previously resided: Oakland, SF, Tokyo. Now near Seattle, loving vote by mail.

21 thoughts on “Easiest WSL2 Bridge Network (without Hyper-V Virtual Network Manager)”

  1. Thanks averyfreeman for this great tutorial which worked out perfectly for me on Windows 10.
    I just wanted to add, that this is not the case for Windows 11 anymore. There, in the control panel the virtual network adapters are not shown anymore, they are shown in the task manager and when doing ipconfig /all but not in the control panel. I don’t know if this is a bug (or a feature) and had to use the Hyper-V Manager on Windows 11 to bridge WSL to my physical network.
    What I did not try is to bridge the network adapters using powershell…

  2. I can’t see vEthernet(WSL) inside menu Control Panel\Network and Internet\Network Connections.

    How to show it?

    1. I had to look this up, honestly, because I didn’t have it either and wasn’t sure why. Apparently it’s part of the Sandbox feature (?). Here’s how I got it installed:
      Steps to install Windows Sandbox from control panel + programs and features

  3. I stumbled into this, and this was great! Solved one problem, created another. I am unable to access my WSL2 windows host machine via IP this way. Any thoughts on that?

  4. This. This is exactly what I needed. So much more intuitive and honestly more robust than the other solutions to this nightmare of a design flaw. Everything works perfectly as it should, thank you so much for this!!

  5. How did you resolve the issue that as soon as you bridge the WSL vEthernet adapter to the actual ethernet adapter in windows, windows seems to no longer know how to reach the internet? I had to remove the two adapters from the bridge to get internet working again on the WSL host pc.

    1. Make sure “ethernet” is the one that “wsl” is bridged to, not the other way around, for starters. Then, if you still don’t have connectivity, check and see that your /etc/wsl.confa file has sane network defaults, like this:

      hostname = wsl-pawn-sacrifice
      generateHosts = false
      generateResolvConf = false

      More on wsl.conf here: https://learn.microsoft.com/en-us/windows/wsl/wsl-config#example-wslconf-file

      Make sure you have /etc/resolv.conf file and set it to your DNS of choice, like inside is a line that says:

      That ought to do it, but you can also check /etc/hosts and give it the names of some things you want it to be able to reach with local DNS resolution, like: localhost localhost.localdomain gateway gateway.localdomain

      and so on… Good luck!

  6. Also an easy way that still works since windows NT4:
    – open ‘windows run’ (shortcut: Win +r)
    – type ‘ncpa.cpl’ en press

    As an added bonus the run box remembers your command, so next time you can just look it up.
    There is many more control options you can open directly: diskmgmt.msc, taskmgr, services.msc and so on

  7. hi, thanks so much for your tutorial, it helps me a lot!

    maybe do you have a final solution for this?:
    AFAIK you have to re-add WSL NIC in control panel every time you reboot (through the right-click -> properties menu) โ€“ trying to work around this, but havenโ€™t found a solution yet as of 8am 6-5-202

    thanks in advance

    1. Yes, I did notice having to do this when I ran this configuration. I am mostly running Arch Linux bare metal instead of WSL these days, so I apologize for not having found a solution. Best regards!

  8. First thank you soo much as this article was extremely helpful. Alter `.wslconfig` is only possible under windows 11. To this day, it is not work as it should under Windows 10. Which drive me to search for another method and I got across yours.

    Because I had few fringe issue such as speed and WSL launch time when config `/etc/wsl.conf`, I wrote this script which might be useful instead of manually config the `nameserver` manually.

    In `~/.bashrc`:
    # Check if the flag file exists
    if [ ! -f /tmp/my_command_executed ]; then
    # Run your command

    # Create the flag file in /tmp to indicate that the command has been executed
    touch /tmp/my_command_executed
    In `renetwork.sh`:
    sudo sed -i ‘/nameserver/ s/\(nameserver \)[0-9.]\+/\1192.168.1.1/’ /etc/resolv.conf
    sudo ip addr flush dev eth0
    sudo ip addr add dev eth0
    ip addr show dev eth0
    sudo ip link set eth0 up
    sudo ip route add default via dev eth0
    ip route show
    ping -c 3

    # edit (moderator): 20231218 – changed “lunch time” to “launch time”. Great submission, thank you!

  9. This is exactly what I wanted for my sshuttle .
    adding this route in Windows,
    route add mask
    will route all traffic via WSL–Shuttle from Windows.

  10. Thanks for this info! Very very helpful and much simpler than other solutions. I have a script running in WSL to configure the IP address after reboots, however I noticed that the network bridge also does not persist across boots. Is there anyway to have the network bridge to vEthernet (WSL) persist?

    1. Sorry, I haven’t used WSL extensively in quite some time, as I’ve moved to an Arch Linux daily driver. I do seem to remember having to re-create the bridge on each login, though. If you could scope the powershell commands to do it, you could create a script and run it on login. I’d love to see what you come up with if you work it out!

Leave a Reply

Your email address will not be published. Required fields are marked *