Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL behind network: ping works wget fails IPV6 disabled #3637

Closed
cyrilthank opened this issue Oct 26, 2018 · 2 comments
Closed

WSL behind network: ping works wget fails IPV6 disabled #3637

cyrilthank opened this issue Oct 26, 2018 · 2 comments
Labels

Comments

@cyrilthank
Copy link

Hi
I am on Microsoft Windows 10 Version 1709 (OS Build 16299.726)

I am working behind a vpn and so far tried the below options

  1. disabled ipv6
  2. updated gai.conf
  3. DNSSEC=off
    to /etc/systemd/resolved.conf
  4. the nslookup matches between the ubuntu/WSL and windows
  5. the ping output matches between the ubuntu/WSL and windows
  6. Windows Defender Firewall has added the executables
    C:\Program Files\WindowsApps\CanonicalGroupLimited.Ubuntu18.04onWindows_1804.2018.817.0_x64__79rhkp1fndgsc\ubuntu1804.exe
    C:\Program Files\WindowsApps\CanonicalGroupLimited.Ubuntu18.04onWindows_1804.2018.817.0_x64__79rhkp1fndgsc\ubuntu.exe
    For domain/public/private
  7. Only antivirus running is McAfee

Appreciate any help

@cyrilthank
Copy link
Author

Executed below steps given in #5
but still not working

sushantmishra1996 commented on Jul 16
FOR PEOPLE WORKING ON A PROXY NETWORK
I had this same issue. I resolved it this way:

Disabling firewall as described by @MendesMartini
My resolv.conf file 's nameserver address matched to the DNS address from /ipconfig/all .
Use this command
sudo nano /etc/apt/apt.conf
Write this line with your proxy address and port in the above file.
Acquire::http::Proxy "http://proxyaddress:port";
press ctrl+X then y then enter to save.
( Example: acquire::http::Proxy "http://192.10.3.40:8080"; )
Run sudo apt-get update.

Copy link
Contributor

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants