Skip to content

feat: add start vpn on launch setting #108

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

Merged
merged 1 commit into from
Mar 18, 2025

Conversation

ethanndickson
Copy link
Member

@ethanndickson ethanndickson commented Mar 11, 2025

Relates to #104.

On-demand is a pretty big lift - in the meantime we'll add a 'start VPN on launch' config setting.

Copy link
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@ethanndickson ethanndickson marked this pull request as ready for review March 11, 2025 07:08
@ethanndickson ethanndickson requested a review from ThomasK33 March 11, 2025 08:44
@ethanndickson ethanndickson force-pushed the ethan/start-on-launch-setting branch from e19e213 to df5447f Compare March 12, 2025 02:30
@ethanndickson ethanndickson self-assigned this Mar 12, 2025
@ethanndickson ethanndickson force-pushed the ethan/start-on-launch-setting branch from df5447f to ea50192 Compare March 12, 2025 05:50
@ethanndickson ethanndickson force-pushed the ethan/start-on-launch-setting branch from ea50192 to be1bc20 Compare March 18, 2025 03:22
Copy link
Member Author

ethanndickson commented Mar 18, 2025

Merge activity

  • Mar 17, 11:35 PM EDT: A user started a stack merge that includes this pull request via Graphite.
  • Mar 17, 11:35 PM EDT: A user merged this pull request with Graphite.

@ethanndickson ethanndickson merged commit de63a7a into main Mar 18, 2025
4 checks passed
@ethanndickson ethanndickson deleted the ethan/start-on-launch-setting branch March 18, 2025 03:35
ethanndickson added a commit that referenced this pull request Mar 19, 2025
This is a fix for #108. Previously we would start the VPN immediately on launch if the config option was true. This starting of the VPN raced with any concurrent upgrades of the network extension, causing the VPN to be started with a VPN config belonging to the older network extension, and producing a consistent error message: 
![image](https://github.com/user-attachments/assets/a69932cb-4c86-4d45-8ab5-5843e255f395)

Instead, we should only start the VPN once we know that the system extension and VPN configuration are installed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants