No network connection in any distribution under WSL 2 #5336

duncanmmacleod · 2020-06-04T14:04:51Z

Environment

Windows build number: 10.0.19041.0
Your Distribution version: Ubuntu-18.04
Whether the issue is on WSL 2 and/or WSL 1: WSL 2 only (Linux version 4.19.104-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Feb 19 06:37:35 UTC 2020)

Steps to reproduce

I have installed WSL 2 on a new Windows 10 Education machine managed by my employer (university) following the online instructions. Whenever I create a new distribution using WSL version 2 I have no network connection.

duncan@Macleod-XPS:/mnt/c/Users/spxdmm$ ping google.com
ping: google.com: Temporary failure in name resolution
duncan@Macleod-XPS:/mnt/c/Users/spxdmm$ ping 127.0.0.1
connect: Network is unreachable
duncan@Macleod-XPS:/mnt/c/Users/spxdmm$ ifconfig eth0
eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 00:15:5d:a5:38:8b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

duncan@Macleod-XPS:/mnt/c/Users/spxdmm$ cat /etc/resolv.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver 192.168.176.1

Gist of strace here: https://gist.github.com/duncanmmacleod/4a69a363bf990c3a0dead811b22ce6d5

If I use wsl --set-version to roll back the distribution to WSL 1 I get a network connection just fine.

Expected behavior

New distributions on WSL 2 have a working network connection out-of-the-box.

Actual behavior

See above

Thanks, sorry if this is a duplicate of an existing issue (I surely can't be the only one...)

The text was updated successfully, but these errors were encountered:

rescenic · 2020-06-04T20:48:11Z

Try network reset or allow in firewall.

duncanmmacleod · 2020-06-04T20:49:16Z

Can you be any more specific about how to do either of those things? I'm new to Windows (just migrating back from macOS).

onomatopellan · 2020-06-04T21:08:23Z

Try something like ping 216.58.192.164. Does it work?

duncanmmacleod · 2020-06-04T21:09:28Z

$ ping 216.58.192.164
connect: Network is unreachable

onomatopellan · 2020-06-04T21:17:21Z

See #4731

duncanmmacleod · 2020-06-04T21:20:00Z

Ok, looks like this is a duplicate of #4731, is that what you mean @onomatopellan?

onomatopellan · 2020-06-04T21:30:51Z

Hard to say. There are more threads with "Network is unreachable" where people tries to solving it in different ways like in #4275 (comment)

It depends of your networking configuration, if you are using some VPN, proxy configuration... Try any of the solutions of those threads and if nothing work the best you can do is post a link to a networking trace so the team can take a look at it.

duncanmmacleod · 2020-06-04T21:33:00Z

Thanks @onomatopellan, I don't have any special networking configuration, so will post a tracr using the feedback hub.

wi-ry · 2020-06-09T03:53:57Z

Try any of the solutions of those threads and if nothing work the best you can do is post a link to a networking trace so the team can take a look at it.

I’ve shared my network trace: https://aka.ms/AA8mo2v

WSL1 works fine, WSL2 does not. Downgrading from WSL2 to WSL1 restores connectivity.

ericct · 2020-06-09T08:50:04Z

Maybe related to #5286 ?

duncanmmacleod · 2020-06-09T09:13:47Z

Try any of the solutions of those threads and if nothing work the best you can do is post a link to a networking trace so the team can take a look at it.

https://aka.ms/AA8mo2v

@mrausnadian, 'my account doesn't have access to that feedback', can you please summarise the content of that link?

yooceii · 2020-06-10T00:40:39Z

I disabled the Hyper-v feature. The network backs to normal.

habamax · 2020-06-10T12:38:33Z

I disabled the Hyper-v feature. The network backs to normal.

How did you do it? If I disable it in windows features then wsl just doesn't run "The request is not supported".

rescenic · 2020-06-10T14:59:38Z

@habamax commented on Jun 10, 2020, 7:38 PM GMT+7:

I disabled the Hyper-v feature. The network backs to normal.

How did you do it? If I disable it in windows features then wsl just doesn't run "The request is not supported".

Convert the linux to WSL 1.

habamax · 2020-06-10T15:10:43Z

@habamax commented on Jun 10, 2020, 7:38 PM GMT+7:

I disabled the Hyper-v feature. The network backs to normal.

How did you do it? If I disable it in windows features then wsl just doesn't run "The request is not supported".

Convert the linux to WSL 1.

How does it solve the issue with wsl2?

PS, wanted to use wsl2 but it is not ready.

yooceii · 2020-06-10T16:58:54Z

@habamax commented on Jun 10, 2020, 7:38 PM GMT+7:

I disabled the Hyper-v feature. The network backs to normal.

How did you do it? If I disable it in windows features then wsl just doesn't run "The request is not supported".

Convert the linux to WSL 1.

How does it solve the issue with wsl2?

PS, wanted to use wsl2 but it is not ready.

You need to ensure the virtual machine platform is enabled, Check the #4840
Also, make sure the folder of the distro is not compressed or encrypted.

habamax · 2020-06-10T17:15:31Z

You need to ensure the virtual machine platform is enabled, Check the #4840
Also, make sure the folder of the distro is not compressed or encrypted.

Well, I can start wsl2 but again there is no internet connection while wsl1 has it.

Anyway, thanks, will continue using wsl1.

archonic · 2020-06-15T17:26:40Z

@duncanmmacleod Did you ever solve this? I'm experiencing the same exact issue on 19041.329. I hardly consider using WSL 1 a reasonable solution.

I'm also finding that setting the name server and adding generateResolvConf = false to /etc/wsl.conf has no effect - it gets regenerated after every restart.

duncanmmacleod · 2020-06-15T17:29:30Z

@duncanmmacleod Did you ever solve this? I'm experiencing the same exact issue on 19041.329. I hardly consider using WSL 1 a reasonable solution.

No, I submitted the relevant feedback reports to Microsoft and am waiting for a response.

archonic · 2020-06-15T18:36:09Z

I've given up on WSL completely. WSL 2 has network adaptor issues and WSL 1 has no docker integration. It's amazing that despite having a fully dockerized environment, I cannot work on Windows.

majmercado · 2020-06-18T17:16:58Z

In my case it was the firewall of my antivirus suite that is blocking the connection. Try disabling your antivirus' firewall (or the whole suite) and retry the connection.

The bridge network via your primary physical connection that provides external network access to the WSL guest should work out of the box.

On my case it is norton's firewall that is blocking the connection. It is quite hard to see since there are no notifications that the connection is being blocked. I just added at WSL guest hardware / MAC address via the device trust list.

pavel-a · 2020-07-05T11:15:00Z

Similar issue here: after upgrade to ver 2004 and wsl 2 - internet (or network) non-functional in any distro.

In Ubuntu 18,04 (restored from backup made before update to wsl 2) : DNS resolution fails, but ping to numeric address works. Maybe related to change in resolv.conf behavior.
Debian freshly installed from Store after upadte to 2004: even ping to numeric address (8.8.4.4) fails
After reinstalling these two distros with --version 1 , dns works in both.

My network config is very simple : plain GB ethernet and (disabled) wi-fi; no any 3rd party network or "security" stuff.

rescenic · 2020-07-05T12:17:51Z

@pavel-a

=============================================================================
FIX WSL2 NETWORKING IN WINDOWS 10
=============================================================================
cmd as admin:
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns

Windows Search > Network Reset

Restart Windows
-----------------------------------------------------------------------------

OR

# Fix network issues
# Delete auto-generated files
[root@PC-NAME user]# rm /etc/resolv.conf || true
[root@PC-NAME user]# rm /etc/wsl.conf || true

# Enable changing /etc/resolv.conf
# Enable extended attributes on Windows drives
[root@PC-NAME user]# cat <<EOF > /etc/wsl.conf
[network]
generateResolvConf = false

[automount]
enabled = true
options = "metadata"
mountFsTab = false
EOF

# Use google nameservers for DNS resolution
[root@PC-NAME user]# cat <<EOF > /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
EOF

Exit Linux WSL

cmd as admin:
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns

Windows Search > Network Reset

Restart Windows

md-ziauddin · 2020-07-12T20:00:57Z

@pavel-a

=============================================================================
FIX WSL2 NETWORKING IN WINDOWS 10
=============================================================================
cmd as admin:
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns

Windows Search > Network Reset

Restart Windows
-----------------------------------------------------------------------------

OR

# Fix network issues
# Delete auto-generated files
[root@PC-NAME user]# rm /etc/resolv.conf || true
[root@PC-NAME user]# rm /etc/wsl.conf || true

# Enable changing /etc/resolv.conf
# Enable extended attributes on Windows drives
[root@PC-NAME user]# cat <<EOF > /etc/wsl.conf
[network]
generateResolvConf = false

[automount]
enabled = true
options = "metadata"
mountFsTab = false
EOF

# Use google nameservers for DNS resolution
[root@PC-NAME user]# cat <<EOF > /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
EOF

Exit Linux WSL

cmd as admin:
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns

Windows Search > Network Reset

Restart Windows

Tried, did not work..
when i use ifconfig eth0 there is no ipv4

builditcal · 2020-07-13T22:30:11Z

Hey all,

Please try this if wsl2's internet stops working

sudo nano /etc/resolv.conf
Remove line out the nameserver nameserver 17...
add this new line nameserver 8.8.8.8
ctrl + o and ctrl + x to write a quit
sudo nano /etc/wsl.conf
Paste the following in:

[network]
generateResolvConf = false

ctrl + o and ctrl + x to write a quit
close WSL and reopen, hopefully the issue is fixed :)

The solution by above by Ziauddin02 resolves it in script form :)

BraINstinct0 · 2020-07-14T07:00:22Z

Hey all,

Please try this if wsl2's internet stops working

sudo nano /etc/resolv.conf

Comment out the nameserver #nameserver 17...

add this new line nameserver 8.8.8.8

ctrl + o and ctrl + x to write a quit

hopefully the issue is fixed :)

Worked! also swapping out 8.8.8.8 to any other (eligible?) DNS seems to work. Though, if I have set my Windows to use a different one, would it cause any problems?

fi11er · 2023-03-23T12:14:17Z

Hello! I have the same problem after KB5023696 update. Is there any official microsoft ticket I can watch? Looks like this bug is critical

ppnoufal · 2023-09-19T01:56:19Z

Fixes above solve the connectivity issues when you ant to access resources on the Internet. It does not offer a solution when you want WSL to host services, and amongst them when you want to access desktop with X.

The problem is that by default, the internal network is NATted, with a dynamic IP which changes each time WSL is restarted. In order to avoid this, you have to select the external network, and choose the network interface you use to connect to the Inter,et, ethernet or Wifi. Once done, your WSL will have to change the IP address to a fixed IP in the external network by eans of systemd network configuration. I tried that, and it works. If you are interested, I have step by step instructions to achieve it.

Hi, could you please provide me the steps

wesleysmitthe · 2023-09-19T18:50:29Z

Hi, I just changed the DNS resolver in the file /etc/resolv.conf, and it worked for me.

sudo nano /etc/resolv.conf

# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /># [network]
# generateResolvConf = false
nameserver 8.8.8.8

https://learn.microsoft.com/en-us/answers/questions/853140/wsl-2-internet-connectivity-is-gone

craigloewen-msft · 2023-09-19T21:21:42Z

Hi folks, we have put out a new update that aims to address networking issues in WSL. In your .wslconfig file you can set experimental.networkingMode=mirrored, as well as some other key settings that should improve your network compatibility! Please try them out and let us know what you think.

More info on this release and the changes can be found here in the blog post.

Please note: You need to be on a Windows Insiders version to use the new networking settings (Any channel of Windows Insiders will do, including release preview). If you see the "These are not supported" messages it means that your current Windows version doesn't have support, and you will need to upgrade. These features will eventually be coming to Windows 11 22H2.

vishwa3 · 2023-09-26T17:01:13Z

I am also facing this issue and have tried most of the solutions like changing nameserver in resolv.conf as well as commands to reset stuff but no luck - Not only this but previously too faced issues with wsl which resulted in re-imaging the system but it's too time consuming to keep on debugging network errors and try stuff rather than concentrate on my actual tasks - time to convince my lead and manager to maybe move away from Wsl - so many people are facing these issues , but still no clear solution - not everyone is a network wizard to resolve issues like these

jn-simonnet · 2023-09-27T04:20:19Z

Given the exchange above, I am publishing what I did to solve the isue. The key is an action in Hyper-V manager to change networking options.
A word of caution : I have not recently verified if this still works. My solution dates back December 2022.

Install Ubuntu with an IP in external network on WSL2 V2-summary.pdf

Elektronenvolt · 2023-09-28T11:51:09Z

@vishwa3 - try this - may your Windows Firewall blocks DNS.

#5336 (comment)
New-NetFirewallRule -DisplayName "WSL allow in" -Direction Inbound -InterfaceAlias "vEthernet (WSL)" -Action Allow

vishwa3 · 2023-09-28T17:46:08Z

I am also facing this issue and have tried most of the solutions like changing nameserver in resolv.conf as well as commands to reset stuff but no luck - Not only this but previously too faced issues with wsl which resulted in re-imaging the system but it's too time consuming to keep on debugging network errors and try stuff rather than concentrate on my actual tasks - time to convince my lead and manager to maybe move away from Wsl - so many people are facing these issues , but still no clear solution - not everyone is a network wizard to resolve issues like these

Thanks @Elektronenvolt and @jn-simonnet for your inputs - I managed to resolve the issue . I was on a corporate network with McAfee installed in my system - Raised a ticket with cyber security and got rid of it - The IT team had inadvertently pushed McAfee on my system and soon enough I started facing this issue-once McAfee was gone , WSL2 started pinging again , maybe I was unnecessarily critical of WSL2 though it has caused me issues before - Time to get back to my pending stories now 👍

marvinhinz · 2023-10-20T19:52:00Z

@vishwa3 - try this - may your Windows Firewall blocks DNS.

#5336 (comment) New-NetFirewallRule -DisplayName "WSL allow in" -Direction Inbound -InterfaceAlias "vEthernet (WSL)" -Action Allow

This solved my issue! Although i did not change anything, the network connectivity just stopped working, i was this close to reinstalling my wsl :D

vishwa3 · 2023-10-21T11:27:48Z

@vishwa3 - try this - may your Windows Firewall blocks DNS.
#5336 (comment) New-NetFirewallRule -DisplayName "WSL allow in" -Direction Inbound -InterfaceAlias "vEthernet (WSL)" -Action Allow

This solved my issue! Although i did not change anything, the network connectivity just stopped working, i was this close to reinstalling my wsl :D

Thanks @marvinhinz - My issue is resolved - please check -
https://github.com/microsoft/WSL/issues/5336#issuecomment-1739761276

craigloewen-msft · 2023-10-24T21:16:56Z

These new networking features are now available on the latest version of Win11 22H2!

Please make sure you're on the latest build to get these features, you can do that by clicking "Check for Updates" in Windows settings. You can check you have the right build by either ensuring you have KB5031354 installed, or run cmd.exe /c ver and ensure that your build number is 22621.2428 or higher (Including the minor build number which is after the . as this was a backport!)

keith-horton · 2023-11-14T07:21:31Z

We have updated the troubleshooting document for name resolution. There are configuration which can break DNS name resolution from a WSL container, and there is a work around for an HNS issue. This information can be found here: https://github.com/MicrosoftDocs/WSL/blob/main/WSL/troubleshooting.md#troubleshooting-dns-in-wsl

abdullah-bin-hasan · 2023-11-16T14:58:41Z

Doing these solved my problem:
Open Hyper-V Manager as administrator

Select your pc, open Virtual Switch Manager

Select WSL

Set to external network

Select the network card the traffic runs through

Then login to wsl2 terminal and configure an IP address. E.g.

sudo ip addr flush dev eth0
sudo dhclient eth0

This is where i found it: https://stackoverflow.com/a/62438375/10853017

jby · 2023-11-24T07:46:10Z

How did this turn into an issue about DNS?
I have the same problem as @duncanmmacleod in the original post.
Windows 10, WSL1, Ubuntu -> works fine
Convert to WSL2 -> No network traffic leaving the Ubuntu install, I don't even get a ping response from the Windows host - the Windows host can ping the WSL2 Ubuntu install though.

jby · 2023-11-24T07:58:09Z

The reported failures in DNS resolution is a result of the problem - not the cause...

Elektronenvolt · 2023-12-03T10:54:26Z

The reported failures in DNS resolution is a result of the problem - not the cause...

Can confirm this statement. In our case Windows Defender blocked incoming DNS for the WSL network adapter. In other cases here VPN clients caused DNS troubles, e.g.

jansturm1 · 2024-04-04T11:23:08Z

