4.3.22 host-only adapter change: applied firewall profile?
Posted: 13. Feb 2015, 14:02
From the changelog for 4.3.22:
Host-only adapter: prevent Windows from creating an "Unidentified network"
After this change, what Windows firewall profile is applied to the VirtualBox Host-only adapter?
Previously, while the adapter was still showing up as belonging to an "unidentified network", the Public profile was clearly applied. What profile is applied now, and how can I check or potentially change it via the Windows UI?
This change was achieved by setting the *NdisDeviceType parameter to 1 for the Host-only adapter (see https://www.virtualbox.org/ticket/9688). According to Microsoft's documentation (see https://msdn.microsoft.com/en-us/librar ... S.85).aspx), this marks the adapter as an "endpoint device and is not a true network interface that connects to a network". Since the adapter no longer shows up as part of any network, I can't find a way to see what firewall profile is applied to it.
Host-only adapter: prevent Windows from creating an "Unidentified network"
After this change, what Windows firewall profile is applied to the VirtualBox Host-only adapter?
Previously, while the adapter was still showing up as belonging to an "unidentified network", the Public profile was clearly applied. What profile is applied now, and how can I check or potentially change it via the Windows UI?
This change was achieved by setting the *NdisDeviceType parameter to 1 for the Host-only adapter (see https://www.virtualbox.org/ticket/9688). According to Microsoft's documentation (see https://msdn.microsoft.com/en-us/librar ... S.85).aspx), this marks the adapter as an "endpoint device and is not a true network interface that connects to a network". Since the adapter no longer shows up as part of any network, I can't find a way to see what firewall profile is applied to it.