This repository has been archived by the owner on Sep 29, 2024. It is now read-only.
Support --route-nopull #280
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
When provided, pull everything except: - Routes - DNS - Proxy Implement with higher granularity compared to OpenVPN.
Pull server settings by default to match standard OpenVPN behavior. Library was prioritizing client over server.
This was referenced Oct 23, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
With higher granularity than standard OpenVPN client, which instead rejects these settings altogether:
Also fixes incorrect priority of client settings over server-pulled settings. Server settings must always take over, unless
--route-nopullis set.