Set Category of the TUN device's network profile to 1 in Windows Registry#363
Merged
KKRainbow merged 1 commit intoEasyTier:mainfrom Sep 24, 2024
Merged
Conversation
Hs-Yeah
force-pushed
the
feat/set-tun-category-in-win-reg
branch
from
8379c71 to
19f2e0d
Compare
Member
|
Great Job! |
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
2 participants
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.
On Windows, newly added virtual network cards are set to "Public network" by default, causing the Windows built-in firewall to reject all inbound traffic from the virtual network card. Many services, such as Samba, Remote Desktop, Jellyfin are affected by this.
Changing the Category of the TUN device's network profile to 1 in Windows Registry makes it to be "Private network".