What is "HNS Container Networking" and why is it....

I've never seen this before. I try to do a search and I find tons of techinbabel on how it works but nothing telling me "why".

Windows is trying to add an allow rule to my firewall for "HNS Container Networking - DNS (UDP-In)".

Can anyone give me a simple reason "why" my os is trying to use this?

Sqrly said:

I've never seen this before. I try to do a search and I find tons of techinbabel on how it works but nothing telling me "why".

Windows is trying to add an allow rule to my firewall for "HNS Container Networking - DNS (UDP-In)".

Can anyone give me a simple reason "why" my os is trying to use this?

Do you have Pro and have you just turned on Hyper-V?

HNS is part of this and requires those rules to be added....

Microsoft said:

The Host Networking Service (HNS) and the Host Compute Service (HCS) work together to create containers and attach endpoints to a network.

Network Creation

• HNS creates a Hyper-V virtual switch for each network
• HNS creates NAT and IP pools as required

Endpoint Creation

• HNS creates network namespace per container endpoint
• HNS/HCS places v(m)NIC inside network namespace
• HNS creates (vSwitch) ports
• HNS assigns IP address, DNS information, routes, etc. (subject to networking mode) to the endpoint

https://docs.microsoft.com/en-us/vir...etwork-service

Bree said:

Do you have Pro and have you just turned on Hyper-V?

Yes, I have Pro, it says so right under my avatar and in the system spec picture I put in my post!

Sorry to be snippy but I find it quite irritating when someone asks me questions to which the answers are in my original post. I can only conclude they didn't actually read it.

No I did not turn on Hyper-V, and it is not installed.



The only recent changes I've made are to my OpenVPN config files. I added the "block-outside-dns" line the the end of the config file.

Seems very suspicious that suddenly a secondary DNS system tries to turn on.

Sqrly said:

No I did not turn on Hyper-V, and it is not installed. ...
...Seems very suspicious that suddenly a secondary DNS system tries to turn on.

One other situation that could create a virtual switch it to enable Windows Sandbox.

Enable or Disable Windows Sandbox in Windows 10

Microsoft said:

...enables networking by creating a virtual switch on the host and connects the sandbox to it via a virtual NIC....

https://docs.microsoft.com/en-us/win...using-wsb-file

I figured it out.

I only recently updated to 2004 and I was trying out "Edge Application Guard". "..Microsoft Edge opens the site in an isolated Hyper-V-enabled container..".

I didn't read far enough to figure out how it uses Hyper-V while Hyper-V is supposedly not installed.

Thanks for taking the time to reply Bree.

Sqrly said:

I figured it out.
I only recently updated to 2004 and I was trying out "Edge Application Guard". "..Microsoft Edge opens the site in an isolated Hyper-V-enabled container..".
I didn't read far enough to figure out how it uses Hyper-V while Hyper-V is supposedly not installed.
Thanks for taking the time to reply Bree.

Yes, it had to be something that employed parts of Hyper-V. Containers are used for both Windows Sandbox and Edge Application Guard.

Funny ...
You accuse Bree of not reading your post.
Then you discover that your problem arose ... from not reading the Edge app guard document.
Can that document post a snippy reply? :)