-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Cisco VPN: ssh: handshake failed: ssh: unable to authenticate.. no supported methods remain #3930
Comments
Thank you @davisford for opening this.
Any PRs, thoughts welcome! |
Hi I also have exact same issue (minikube 1.2.0) hyperkit on mac os, when VPN is up, @davisford did you figure out how to reroute the traffic not to go through vpn ? |
@aidagha with the Cisco VPN I indicated above, there is no way. It hijacks the complete network stack. I believe it can be configured to allow local LAN access when using VPN (see pic): But note the (if configured) -- mine doesn't allow it. If you can convince whoever set up your VPN to allow that, then it might work? |
Just as a heads up - there is some integration with hyperkit and VPN's that may resolve this now. Expect it to still be broken with VirtualBox however. |
Hi, not sure how useful this issue is, or what you could do to work around it, but I figured I'd document it -- maybe it will help someone else.
So, I've happily constructed my minikube environment and been playing with k8s clusters for several days, but today I noticed it just hang. I could not get
minikube status
to return, andkubectl
was totally unresponsive (also hangs).I realized shortly after that it was a result of the Cisco VPN Client I'm using which happens to hi-jack the entire network stack -- and forces all traffic through its tunnel.
I've run into this issue before -- working at other companies that use this client and trying to run Virtual Machines like VMWare. Even if you setup networking in a VM to use bridged or hosted -- the VPN prevents you from reaching it when you are connected.
Perhaps there's an event from the OS you could trap on to let you know when the network is re-configured and then you could gracefully shutdown or pause? That's really the purpose of me posting this issue. Hope it is helpful
Mac OS 10.13.6 High Sierra
The text was updated successfully, but these errors were encountered: