Windows 10 firewall issues with nebula

[goligo]

Hello,

I noticed an issue with Windows 10 hosts added to my nebula network. Although everything was set up correctly, hosts could not be reached (ping didn't work, no http connection working). After some trouble shooting I discovered, that the nebula UDP-communication between the nodes was working fine, but Windows blocked the resulting packets in the 192.168.100.0-network. I had to add an extra rule in the Windows firewall to allow traffic from this network.

Interestingly the issue did only reproduce on Windows 10 for me, not on Windows 11. In case this is the expected behavior, it would be great if it could be mentioned in the documentation.

Regards, Malte

[bitshop]

I had a similar issue but it was just Windows firewall doing it's job since the firewall rules didn't exist. It could be when nebula launched you chose additional network profiles to allow. If you think that's an answer and the issue should be closed it would be ideal to close this.

[goligo]

I think this is an issue someone should have a look at. I haven't seen such behaviour with other VPNs and it makes nebula feel broken, you install it and it doesn't work without any hint what could be going wrong. Maybe it is related to whether the network adapter is assigned to "public" or "private" network in Windows?