-
Notifications
You must be signed in to change notification settings - Fork 37
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
VPN now recovers from WireGuard closing utun #931
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Aug 13, 2024
diegoreymendez
commented
Aug 13, 2024
Comment on lines
+64
to
+65
case startWireGuardBackend(Error) | ||
case setWireguardConfig(Error) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's cleaner and easier to manage if we just send underlying errors.
samsymons
approved these changes
Aug 13, 2024
diegoreymendez
added a commit
to duckduckgo/iOS
that referenced
this pull request
Aug 13, 2024
Task/Issue URL: https://app.asana.com/0/0/1208000338328853/f macOS: duckduckgo/macos-browser#3084 BSK: duckduckgo/BrowserServicesKit#931 ## Description If we detect an error while updating the tunnel configuration we now cancel the tunnel so Apple recreates the virtual interface. I believe the underlying issue is WireGuard should not "touch" the virtual interface at all, as that responsibility is owned by Apple.
diegoreymendez
added a commit
to duckduckgo/macos-browser
that referenced
this pull request
Aug 13, 2024
Task/Issue URL: https://app.asana.com/0/0/1208000338328853/f iOS: duckduckgo/iOS#3204 BSK: duckduckgo/BrowserServicesKit#931 ## Description If we detect an error while updating the tunnel configuration we now cancel the tunnel so Apple recreates the virtual interface. I believe the underlying issue is WireGuard should not "touch" the virtual interface at all, as that responsibility is owned by Apple.
samsymons
added a commit
that referenced
this pull request
Aug 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Task/Issue URL: https://app.asana.com/0/0/1208000338328853/f
iOS PR: duckduckgo/iOS#3204
macOS PR: duckduckgo/macos-browser#3084
What kind of version bump will this require?: Major
Description
Adds a recovery mechanism for the tunnel so that when WireGuard throws an error on tunnel update, we restart the VPN tunnel.
Testing
See the platform-specific PRs for testing instructions.
Internal references:
Software Engineering Expectations
Technical Design Template