No network access from WSL/Ubuntu

sbhatti534602210 commented 3 years ago

Microsoft Windows [Version 10.0.19043.1081] Ubuntu 20.04.2 LTS

I worked through the instructions for installing wsl for windows 10, from: https://docs.microsoft.com/en-us/windows/wsl/install-win10

However, I cannot connect to the internet from Ubuntu. I switched off the firewall as suggested here: https://docs.microsoft.com/en-us/windows/wsl/faq#why-do-i-not-have-internet-access-from-wsl-

But still could not connect.

There are a few things I have tried already but they did not resolve the problem (see below). As in the FAQ page: https://docs.microsoft.com/en-us/windows/wsl/faq#where-can-i-provide-feedback- I raised this through the issues tracker but did not get any response. Can someone help with this, please? I don't know why my previous request was closed without any response.

Thanks!

From Ubuntu terminal I tried to install:

curl https://get.volta.sh | bash (6) Could not resolve host: get.volta.sh

so I tried: ping 8.8.8.8 ping: connect: Network is unreachable

Some of the troubleshooting steps I have tried (which did not work)

Disabled the firewall.
Re-installed ubuntu.
BT (my internet provider), port forwarding: https://www.bt.com/help/broadband/learn-about-broadband/how-do-i-set-up-port-forwarding-on-my-bt-hub-
Checked Network Connection settings Ethernet Properties vEthernet Properties (WSL) Hyper-V Virtual Ethernet Adapter Internet Protocol Version 4 (TCP/IPv4) -checked Internet Protocol Version 6 (TCP/IPv6) -checked Hyper-V Extensible Virtual Switch -unchecked
Checked Device Manager (View Hidden) Network adapters > Hyper-V Virtual Ethernet Adapter Properties Device status - This device is working properly.
Turn Windows features on and off Uncheck Windows Subsystem for Linux Windows needs to reboot your PC to finish the requested changes Recheck Windows Subsystem for Linux Windows needs to reboot
Change the nameserver sudo nano /etc/resolv.conf '# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/resolv.conf '# [network] '# generateResolvConf = false nameserver xxx.xx.xx Change the name server to 8.8.8.8 and save the file. You should now be able to connect to the internet. -even restarted ubuntu, same error after restarting and the nameserver seems to be reset to default
https://github.com/microsoft/WSL/issues/5336#issuecomment-653881695 Open Powershell or Cmd as Administrator and run each of these commands: wsl --shutdown netsh winsock reset netsh int ip reset all netsh winhttp reset proxy ipconfig /flushdns Hit the Windows Key, type Network Reset, hit enter. You should see this window. Click "Reset now". Restart Windows

patrick330602 commented 3 years ago

Change the nameserver sudo nano /etc/resolv.conf '# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/resolv.conf '# [network] '# generateResolvConf = false nameserver xxx.xx.xx Change the name server to 8.8.8.8 and save the file. You should now be able to connect to the internet. -even restarted ubuntu, same error after restarting and the nameserver seems to be reset to default

As you can see from the comment, you should edit the /etc/wsl.conf to include the following:

[network]
generateResolvConf = false

to prevent /etc/resolv.conf to be reset.

markko1-pro commented 3 years ago

I'm not an expert, but I think resolv.conf does not play a role here, since resolv.conf is used only for resolving DNS names. If pinging 8.8.8.8 (Google DNS server) directly does not work, then the issue is elsewhere. Do you use a VPN? I think there is an ongoing issue with VPN vs WSL2

sbhatti534602210 commented 3 years ago

Thank you, @patrick330602 and @markko1-pro for getting back to me. So should I edit the /etc/wsl.conf file?

I do not use VPN. I'm using wsl2.

patrick330602 commented 3 years ago

So should I edit the /etc/wsl.conf file?

Yep

sbhatti534602210 commented 3 years ago

Thank you, @patrick330602. I edited /etc/wsl.conf to add the lines:

[network] generateResolvConf = false

I then edited the /etc/resolv.conf to change the name server from the default :

nameserver 8.8.8.8

Closed Ubuntu, reopened it tried:

ping 8.8.8.8

and got:

ping: connect: Network is unreachable

As I understand Ubuntu should be ready to go once you install it and you should not have to edit config files. However, for me, it has not and I don't know why. And also, despite editing the config files, I still cannot connect to the internet from the WSL.

markko1-pro commented 3 years ago

One other thing you could try - disable your antivirus for a while and see whether it helps. I had a similar problem with Kaspersky antivirus. Thankfully our IT allowed me to remove this curse from my PC :)

sbhatti534602210 commented 3 years ago

Thank you, @markko1-pro. I did try that already as it seemed the most likely problem. However, it didn't make a difference.

I had just previously installed Ubuntu and did have connection to the internet in order to download and install packages. However, my computer crashed and I had to do a factory reset. It's after this that I have not been able to connect to the internet from the wsl. I reinstalled, then uninstalled and reinstalled Ubuntu but the problem remains.

My first thought was that it might be the firewall, my computer seems to come with a preinstalled (temporary licence) antivirus software. It had previously expired and I had removed it but with resetting the computer, it got reinstalled.

Regardless of that, I did try the steps I listed above several times, in different orders in case that made a difference. But it doesn't.

sbhatti534602210 commented 3 years ago

