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 Updating cannot resolve deb.debian.org #1391

Closed
RUNETHERABB1T opened this issue Dec 17, 2023 · 9 comments
Closed

WSL Updating cannot resolve deb.debian.org #1391

RUNETHERABB1T opened this issue Dec 17, 2023 · 9 comments
Labels
community support ATTRIBUTE: community is invited to help

Comments

@RUNETHERABB1T
Copy link

What happened:

So I was trying to figure out how to use the make command because I am new to building software outside of making games. But I found that I could barely have a WSL terminal run "sudo apt-get update && sudo apt-get upgrade -y"

What did you expect to happen?:
I expected software to just update without having errors saying stuff along the lines of
" Temporary failure resolving 'deb.debian.org"

How did you reproduce it?:
i have barely touched the settings for portmaster so it should be as simple as making a new windows VM. Setup WSL and try to update stuff. I was using the debian Linux terminal at the time if that is relevant

Random info that might be useful:
Somehow closing PortMaster down and rerunning the command made it work right away so I am honestly not entirely sure what is up with that. Also please note I am very new to trying to submit issues like this on github so please tell me if I can make future issues more clear and easier to understand as I can't exactly figure out if this is even understandable but I need some help so. Thanks in advance I guess

I also just want to say that I cannot find the Debug info thing that I am asked to also submit so if someone can please help me with figuring that one out I would appreciate it.

Sorry if all of this is basic this barely makes sense to me and I am trying to learn. Thanks and have a good day!

@RUNETHERABB1T RUNETHERABB1T added the bug TYPE: a report on something that isn't working label Dec 17, 2023
@Raphty
Copy link
Member

Raphty commented Dec 17, 2023

I am sorry but WSL as well as other VM(type) software is currently not sported see #166

I have seen some people make it work, but we at this point don't consider incompatibility a bug.

@Raphty Raphty added community support ATTRIBUTE: community is invited to help and removed bug TYPE: a report on something that isn't working labels Dec 17, 2023
Copy link

Hey @RUNETHERABB1T, thank you for raising this issue with us.

After a first review we noticed that this does not seem to be a technical issue, but rather a configuration issue or general question about how Portmaster works.

Thus, we invite the community to help with configuration and/or answering this questions.

If you are in a hurry or haven't received an answer, a good place to ask is in our Discord community.

If your problem or question has been resolved or answered, please come back and give an update here for other users encountering the same and then close this issue.

If you are a paying subscriber and want this issue to be checked out by Safing, please send us a message on Discord or via Email with your username and the link to this issue, so we can prioritize accordingly.

@hexadivine
Copy link

hexadivine commented Jan 11, 2024

@RUNETHERABB1T - Portmaster do not support WSL2. However, you can bypass portmaster by changing the nameserver from resolv.conf file (in WSL2 instance). Try this -

sudo nano /etc/resolv.conf

add below nameserver
nameserver 1.1.1.1

Keep in mind that with this you are bypassing all traffic from Portmaster. This could be a potential privacy concern for some individuals.

@Raphty
Copy link
Member

Raphty commented Jan 12, 2024

thanks for the note. I can not confirm if that works, but be aware that this workaround might stop working at some point when we are looking into adding support for VMs

The issue is not that Portmaster does not see it, and this "bypass" is not actually going past Portmaster it just allows the VM to pass through Portmaster and because we are ignoring it at the moment it works. If we start making changes to how we look at this traffic than can result in breaking this. Just something to be aware of.

@hexadivine
Copy link

Understood @Raphty, you are right, after digging deeper - I noticed that all traffic do in fact go through Portmaster (if turned on). To make this work I added 1.1.1.1 in the resolv.conf as mentioned above.

image

Note - If "Windows Subsystem for Linux" is not visible in portmaster then try creating a server in WSL2 using below command.
python3 -m http.server (I am using WSL2-Ubuntu)

and visit localhost:8000 from host machine this will generate network traffic to localhost and WSL will be visible in Portmaster.

@hexadivine
Copy link

I tested same on the Parrot VBox. By default there is no internet connection, for that you have to add 1.1.1.1 in the resolf.conf and traffic will be transferred through portmaster. You can block/unblock or filter traffic from VirtualBox Virtual Machine.

image

In the conclusion - I can confirm that Portmaster supports VMs for me.

@Raphty
Copy link
Member

Raphty commented Jan 12, 2024

thank you for letting us know, I will add this into the wiki!

@Raphty Raphty added the documentation pending ATTRIBUTE: some part of this issue still needs to be documented in the wiki or somewhere else label Jan 12, 2024
@Raphty
Copy link
Member

Raphty commented Jan 19, 2024

Updated https://wiki.safing.io/en/FAQ/VMsAndPortmaster

@Raphty Raphty removed the documentation pending ATTRIBUTE: some part of this issue still needs to be documented in the wiki or somewhere else label Jan 19, 2024
@hexadivine
Copy link

Looks good 😊 thanks @Raphty

@Raphty Raphty closed this as completed Jan 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community support ATTRIBUTE: community is invited to help
Projects
None yet
Development

No branches or pull requests

3 participants