Repository navigation
Add explicit IPv6 permissions and configurable system blocking - #83
Merged
Merged
Conversation
This file contains hidden or 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
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.
IPv6 destinations are now opt-in per profile and for the system route. Mixed routing requires both permissions; automatic uplink detection is removed. Both permissions round-trip in the shared configuration.
Connection settings also offer an enabled-by-default Windows IPv6 block. Turning it off retains the TUN IPv6 address to avoid sing-tun blocking loopback, while DNS remains IPv4-only and routed IPv6 is rejected. Includes autosave, import/export, read-only handling and documentation.
Validation: configuration tests (including 24 policy combinations), UI tests and schema tests passed locally. CI adds real TUN/WFP loopback and cleanup checks for both DLLs, plus the compatibility mode across proxy types. Real TUN tests were not run on the workstation with an active connection.