No IPv6 inside WDAG, Sandbox and Hyper-V - Windows 10 Pro, v 1909

%3CLINGO-SUB%20id%3D%22lingo-sub-1262975%22%20slang%3D%22en-US%22%3ENo%20IPv6%20inside%20WDAG%2C%20Sandbox%20and%20Hyper-V%20-%20Windows%2010%20Pro%2C%20v%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262975%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone!%20Thanks%20for%20reading%20this!%3C%2FP%3E%3CP%3EI%20have%20tested%20my%20IPv6%20connectivity%20on%20my%20Windows%2010%20Pro%20v1909%20using%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftest-ipv6.com%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftest-ipv6.com%2F%3C%2FA%3E%26nbsp%3B%20and%20I%20have%20IPv6%20available%20on%20my%20machine.%20It%20reports%2010%2F10%20tests%20ok.%20Nice!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20when%20I%20repeat%20the%20same%20test%20inside%20Windows%20Defender%20Application%20Guard%20(WDAG)%20for%20Edge%20and%20Windows%20Sandbox%20I%20am%20informed%20that%20I%20have%20no%20IPv6%20at%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20make%20matters%20worse%2C%20I%20have%20installed%20Hyper-V.%20I%20have%20created%20an%20Hyper-V%20Virtual%20Switch%2C%20type%20%22external%22%2C%26nbsp%3B%20which%20%22wraps%22%20the%20wifi%20net%20adapter.%20The%20result%3A%20the%20first%20test%20which%20reported%20ok%20now%20reports%20no%20IPv6%20at%20all.%20Of%20course%2C%20WDAG%20and%20Sandbox%20continue%20to%20report%20no%20IPv6.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20one%20might%20expect%20from%20above%20scenario%2C%20my%20Virtual%20Machine%20(another%20Windows%2010%20Pro%20v1909%20run%20via%20Hyper-V%20and%20the%20aforementioned%20external%20vSwitch%20)%20sees%20no%20IPv6%20at%20all.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20thing%20I%20have%20tried%20to%20solve%20the%20problem%20was%20to%20enable%20Routing%20and%20Remote%20Access%2C%20setting%20it%20to%20Automatic%20and%20Automatic%20(delayed%20start).%20No%20luck.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENonetheless%2C%20IPv4%20continues%20to%20work%20fine%20(otherwise%20I%20would%20not%20be%20able%20to%20create%20and%20type%20this%20thread!).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20anyone%20have%20any%20idea%20I%20would%20be%20glad%20to%20hear.%3C%2FP%3E%3CP%3EThanks%20for%20your%20attention.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-----------------------------------------%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAddendum%3A%20for%20further%20details%2C%20please%20have%20a%20look%20at%20my%20post%20on%20the%20following%20thread%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fwindows%2Fen-US%2Fa6108ab3-c7b8-4fd2-aaf2-51f9b2bec9f4%2Fipv6-route-advertisement-not-forwarded-by-hyperv-default-switch-windows-10-1909-to-guest-vms%3Fforum%3Dwin10itprovirt%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EIPV6%20Route%20Advertisement%20not%20forwarded%20by%20Hyper-V%20Default%20Switch%20(Windows%2010%201909)%20to%20guest%20VM's%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi everyone! Thanks for reading this!

I have tested my IPv6 connectivity on my Windows 10 Pro v1909 using https://test-ipv6.com/  and I have IPv6 available on my machine. It reports 10/10 tests ok. Nice!

 

However, when I repeat the same test inside Windows Defender Application Guard (WDAG) for Edge and Windows Sandbox I am informed that I have no IPv6 at all.

 

To make matters worse, I have installed Hyper-V. I have created an Hyper-V Virtual Switch, type "external",  which "wraps" the wifi net adapter. The result: the first test which reported ok now reports no IPv6 at all. Of course, WDAG and Sandbox continue to report no IPv6.

 

As one might expect from above scenario, my Virtual Machine (another Windows 10 Pro v1909 run via Hyper-V and the aforementioned external vSwitch ) sees no IPv6 at all. 

 

The only thing I have tried to solve the problem was to enable Routing and Remote Access, setting it to Automatic and Automatic (delayed start). No luck.

 

Nonetheless, IPv4 continues to work fine (otherwise I would not be able to create and type this thread!).

 

If anyone have any idea I would be glad to hear.

Thanks for your attention.

 

-----------------------------------------

 

Addendum: for further details, please have a look at my post on the following thread:

IPV6 Route Advertisement not forwarded by Hyper-V Default Switch (Windows 10 1909) to guest VM's 

0 Replies