This message was deleted.
# rancher-desktop
a
This message was deleted.
w
guessing your vpn daemon sees the socket_vmnet interface come up and panics a bit. no colima uses the same socket_vmnet as well unless it is on vde_vmnet. anything in the networking logs?
and did you try vz as i think that uses the apple nat option
c
yes using vz + rosetta. Actually, I tried every options VZ,QEMU,experimental vmnet (can’t remember the real name), …
w
hmm if they all don't work that is one sensitive VPN 🤣
i believe they all look different on the route table, but without knoweldge of what the VPN is reacting to its hard to figure out how to avoid it
have you asked your VPN team about what might be logged and why the connection is bouncing?
c
They only see that my mac disconnect. Initiated from my side basically.
w
yeah but the VPN client has to have some local logging
c
I guess the bride network adapter created or a similar config created by Rancher Desktop is causing the issue.
👍 1
BTW, I need to uninstall RD to get back my VPN working.
The better I can get is the following :
Copy code
plugin NEVPNTunnelPlugin(com.apple.NetworkExtension.IKEv2Provider[inactive]) disconnected with reason Plugin failed
w
huh thats extra weird. in my experience bridge100 goes away when i shutdown RD.
c
maybe… I’m on 13.z
But docker is working though
w
we don't use IKE for our VPN so no way to compare directly
c
I’ll see when 14 is available in my org.
Thanks for your help!
w
some folks on that post seemed to say sonoma didn't fix their problems with IKE. if you have a support contract w Apple may be worth seeing if they can tease out the issue
f
Are you running with "Admin access" enabled? If you don't enable this, then you don't get the bridged/shared network adapter but just port forwarding to localhost. But maybe that is good enough for you?
Most people don't really need the routable IP address, which is why admin mode is no longer the default (it is also annoying as it asks for your password every time you reboot the machine because it has to recreate the socket in
/var/run/docker.sock
)
c
Bridge network seems to be there event with admin access enabled.
f
I was trying to say that if you don't need the routable IP address, you could disable admin access and see if that avoids the disconnect issue you are seeing because then all traffic should be to localhost.
c
Got it. No it doesn’t help unfortunately.