Networkin issues in Pengwin

[mattmazer0397]

Describe the bug My instance of Pengwin no longer has network connectiviy. I cannot "sudo apt update," initialize xserver apps, or even ping pengwin from windows terminal

To Reproduce Steps to reproduce the behavior:

1. Open Pengwin 2) Do anything that utilizes network connectivity 3) Fail

Expected behavior retrieve updates, open xserver app, etc

Screenshots If applicable, add screenshots to help explain your problem.

Additional context

It seems that an insiders update has broken connectivity in the pas for some users, so I'm not sure if this is that issue. Basic Troubleshooting Checklist

[ X ] I have searched Google for the error message. [ X ] I have checked official WSL troubleshooting documentation: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#confirm-wsl-is-enabled. [ X ] I have searched the official Microsoft WSL issues page: https://github.com/Microsoft/WSL/issues. [ X ] I have searched the Pengwin issues page: https://github.com/WhitewaterFoundry/Pengwin/issues. [ X ] I have reset Pengwin: Settings->Apps->Apps & features->Pengwin->Advanced Options->Reset. [ X ] I have disabled and re-enabled WSL in Windows Features. [ X ] I have run Windows 10 updates and restarted.

What other troubleshooting have you attempted?

I've googled extensively and some solutions included disabling the firewall and disabling IPv6. None of these fixes did resolved anything. I did uninstall pengwin, disable vm/wsl features and rebooted, then reenabled and installed Pengwin. I had internet connectivity after this reinstall but my computer has rebooted since and it has lost connectivity.

Pengwin Version 20.8.3.0

Windows Build OS Name: Microsoft Windows 10 Home Insider Preview OS Version: 10.0.20226 N/A Build 20226 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free BIOS Version: AMI F.18, 11/7/2019

[patrickleenders]

Same problem for me too, no more network connections

[maple3142]

Maybe try to ping 8.8.8.8 and google.com to see if the problem related to DNS.

[mattmazer0397]

It seems that a windows insider update is responsible. I rolled back to the last update and everything is fine

[crramirez]

It usually has problems with VPNs or when the computer goes to sleep

[patrickleenders]

After reboot i ping to 8.8.8.8 respons if i ping to google.com Temporary failure in name resolution. DNS problem

[robomac]

I'm not on Windows Insider (too many other issues; it was worth it to flatten my system) and I suddenly have this same problem with Pengwin.

[imaandrew]

Can you try running the powershell script here? This fixes the problem for me.

[robomac]

@ThatWeirdAndrew That doesn't do a thing for me... but I had even tried rebooting before that. All that script does is restart a few services. Something has gone wonky in the linux or bridge configuration.

[shabazz-abdulrahman1]