Only solution that worked for me (https://superuser.com/a/1671057/1662386):

Add the following to your <windows_user_profile>/.wslconfig:

[wsl2]
networkingMode=mirrored
Exit your WSL distribution

Run wsl --shutdown from PowerShell then restart WSL

Kieran-Sears · 2024-04-15T11:38:29Z

@duncanmmacleod Did you ever solve this? I'm experiencing the same exact issue on 19041.329. I hardly consider using WSL 1 a reasonable solution.

I'm also finding that setting the name server and adding generateResolvConf = false to /etc/wsl.conf has no effect - it gets regenerated after every restart.

I believe you need to include [network] above it, just having generateResolvConf = false doesn't cut it.

zeroarst · 2024-05-21T05:24:33Z

Only solution that worked for me (https://superuser.com/a/1671057/1662386):

Add the following to your <windows_user_profile>/.wslconfig:
[wsl2]
networkingMode=mirrored
Exit your WSL distribution
Run wsl --shutdown from PowerShell then restart WSL

I got

wsl: Mirrored networking mode is not supported, falling back to NAT networking

Any idea?

keith-horton · 2024-05-21T16:32:02Z

Mirrored Mode requires Windows 11 22H2 and higher. And the optional component "Virtual Machine Platform" is installed.

Thanks!

InternetPseudonym · 2024-05-21T16:42:05Z

Mirrored Mode requires Windows 11 22H2 and higher. And the optional component "Virtual Machine Platform" is installed.

Thanks!

oh, nice ... a version-locked feature and the the version it is locked to just so happens to be the most ad-ridden one of all time. I see the marketing department finally took full control. Well. It really "is" time to switch / virtualize / pirate winblows, then. Who would've thought.

Elektronenvolt · 2024-05-21T22:19:12Z

Mirrored Mode requires Windows 11 22H2 and higher. And the optional component "Virtual Machine Platform" is installed.
Thanks!

oh, nice ... a version-locked feature and the the version it is locked to just so happens to be the most ad-ridden one of all time. I see the marketing department finally took full control. Well. It really "is" time to switch / virtualize / pirate winblows, then. Who would've thought.

Well, I would call it 'dependency' 🧐But, what is 'version locked' in this case? Don't see it...

hub977 · 2024-07-30T03:43:37Z

我参考此链接得以在WSL2下恢复网络 https://learn.microsoft.com/zh-cn/windows/wsl/troubleshooting

1.允许 DNS 数据包共享访问的 HNS 防火墙规则可能无效，引用以前的 WSL 接口标识符。这是 HNS 中的一处缺陷，在最新的 Windows 11 版本已得到修复。在早期版本中如果发生这种情况，虽然不容易发现，但有一个简单的解决方法：

2.停止 WSL

wsl.exe –shutdown

3.删除旧的 HNS 防火墙规则。大多数情况下，此 Powershell 命令应正常工作：

Get-NetFirewallRule -Name "HNS*" | Get-NetFirewallPortFilter | where Protocol -eq UDP | where LocalPort -eq 53 | Remove-NetFirewallRule

4.移除所有 HNS 终结点。注意：如果使用 HNS 管理其他容器（例如 MDAG 或 Windows 沙盒），则还应停止这些容器。

hnsdiag.exe delete all

5.重新启动或重启 HNS 服务

Restart-Service hns #如果重启hns报错，需要依赖项，可重启电脑解决

6.重启 WSL 后，HNS 将创建新的防火墙规则，并正确面向 WSL 接口。

C:\Users\Administrator>wsl -l -v
NAME STATE VERSION

kali Stopped 2
C:\Users\Administrator>wsl
┏━(Message from Kali developers)
┃
┃ This is a minimal installation of Kali Linux, you likely
┃ want to install supplementary tools. Learn how:
┃ ⇒ https://www.kali.org/docs/troubleshooting/common-minimum-setup/
┃
┗━(Run: “touch ~/.hushlogin” to hide this message)
┌──(root㉿BOT)-[/mnt/c/Users/Administrator]
└─# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=48 time=59.3 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=48 time=64.6 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=48 time=58.2 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=48 time=101 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=48 time=61.6 ms
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 58.243/69.056/101.487/16.363 ms

如上ping 8.8.8.8可以通

hub977 · 2024-07-30T03:48:23Z

我参考此链接得以在WSL2下恢复网络 https://learn.microsoft.com/zh-cn/windows/wsl/troubleshooting

1.允许 DNS 数据包共享访问的 HNS 防火墙规则可能无效，引用以前的 WSL 接口标识符。这是 HNS 中的一处缺陷，在最新的 Windows 11 版本已得到修复。在早期版本中如果发生这种情况，虽然不容易发现，但有一个简单的解决方法：

2.停止 WSL

wsl.exe –关闭

3.删除旧的 HNS 防火墙规则。大多数情况下，此 Powershell 命令应正常工作：

Get-NetFirewallRule -名称“HNS*” |Get-NetFirewallPortFilter |其中 Protocol -eq UDP |其中 LocalPort -eq 53 |删除 NetFirewallRule

4.移除所有 HNS 终结点。注意：如果使用 HNS 管理其他容器（例如 MDAG 或 Windows 沙盒），则还应停止这些容器。

hnsdiag.exe全部删除

5.重新启动或重启 HNS 服务

Restart-Service hns #如果重启hns报错，需要依赖项，可重启电脑解决

6.重启 WSL 后，HNS 将创建新的防火墙规则，并正确面向 WSL 接口。

C：\Users\Administrator>wsl -l -v 名称状态版本

kali 已停止 2 C：\Users\Administrator>wsl ┏━（Kali 开发者的消息） ┃ ┃ 这是 Kali Linux 的最小安装，您可能 ┃ 想要安装补充工具。了解如何操作： ┃ ⇒ https://www.kali.org/docs/troubleshooting/common-minimum-setup/ ┃ ┗━（运行： “touch ~/.hushlogin” 隐藏此消息） ┌──（root㉿BOT）-[/mnt/c/Users/Administrator] └─# ping 8.8.8.8 PING 8.8.8.8 （8.8.8.8） 56（84）字节的数据。 8.8.8.8 的 64 个字节： icmp_seq=1 TTL=48 时间=59.3 毫秒 8.8.8 的 64 个字节： icmp_seq=2 TTL=48 时间=64.6 毫秒 8.8.8 的 64 个字节： icmp_seq=3 TTL=48 时间=58.2 毫秒 8.8.8.8 的 64 个字节： icmp_seq=4 TTL=48 时间=101 毫秒 8.8.8.8 的 64 个字节： icmp_seq=5 TTL=48 时间=61.6 毫秒 ^C --- 8.8.8.8 ping 统计--- 传输的 5 个数据包，接收 5 个，数据包丢失率为 0%，时间 4007ms RTT 最小值/平均值/最大值/MDev = 58.243/69.056/101.487/16.363 毫秒

如上ping 8.8.8.8可以通

本人系统环境为windows 10.0.19044
同时需要在 /etc/resolv.conf中写入servername 8.8.8.8
/etc/wsl.conf中写入
[network]
generateResolvConf = false

希望能帮助到你！！！

friedinando · 2024-08-11T22:41:06Z

In my case, this config fix the problem:

[wsl2]
networkingMode=mirrored
Exit your WSL distribution

tannath · 2024-10-10T08:33:15Z

Before use name like eth0 of device with internet access - check device name by:

  Get-NetAdapter

A working solution on mode bridged

On windows brand new virtual device (enable features of hyper-v in cli):

  Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
  Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Management-PowerShell

make by:

  New-VMSwitch -Name "External Device" -NetAdapterName eth0

And finally firewall, yep firewall ( your $clsid will be different - Name) :

  Get-NetFirewallHyperVVMSetting

  Name "{b26585cf-342b-471d-93a6-763ac5dba536}"
  Enabled               : True
  DefaultInboundAction  : Allow
  DefaultOutboundAction : Allow
  LoopbackEnabled       : True
  AllowHostPolicyMerge  : True

  $clsid = "{b26585cf-342b-471d-93a6-763ac5dba536}"

  Set-NetFirewallHyperVVMSetting -Name $clsid -Enabled True -DefaultInboundAction Allow
   -DefaultOutboundAction Allow -LoopbackEnabled True -AllowHostPolicyMerge True

On windows in file at c:/Users/<name_of_user>/.wslconfig

  [wsl2]
  networkingMode=bridged
  vmSwitch="External Device"
  dhcp=true
  ipv6=true

  [experimental]
  dnsTunneling=true
  firewall=true

ericct mentioned this issue Jun 9, 2020

[WSL2/Ubuntu/Debian/Kali] Network not configured #5286

Closed

therealkenc mentioned this issue Jun 16, 2020

Missing network connection in WSL2 after last (windows) update #5414

Closed

therealkenc mentioned this issue Jun 18, 2020

No network if %temp% moved #5437

Closed

therealkenc mentioned this issue Jun 29, 2020

Resolving error in Ubuntu 18.04 using WSL2 #5502

Closed

erik-brueggemann mentioned this issue Apr 13, 2023

Network doens't work with WSL 2 and Ubuntu #9926

Closed

2 tasks

This was referenced Dec 25, 2023

error: failed to synchronize all databases (no servers configured for repository) Athena-OS/athena-repository#6

Open

bug(docker): reNgine doesn't want to install in combination with WSL yogeshojha/rengine#956

Closed

github-actions bot mentioned this issue Feb 7, 2024

No network connection in any distribution under WSL2 #11131

Open

2 tasks

No network connection in any distribution under WSL 2 #5336

No network connection in any distribution under WSL 2 #5336

Comments

duncanmmacleod commented Jun 4, 2020

Environment

Steps to reproduce

Expected behavior

Actual behavior

rescenic commented Jun 4, 2020

duncanmmacleod commented Jun 4, 2020

onomatopellan commented Jun 4, 2020

duncanmmacleod commented Jun 4, 2020

onomatopellan commented Jun 4, 2020

duncanmmacleod commented Jun 4, 2020

onomatopellan commented Jun 4, 2020

duncanmmacleod commented Jun 4, 2020

wi-ry commented Jun 9, 2020 • edited Loading

ericct commented Jun 9, 2020

duncanmmacleod commented Jun 9, 2020

yooceii commented Jun 10, 2020

habamax commented Jun 10, 2020

rescenic commented Jun 10, 2020

habamax commented Jun 10, 2020

yooceii commented Jun 10, 2020

habamax commented Jun 10, 2020

archonic commented Jun 15, 2020 • edited Loading

duncanmmacleod commented Jun 15, 2020

archonic commented Jun 15, 2020

majmercado commented Jun 18, 2020

pavel-a commented Jul 5, 2020 • edited Loading

rescenic commented Jul 5, 2020 • edited Loading

md-ziauddin commented Jul 12, 2020

builditcal commented Jul 13, 2020 • edited Loading

BraINstinct0 commented Jul 14, 2020 • edited Loading

fi11er commented Mar 23, 2023

ppnoufal commented Sep 19, 2023

wesleysmitthe commented Sep 19, 2023 • edited Loading

craigloewen-msft commented Sep 19, 2023

vishwa3 commented Sep 26, 2023

jn-simonnet commented Sep 27, 2023

Elektronenvolt commented Sep 28, 2023

vishwa3 commented Sep 28, 2023

marvinhinz commented Oct 20, 2023

vishwa3 commented Oct 21, 2023 • edited Loading

craigloewen-msft commented Oct 24, 2023

keith-horton commented Nov 14, 2023

abdullah-bin-hasan commented Nov 16, 2023

jby commented Nov 24, 2023

jby commented Nov 24, 2023

Elektronenvolt commented Dec 3, 2023

jansturm1 commented Apr 4, 2024

Kieran-Sears commented Apr 15, 2024

zeroarst commented May 21, 2024

keith-horton commented May 21, 2024

InternetPseudonym commented May 21, 2024 • edited Loading

Elektronenvolt commented May 21, 2024

hub977 commented Jul 30, 2024

hub977 commented Jul 30, 2024

friedinando commented Aug 11, 2024

tannath commented Oct 10, 2024 • edited Loading

wi-ry commented Jun 9, 2020 •

edited

Loading

archonic commented Jun 15, 2020 •

edited

Loading

pavel-a commented Jul 5, 2020 •

edited

Loading

rescenic commented Jul 5, 2020 •

edited

Loading

builditcal commented Jul 13, 2020 •

edited

Loading

BraINstinct0 commented Jul 14, 2020 •

edited

Loading

wesleysmitthe commented Sep 19, 2023 •

edited

Loading

vishwa3 commented Oct 21, 2023 •

edited

Loading

InternetPseudonym commented May 21, 2024 •

edited

Loading

tannath commented Oct 10, 2024 •

edited

Loading