Fix Peer Cache limit to subnet
Currently peer cache is still not a usable feature. We have found that all systems see themselves on the same subnet because of the Teredo Tunneling Adapter. They are all on the same IPv6 subnet. This has almost been found by a 3rd party vender (https://2pintsoftware.com/peer-cache-1806/). As Peer Cache is now a release feature and not pre-release, this should be fixed ASAP as it is a broken feature.
This is fixed both in 1810, and in the 1806 HFRU.
We are still experiencing this issue in 1810. Noticing in the ContentTransferManager log that the SUBNETPEER is pointing to a PC in a completely different subnet.
Was this actually fixed in a 1806hfru? I can't find any mention of it in any release notes.
In 1810, Teredo address is removed in subnet mapping for option “During peer downloads, only use peers within the same subnet”. With this option checked, only peer source in the same boundary group and within the same subnet will be used. The peer source within the same subnet but outside the boundary group is not used. If you see different behavior, do you mind to share your configuration? Boundary, boundary group, boundary group option, client and peer source IPs/subnet masks and build number, we will look into it.