I have similar issues, this was working before until a recent Windows update , then all of a sudden I lost network connectivity in WSL2 I have tried almost all steps described by @mattmazer0397 above no luck. I noticed this when I could no loger do a git pull or git push upstream to a remote repository. then I ran a ping command and got an error 'temporary failure in name resolution' , also I tried to install packages using pengwin-setup everything failed as WSL2 can't connect to the network to install the packages see error below: The following NEW packages will be installed: alsa-topology-conf alsa-ucm-conf at-spi2-core cron dconf-gsettings-backend dconf-service emacs emacs-bin-common emacs-common emacs-el emacs-gtk emacsen-common exim4-base exim4-config exim4-daemon-light glib-networking glib-networking-common glib-networking-services gsasl-common gsettings-desktop-schemas guile-2.2-libs install-info libasound2 libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 libcolord2 libdconf1 libepoxy0 libevent-2.1-7 libgc1 libgd3 libgif7 libgnutls-dane0 libgsasl7 libgtk-3-0 libgtk-3-bin libgtk-3-common libjansson4 libjson-glib-1.0-0 libjson-glib-1.0-common libm17n-0 libmailutils7 libmariadb3 libmpdec3 libntlm0 libotf0 libproxy1v5 libpython3.9 libpython3.9-minimal libpython3.9-stdlib librest-0.7-0 libsoup-gnome2.4-1 libsoup2.4-1 libunbound8 libwayland-cursor0 libwayland-egl1 libxcomposite1 libxcursor1 libxdamage1 libxft2 libxi6 libxinerama1 libxkbcommon0 libxpm4 libxrandr2 libxtst6 m17n-db mailutils mailutils-common mariadb-common media-types mysql-common netbase xkb-data 0 upgraded, 77 newly installed, 0 to remove and 0 not upgraded. Need to get 61.5 MB of archives. After this operation, 253 MB of additional disk space will be used. Err:1 https://deb.debian.org/debian bullseye/main amd64 install-info amd64 6.7.0.dfsg.2-6 Temporary failure resolving 'deb.debian.org' Err:2 https://deb.debian.org/debian bullseye/main amd64 cron amd64 3.0pl1-137 Temporary failure resolving 'deb.debian.org' Err:3 https://deb.debian.org/debian bullseye/main amd64 netbase all 6.3 Temporary failure resolving 'deb.debian.org' Err:4 https://deb.debian.org/debian bullseye/main amd64 media-types all 4.0.0 Temporary failure resolving 'deb.debian.org' Err:5 https://deb.debian.org/debian bullseye/main amd64 alsa-topology-conf all 1.2.4-1 Temporary failure resolving 'deb.debian.org' Err:6 https://deb.debian.org/debian bullseye/main amd64 libasound2-data all 1.2.4-1.1 Temporary failure resolving 'deb.debian.org' Err:7 https://deb.debian.org/debian bullseye/main amd64 libasound2 amd64 1.2.4-1.1 Temporary failure resolving 'deb.debian.org' Err:8 https://deb.debian.org/debian bullseye/main amd64 alsa-ucm-conf all 1.2.4-2 Temporary failure resolving 'deb.debian.org' Err:9 https://deb.debian.org/debian bullseye/main amd64 libatspi2.0-0 amd64 2.38.0-4 Temporary failure resolving 'deb.debian.org' Err:10 https://deb.debian.org/debian bullseye/main amd64 libxi6 amd64 2:1.7.10-1 Temporary failure resolving 'deb.debian.org' Ign:11 https://deb.debian.org/debian bullseye/main amd64 libxtst6 amd64 2:1.2.3-1 Err:12 https://deb.debian.org/debian bullseye/main amd64 at-spi2-core amd64 2.38.0-4 Temporary failure resolving 'deb.debian.org' Err:13 https://deb.debian.org/debian bullseye/main amd64 libdconf1 amd64 0.38.0-2 Temporary failure resolving 'deb.debian.org' Err:14 https://deb.debian.org/debian bullseye/main amd64 dconf-service amd64 0.38.0-2 Temporary failure resolving 'deb.debian.org' Err:15 https://deb.debian.org/debian bullseye/main amd64 dconf-gsettings-backend amd64 0.38.0-2 Temporary failure resolving 'deb.debian.org' Ign:16 https://deb.debian.org/debian bullseye/main amd64 emacsen-common all 3.0.4 Err:17 https://deb.debian.org/debian bullseye/main amd64 emacs-common all 1:27.1+1-3.1 Temporary failure resolving 'deb.debian.org' Err:18 https://deb.debian.org/debian bullseye/main amd64 emacs-bin-common amd64 1:27.1+1-3.1 Temporary failure resolving 'deb.debian.org' Err:19 https://deb.debian.org/debian bullseye/main amd64 libgif7 amd64 5.1.9-2 Temporary failure resolving 'deb.debian.org' Err:20 https://deb.debian.org/debian bullseye/main amd64 libatk1.0-data all 2.36.0-2 Temporary failure resolving 'deb.debian.org' Err:21 https://deb.debian.org/debian bullseye/main amd64 libatk1.0-0 amd64 2.36.0-2 Temporary failure resolving 'deb.debian.org' Err:22 https://deb.debian.org/debian bullseye/main amd64 libatk-bridge2.0-0 amd64 2.38.0-1 Temporary failure resolving 'deb.debian.org' Err:23 https://deb.debian.org/debian bullseye/main amd64 libcolord2 amd64 1.4.5-3 Temporary failure resolving 'deb.debian.org' Err:24 https://deb.debian.org/debian bullseye/main amd64 libepoxy0 amd64 1.5.5-1 Temporary failure resolving 'deb.debian.org' Err:25 https://deb.debian.org/debian bullseye/main amd64 libjson-glib-1.0-common all 1.6.2-1 Temporary failure resolving 'deb.debian.org' Err:26 https://deb.debian.org/debian bullseye/main amd64 libjson-glib-1.0-0 amd64 1.6.2-1 Temporary failure resolving 'deb.debian.org' Err:27 https://deb.debian.org/debian bullseye/main amd64 libproxy1v5 amd64 0.4.17-1 Temporary failure resolving 'deb.debian.org' Err:28 https://deb.debian.org/debian bullseye/main amd64 glib-networking-common all 2.66.0-2 Temporary failure resolving 'deb.debian.org' Err:29 https://deb.debian.org/debian bullseye/main amd64 glib-networking-services amd64 2.66.0-2 Temporary failure resolving 'deb.debian.org' Err:30 https://deb.debian.org/debian bullseye/main amd64 gsettings-desktop-schemas all 3.38.0-2 Temporary failure resolving 'deb.debian.org' Err:31 https://deb.debian.org/debian bullseye/main amd64 glib-networking amd64 2.66.0-2 Temporary failure resolving 'deb.debian.org' Err:32 https://deb.debian.org/debian bullseye/main amd64 libsoup2.4-1 amd64 2.72.0-2 Temporary failure resolving 'deb.debian.org' Err:33 https://deb.debian.org/debian bullseye/main amd64 libsoup-gnome2.4-1 amd64 2.72.0-2 Temporary failure resolving 'deb.debian.org' Err:34 https://deb.debian.org/debian bullseye/main amd64 librest-0.7-0 amd64 0.8.1-1.1 Temporary failure resolving 'deb.debian.org' Err:35 https://deb.debian.org/debian bullseye/main amd64 libwayland-cursor0 amd64 1.18.0-2~exp1.1 Temporary failure resolving 'deb.debian.org' Err:36 https://deb.debian.org/debian bullseye/main amd64 libwayland-egl1 amd64 1.18.0-2~exp1.1 Temporary failure resolving 'deb.debian.org' Err:37 https://deb.debian.org/debian bullseye/main amd64 libxcomposite1 amd64 1:0.4.5-1 Temporary failure resolving 'deb.debian.org' Err:38 https://deb.debian.org/debian bullseye/main amd64 libxcursor1 amd64 1:1.2.0-2 Temporary failure resolving 'deb.debian.org' Err:39 https://deb.debian.org/debian bullseye/main amd64 libxdamage1 amd64 1:1.1.5-2 Temporary failure resolving 'deb.debian.org' Ign:40 https://deb.debian.org/debian bullseye/main amd64 libxinerama1 amd64 2:1.1.4-2 Err:41 https://deb.debian.org/debian bullseye/main amd64 xkb-data all 2.29-2 Temporary failure resolving 'deb.debian.org' Err:42 https://deb.debian.org/debian bullseye/main amd64 libxkbcommon0 amd64 1.0.3-2 Temporary failure resolving 'deb.debian.org' Ign:43 https://deb.debian.org/debian bullseye/main amd64 libxrandr2 amd64 2:1.5.1-1 Err:44 https://deb.debian.org/debian bullseye/main amd64 libgtk-3-common all 3.24.24-4 Temporary failure resolving 'deb.debian.org' Err:45 https://deb.debian.org/debian bullseye/main amd64 libgtk-3-0 amd64 3.24.24-4 Temporary failure resolving 'deb.debian.org' Err:46 https://deb.debian.org/debian bullseye/main amd64 libjansson4 amd64 2.13.1-1.1 Temporary failure resolving 'deb.debian.org' Err:47 https://deb.debian.org/debian bullseye/main amd64 m17n-db all 1.8.0-3 Temporary failure resolving 'deb.debian.org' Ign:48 https://deb.debian.org/debian bullseye/main amd64 libxpm4 amd64 1:3.5.12-1 Err:49 https://deb.debian.org/debian bullseye/main amd64 libgd3 amd64 2.3.0-2 Temporary failure resolving 'deb.debian.org' Err:50 https://deb.debian.org/debian bullseye/main amd64 libotf0 amd64 0.9.13-7 Temporary failure resolving 'deb.debian.org' Ign:51 https://deb.debian.org/debian bullseye/main amd64 libxft2 amd64 2.3.2-2 Ign:52 https://deb.debian.org/debian bullseye/main amd64 libm17n-0 amd64 1.8.0-2 Err:53 https://deb.debian.org/debian bullseye/main amd64 emacs-gtk amd64 1:27.1+1-3.1 Temporary failure resolving 'deb.debian.org' Err:54 https://deb.debian.org/debian bullseye/main amd64 emacs all 1:27.1+1-3.1 Temporary failure resolving 'deb.debian.org' Err:55 https://deb.debian.org/debian bullseye/main amd64 emacs-el all 1:27.1+1-3.1 Temporary failure resolving 'deb.debian.org' Err:56 https://deb.debian.org/debian bullseye/main amd64 exim4-config all 4.94.2-1 Temporary failure resolving 'deb.debian.org' ^C ping google.com also produced the error : ping: google.com: Temporary failure in name resolution

I have searched the opened and closed issues and this issue (issue-641) exactly related to my issue so there is no need to raise a new issue. This problem is literally making the Windows / WSL2 setup un usable for Development work, what's the use if I can't clone a repository or install packages due to some issues with the way Networking is setup in WSL2 ( I learnt some people have reverted back to WSL1 just to avioid this problem). After reaserching the internet , it turns out that this issue has been raised before here: https://github.com/microsoft/WSL/issues/6404# Microsoft can't just ignore this problem, it is a BIG DEAL.

[crramirez]

Hello,

Check if you are inside a VPN that is getting in the way. The problem is the DNS you can add the following entry to /etc/wsl.conf: [network] generateResolvConf = false

and then edit your /etc/resolv.conf nameserver entry and put here your actual DNS.

Regards, Carlos