Across the examples here we get smatterings of gateways and subnets, in some cases of existing host or container ranges. I think it would be useful if the examples were more representative of a container and container host - so where we get an example of (say) 10.0.244.0/24 we see that the out of the box nat might have had 192.168.48.1 on the host, and the container ipconfig might show that the container was (say) 192.168.49.2 and show that original ip (192.168.48.1) as its gateway and one of its dns servers.
From that basis then the nat or transparent or overlay examples could then show a potential/reasonable modification rather than just the 10.x without the context.
I also note at Windows 2022, the overlay needs vni(s) and out of the box in Azure my NIC have a 0 value.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 556473c3-3630-dc56-caad-a3d72d34e9e1
Version Independent ID: 560ad6ca-e017-db71-4605-a73e9f1b8aed
Across the examples here we get smatterings of gateways and subnets, in some cases of existing host or container ranges. I think it would be useful if the examples were more representative of a container and container host - so where we get an example of (say) 10.0.244.0/24 we see that the out of the box nat might have had 192.168.48.1 on the host, and the container ipconfig might show that the container was (say) 192.168.49.2 and show that original ip (192.168.48.1) as its gateway and one of its dns servers.
From that basis then the nat or transparent or overlay examples could then show a potential/reasonable modification rather than just the 10.x without the context.
I also note at Windows 2022, the overlay needs vni(s) and out of the box in Azure my NIC have a 0 value.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.