By the way, while this problem relates to an Ubuntu installation, I did also try a different wsl distribution, Kali. Which when you download and install from the Microsoft Store comes without any packages. When I tried: sudo apt update I got a network error there as well.

grovertb commented 3 years ago

Until 2 days ago it worked normally, but from one moment to another the internet connection in wsl2 was blocked and I no longer have an internet connection. However, I connected the internet to my pc from another provider and if I can have an internet connection in ubuntu. But with the other internet provider I have no connection in ubuntu.

PavelSosin-320 commented 3 years ago

@grovertb All networking utilities, including ping from systemd based distros (Ubuntu, Debian,Fedora,Suse) assume that the network stack is built around 2 services systemd-networkd for links configuration and systemd-resolved for name resolution. If these services failed to start or don't function correctly there is no chance to have networking functional. Could you try networkctl and resolvectl in both cases as a networking "smoke test"? Both services have very flexible configurations and autoconfiguration mechanisms to ensure stable networking via any infrastructure but leave resolve.conf out-of-the-game.

craigloewen-msft commented 3 years ago

If you're seeing this issue, could you please collect networking logs and post them here in this thread?

Instructions here on how to collect these. Thanks!

Could be related to this bug: https://github.com/microsoft/WSL/issues/7135

PavelSosin-320 commented 3 years ago

I suppose that WSL provides eth0 interface to the distro in the way that is independent from Internet provider. But every ISP use its own hardware and software to connect end-machine to the global infrastructure. If network interface is swon as routable by the networkctl and resolved has sufficient DNS configuration - designated DNS is reachable then WSL does its job well but some Linux configuration is missed or can't be autoconfigured. The issues on the ISP side are also possible. MTR utility helps to know how far your can reach through the WSL VM-Host-Router-... Service provider chain.

sbhatti534602210 commented 3 years ago

@craigloewen-msft, is that directed at me or to @PavelSosin-320 / @grovertb? Can you help with the issue I have raised? Thanks.

craigloewen-msft commented 3 years ago

@sbhatti534602210 that comment is to anyone who is seeing this issue where you've upgraded your Windows version and your network stops working in WSL. Collecting those logs will help us resolve this issue!

To my understanding your issue is the same as the above, so collecting logs and posting them here is the best way for us to look into this.

sbhatti534602210 commented 3 years ago

Thank you @craigloewen-msft I followed the instructions from Step 8, Collect WSL logs. There is no log file. It just collected a screenshot of what I did. I guess the information is automatically sent via the Feedback Hub. Or do I need to run wpr -start wsl.wprp -filemode?

PavelSosin-320 commented 3 years ago

@sbhatti534602210 The network stack of Ubuntu and other "mature" Linux distros is built around the 2 systemd driven services: systemd-networkd and systemd-resolved. Both services have self-documented configuration files in /etc/systemd/ folder and use the autoconfiguration mechanism. The networkctl and resolvectl allow interactive configuration and testing networking and name resolution instantly. If networkctl sees eth0 (internet) interface as "routable" then WSL provides a network to WSL VM and the internet is accessible. Otherwise, either there is a bug in the WSL Network switch or internet access is blocked by security or eth0 provisioning takes too long and ends with a timeout. In the case of routing via VPN, some additional WSL Kernel features (TUP/TAN support) may be needed or only additional configuration to make the Linux networking stack working.

PavelSosin-320 commented 3 years ago

@benhillis The prove that WSL networking is OK and the root cause is outside WSL: systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-07-07 07:55:50 IDT; 5h 34min ago Docs: man:NetworkManager(8) Main PID: 101 (NetworkManager) Tasks: 3 (limit: 9543) Memory: 7.8M CGroup: /system.slice/NetworkManager.service └─101 /usr/sbin/NetworkManager --no-daemon

Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.6964] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: > Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.6967] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'exter> Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.6982] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'ext> Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.6985] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'e> Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.7414] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: > Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.7416] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state:> Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.7419] manager: NetworkManager state is now CONNECTED_LOCAL Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.7425] device (eth0): Activation: successful, device activated. Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.7429] manager: NetworkManager state is now CONNECTED_GLOBAL Jul 07 07:55:50 MSI-wsl NetworkManager[101]: [1625633750.7431] manager: startup complete

Context:

systemd-genie is used as an init system
no VPN
Norton internet security is on
Broadband WiFi router
Fedora remix distro

sbhatti534602210 commented 3 years ago

Thank you @PavelSosin-320. I'm sorry, from your message I did not understand what I need to do that I have not done already. Can you specify? Thanks

keltia commented 2 years ago

Hello, same issue here. WSL2 reinstalled from scratch, Ubuntu (tried ArchLinux as well) freshly installed, run wsl and I get

weird nameserver IP inserted into /etc/resolv.conf
ip address shows that eth0as down.

roberto@WoT:~$ ip address
1: lo:  mtu 65536 qdisc noop state DOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: bond0:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 86:e6:ce:f6:ac:34 brd ff:ff:ff:ff:ff:ff
3: dummy0:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 1e:fe:2b:f1:3e:4a brd ff:ff:ff:ff:ff:ff
4: eth0:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:15:5d:ca:74:7f brd ff:ff:ff:ff:ff:ff
5: tunl0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0
6: sit0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0

and /etc/resolv.conf shows:

# 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 172.18.128.1

It used to work with 1903 and 1909 if I remember correctly.

I checked that as well and apparently systemd is not even used:

roberto@WoT:~$ systemctl status NetworkManager
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down