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

socket_vmnet does not cooperate with Cloudflare WARP #42

Open
runderwo opened this issue Aug 8, 2024 · 2 comments
Open

socket_vmnet does not cooperate with Cloudflare WARP #42

runderwo opened this issue Aug 8, 2024 · 2 comments

Comments

@runderwo
Copy link

runderwo commented Aug 8, 2024

Hello, I found that if socket_vmnet is running, WARP cannot connect and reports "DNS Proxy Failure". Only killing socket_vmnet will allow WARP to establish the tunnel. Is there a workaround for this? I need to use socket_vmnet for local tasks on a minikube but I work for a company whose policy mandates tunneling with WARP.

@jandubois
Copy link
Member

Can you start WARP first, and then run socket_vmnet?

I have a suspicion that the problem is that vmnet will run mDNSResponder, which will bind to port 53, and prevents WARP from binding to this port.

I have no idea how to prevent vmnet from starting mDNSResponder, but it doesn't actually need it for most use cases, so runs fine even when port 53 is already in use.

I also don't know why mDNSResponder listens on port 53 at all, as the mDNS port is 5353.

@nirs
Copy link
Member

nirs commented Nov 17, 2024

Maybe kill or stop mDNSResponder, then start WRAP?

@runderwo did you try to contact Cloudflare about this?

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

No branches or pull requests

3 participants