-
Notifications
You must be signed in to change notification settings - Fork 133
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
Unexpected DNS failure in NEPacketTunnelProvider #1099
Comments
I will need a bit more time to attack this. I've occasionally seen those DNS failures and they often make no sense, but I couldn't find the culprit. Or, at least, I thought I had fixed them a while ago. Is this urgent? |
Self note: ensure that CFDNS queries are NEVER going through the tunnel. |
No, not urgent urgent, but if this is meant to work I’d love to be able to get rid of AWS’s shitty first-party client. Is it an intermittent failure or is there an actual bug that’s triggered by something in my setup? |
Unfortunately, I have no clue yet. DNS is the most unpredictable point of failure in the tunnel extension. My comment is an idea but I don't have the time now to confirm or dismiss it. |
Out of curiosity, can you link me to the "AWS client" you are talking about? |
It’s this one (the macOS version obvs.) |
Just wanted to say that as a temporary workaround you can replace the remotes in the .ovpn with the resolved IP addresses. |
Summary
I get a "Failed" when I try and start a VPN configured via an .ovpn file I got from AWS
Steps to reproduce
What is the current bug behavior?
See "Activating" for a second, then "Failed" (note this profile works fine as-is in the AWS first-party VPN application.)
What is the expected correct behavior?
Passepartout opens a browser window into which I authenticate with AWS, then the VPN opens and I can access my VPC.
Relevant logs and/or screenshots
Possible fixes suggested remediation
I see a lot of DNS failures in the above log, but I don't have any idea if they're relevant. DNS works fine on my machine.
The text was updated successfully, but these errors were encountered: