Windows: make network identify-able

[My1]

Windows has a hard time dealing with several things when it cannot "identify" a network. no idea how it does "identify" a network but for example you cannot easily set a net as private if your network is not able to be identified (either you have to make it non every reboot or you run around with a security risk), and therefore easily able to get the network from nebula into private without any bigger issues.

[caguiclajmg]

This can be easily changed with a single PS command:

Set-NetConnectionProfile -Name "Local Area Connection 3" -NetworkCategory Public/Private

I don't think nebula itself should be fiddling with this though.

[My1]

as I said, this Powershell solution is not permanent and would need to be applied after every boot, similar to here

https://superuser.com/questions/1441412/windows-10-set-netconnectionprofile-permanent

If windows could "identify" the network, it would not have that issue.

[aaronkollasch]

I made a version of tun_windows.go that sets the connection to private as the setting is not permanent otherwise.

It's a hack-y solution as it doesn't include a config option, and I agree that it may not belong in nebula itself, but if you are able to compile your own executable and really want a solution, this might help.

[My1]

well at least zerotier which does kinda similar things makes its networks in a way windows can identify them and thereby set them accordingly, not sure how hamachi and others act. but the fact it there is not really a good way of making the network private that does not.

1. need CLI
2. revert on every restart or whatever
3. is a very bad idea in terms of security