search

lima-vm / socket_vmnet

vmnet.framework support for unmodified rootless QEMU (no dependency on VDE)
Apache License 2.0
109 stars 17 forks source link

socket_vmnet does not cooperate with Cloudflare WARP #42

Open runderwo opened 3 months ago

runderwo commented 3 months ago

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 commented 3 months ago

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 commented 2 weeks ago

Maybe kill or stop mDNSResponder, then start WRAP?

@runderwo did you try to contact Cloudflare about this?