You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Windows 11, when starting sing-box with tun adapter it creates tun adapter and gets assigned automatically to Public firewall network making my LAN services (like SSH) unreachable unless I set OpenSSH to Public and Private firewall network. Screenshot below shows tun0 assigned to Public firewall network.
OpenSSH firewall default rule is to open up only for Private network unless I set it to Public network in which I can now access my SSH server
The fix was to run this powershell command Set-NetConnectionProfile -InterfaceAlias 'tun0' -NetworkCategory 'Private'
(tun0 being the interface name assigned by sing-box)
After every reboot it seems to be properly assigned to Private firewall network but I am not sure if it will stay persistent after changing sing-box versions or Windows OS updates.
Could there be an option so that the user can choose between Domain/Private/Public firewall profiles to assign the tun driver to?
The text was updated successfully, but these errors were encountered:
In Windows 11, when starting sing-box with tun adapter it creates tun adapter and gets assigned automatically to Public firewall network making my LAN services (like SSH) unreachable unless I set OpenSSH to Public and Private firewall network. Screenshot below shows tun0 assigned to Public firewall network.
OpenSSH firewall default rule is to open up only for Private network unless I set it to Public network in which I can now access my SSH server
![image](https://private-user-images.githubusercontent.com/75412786/352802528-04e25aa6-345b-4501-a1e8-83cc6c4bded9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk4Mjc2NjYsIm5iZiI6MTczOTgyNzM2NiwicGF0aCI6Ii83NTQxMjc4Ni8zNTI4MDI1MjgtMDRlMjVhYTYtMzQ1Yi00NTAxLWExZTgtODNjYzZjNGJkZWQ5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE3VDIxMjI0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWZmMjJiYmYwNmYxMmM4NWEwMjcwZGI5MTc0MGIxNmJiZDMyODY2N2IzNTYwNjgxYTJlZGI3YTNiOWNmYWE1NDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.5-63Q8jYvhUuJUhKwoyT4_agg0W_SCnVkqhFOdFjMzs)
The issue is similar to this reddit thread:
https://www.reddit.com/r/WireGuard/comments/y8unbd/permanently_set_wireguard_to_private_network_on/
The fix was to run this powershell command
Set-NetConnectionProfile -InterfaceAlias 'tun0' -NetworkCategory 'Private'
(tun0 being the interface name assigned by sing-box)
After every reboot it seems to be properly assigned to Private firewall network but I am not sure if it will stay persistent after changing sing-box versions or Windows OS updates.
Could there be an option so that the user can choose between Domain/Private/Public firewall profiles to assign the tun driver to?
![image](https://private-user-images.githubusercontent.com/75412786/352802590-7426d850-918b-43ca-b005-810d0885330e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk4Mjc2NjYsIm5iZiI6MTczOTgyNzM2NiwicGF0aCI6Ii83NTQxMjc4Ni8zNTI4MDI1OTAtNzQyNmQ4NTAtOTE4Yi00M2NhLWIwMDUtODEwZDA4ODUzMzBlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE3VDIxMjI0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFjMjJjZGRiYmI4MTZmOWIzMWQ5NGFhNzFjNzY3ZTVkZThlZjZkNTNhNTE2ZjFjOGEzZTczMGY0M2VmNzJhYTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.JPW8mjPGucda3kQlPCODw5oePOGKWpwYnjk5OW2lu20)
The text was updated successfully, but these errors were encountered: