![]() ![]() Windows machines (dual stack enabled with IPv4 and IPv6) that are configured with public range IPv4 address (.y for example) in your network will have a default behavior to generate 6to4 tunneling address. Dual Stack Default Behavior and 6to4 Tunneling Addresses If you are one of the people who had deployed public range of IPv4 addresses in your internal network, you’ll want to pay attention below. Technically there is nothing that may prevent you to deploy public range of IPv4 addresses in your internal network. While it is not common to deploy public range of IPv4 addresses in your internal network, people may still do it for various reasons. ![]() If you had deployed your IPv4 addressing range other than one of the above three blocks of addresses, then probably you would have deployed one of the public facing range of addresses. If you have the patience and time to read RFCs, you can get more details on this topic from. In short, these addresses cannot be used for globally routed Internet traffic and can be deployed within corporate network for Intranet traffic. The following three blocks of addresses in IPv4 world are treated as private range addresses. Today we will discuss a special scenario when you have public ranges of IPv4 addressing deployed in your internal network. ![]() We discussed in my previous post IPv6 for the Windows Administrator: How Name Resolution Works in a Dual IPv4/IPv6 Scenario and talked about the behavior when using a private IP address range. ![]() Hello, this is Venkat Kalyanasundaram back with another IPv6 post for everyone. First published on TechNet on Nov 17, 2013 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |