Greetings,
I have been trying to fix a problem with my Windows 10 WSL (Linux subsystems) that developed recently where I could no longer resolve domain names but I could connect directly to IPs, ie ping 8.8.8.8 worked but ping www.google.com did not. I tracked this down to the AVG Fake Website Shield protection being enabled as it worked immediately as soon as I disabled the Fake Website Shield. Looking into further, this makes sense as it has a fake DNS configuration option, so it is definitely doing something to the DNS connection between Linux WSL and Windows 10. My question is: how do I allow the Ubuntu/Debian WSL to continue to use my DNS while keeping the other protections from AVG in place?
Thanks
This appears to be a new problem. I'm seeing the same problem with Fake Web Shield, and I've been using DNS for quite some time until it stopped working very recently, probably in the last week. Just recently applied Windoze Update, and perhaps an AVG update stuck in there too.
It would be REALLY handy if AVG provided a comprehensive troubleshooting guide for WSL2 network services problems. I had a heck of time getting ssh and git to blast through the AVG Enhanced Firewall.
All the magic forwarding and port filtering going on in Windoze + VM/WSL2 + AVG, is recipe for problems. When this problem occurs, you can't interupt, suspend, or terminatethe process (hanging on the libsocket call via sotruss), you have to close the terminal.
The documentation in AVG for WSL2 support could use some attention (it does not exist), and I don't think it's been well tested, nor well documented as far as I can determine. File selection dialogs that fail to recognize linux executables (no .exe extension) is a big problem, and having to dig into the WSL2 packaging is WAY too technical for most users.
Hello Drew,
We're glad to help you.
We'll forward this ticket to our senior-level support for better clarifications. Your patience and understanding are much appreciated on this matter.
Meanwhile, please submit the necessary logs which I've requested to you through email.
Thank you for your understanding in advance!
This appears to be a new problem. I'm seeing the same problem with Fake Web Shield, and I've been using DNS for quite some time until it stopped working very recently, probably in the last week. Just recently applied Windoze Update, and perhaps an AVG update stuck in their too.
It would be REALLY handy if AVG provided a comprehensive troubleshooting guide for WSL2 network services problems. I had a heck of time getting ssh and git to blast through the AVG Enhanced Firewall.
All the magic forwarding and port filtering going on in Windoze + VM/WSL2 + AVG, is recipe for problems. When this problem occurs, you can't interupt, suspend, or terminatethe process (hanging on the libsocket call via sotruss), you have to close the terminal.
The documentation in AVG for WSL2 support could use some attention (it does not exist), and I don't think it's been well tested, and certainly not well documented as far as I can determine.
Hello Drew,
We're glad to help you.
We'll forward this ticket to our senior-level support for better clarifications. Your patience and understanding are much appreciated on this matter.
Meanwhile, please submit the necessary logs which I've requested to you through email.
Thank you for your understanding in advance!