IPv4-Mapped IPv6 Address - Revision history

Heth: /* IP Addresses with a Dual-Stack Socket */

2011-11-25T07:29:22Z

‎IP Addresses with a Dual-Stack Socket

Heth: /* IP Addresses with a Dual-Stack Socket */

2011-11-25T07:28:32Z

‎IP Addresses with a Dual-Stack Socket

Heth at 07:27, 25 November 2011

2011-11-25T07:27:50Z

Heth at 07:07, 25 November 2011

2011-11-25T07:07:36Z

Heth at 06:23, 25 November 2011

2011-11-25T06:23:59Z

Heth at 06:23, 25 November 2011

2011-11-25T06:23:06Z

Heth at 06:20, 25 November 2011

2011-11-25T06:20:18Z

Heth at 06:20, 25 November 2011

2011-11-25T06:20:03Z

Heth at 09:06, 12 June 2011

2011-06-12T09:06:46Z

Heth: IPv4-Mapped moved to IPv4-Mapped IPv6 Address

2011-06-12T09:03:15Z

IPv4-Mapped moved to IPv4-Mapped IPv6 Address

@@ Line 23: / Line 23: @@
 If the underlying protocol is actually IPv4, then the IPv4 address is mapped into an IPv4-mapped IPv6 address format. That is the, family field in the SOCKADDR structure indicates AF_INET6, but an IPv4-mapped IPv6 address is encoded in the IPv6 address structure. For a dual-stack socket in listening mode, this means that any accepted IPv4 connections will return an IPv4-mapped IPv6 address. For a dual-stack socket that is connecting to an IPv4 destination, the SOCKADDR structure passed to connect must be an IPv4-mapped IPv6 address. Applications must take care to handle these IPv4-mapped IPv6 addresses appropriately and only use them with dual stack sockets. If an IP address is to be passed to a regular IPv4 socket, the address must be a regular IPv4 address not a IPv4-mapped IPv6 address.<ref>http://msdn.microsoft.com/en-us/library/windows/desktop/bb513665(v=vs.85).aspx</ref>
 <source lang=cli>
 <input>
@@ Line 57: / Line 59: @@
 </input>
 </source>
 <references/>
 {{source cli}}

@@ Line 57: / Line 57: @@
 </input>
 </source>
-</references>
+<references/>
 {{source cli}}

@@ Line 14: / Line 14: @@
 }}
 IPv4-mapped IPv6 addresses are used in scenarios where IPv6 an IPv6-only application need to communicate with an IPv4 only application using IPv4 packets.
 =IP Addresses with a Dual-Stack Socket=
 Dual-stack sockets always require IPv6 addresses. The ability to interact with an IPv4 address requires the use of the IPv4-mapped IPv6 address format. Any IPv4 addresses must be represented in the IPv4-mapped IPv6 address format which enables an IPv6 only application to communicate with an IPv4 node. The IPv4-mapped IPv6 address format allows the IPv4 address of an IPv4 node to be represented as an IPv6 address. The IPv4 address is encoded into the low-order 32 bits of the IPv6 address, and the high-order 96 bits hold the fixed prefix 0:0:0:0:0:FFFF. The IPv4-mapped IPv6 address format is specified in RFC 4291. For more information, see www.ietf.org/rfc/rfc4291.txt. The IN6ADDR_SETV4MAPPED macro in Mstcpip.h can be used to convert an IPv4 address to the required IPv4-mapped IPv6 address format.
-If the underlying protocol is actually IPv4, then the IPv4 address is mapped into an IPv4-mapped IPv6 address format. That is the, family field in the SOCKADDR structure indicates AF_INET6, but an IPv4-mapped IPv6 address is encoded in the IPv6 address structure. For a dual-stack socket in listening mode, this means that any accepted IPv4 connections will return an IPv4-mapped IPv6 address. For a dual-stack socket that is connecting to an IPv4 destination, the SOCKADDR structure passed to connect must be an IPv4-mapped IPv6 address. Applications must take care to handle these IPv4-mapped IPv6 addresses appropriately and only use them with dual stack sockets. If an IP address is to be passed to a regular IPv4 socket, the address must be a regular IPv4 address not a IPv4-mapped IPv6 address.
+If the underlying protocol is actually IPv4, then the IPv4 address is mapped into an IPv4-mapped IPv6 address format. That is the, family field in the SOCKADDR structure indicates AF_INET6, but an IPv4-mapped IPv6 address is encoded in the IPv6 address structure. For a dual-stack socket in listening mode, this means that any accepted IPv4 connections will return an IPv4-mapped IPv6 address. For a dual-stack socket that is connecting to an IPv4 destination, the SOCKADDR structure passed to connect must be an IPv4-mapped IPv6 address. Applications must take care to handle these IPv4-mapped IPv6 addresses appropriately and only use them with dual stack sockets. If an IP address is to be passed to a regular IPv4 socket, the address must be a regular IPv4 address not a IPv4-mapped IPv6 address.<ref>http://msdn.microsoft.com/en-us/library/windows/desktop/bb513665(v=vs.85).aspx</ref>
 <source lang=cli>
@@ Line 53: / Line 57: @@
 </input>
 </source>
 {{source cli}}

@@ Line 14: / Line 14: @@
 }}
 IPv4-mapped IPv6 addresses are used in scenarios where IPv6 an IPv6-only application need to communicate with an IPv4 only application using IPv4 packets.
 <source lang=cli>
 <input>

@@ Line 16: / Line 16: @@
 <source lang=cli>
 <input>
-C:\Users\Henrik thomsen><notice>ping ::ffff:192.168.146.1</notice>
+C:\Users\Henrik thomsen><notice>ping ::ffff:192.168.139.50</notice>
-Pinging 192.168.146.1 with 32 bytes of data:
+Pinging 192.168.139.50 with 32 bytes of data:
-Reply from 192.168.146.1: bytes=32 time=1ms TTL=255
+Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
-Reply from 192.168.146.1: bytes=32 time=1ms TTL=255
+Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
-Reply from 192.168.146.1: bytes=32 time=2ms TTL=255
+Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
-Reply from 192.168.146.1: bytes=32 time=2ms TTL=255
+Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
-Ping statistics for 192.168.146.1:
+Ping statistics for 192.168.139.50:
      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
 Approximate round trip times in milli-seconds:
-     Minimum = 1ms, Maximum = 2ms, Average = 1ms
+     Minimum = 0ms, Maximum = 0ms, Average = 0ms
 </input>
 </source>

← Older revision		Revision as of 06:20, 25 November 2011
Line 30:		Line 30:
	</input>		</input>
	</source>		</source>
		+	{{source cli}}

← Older revision		Revision as of 06:20, 25 November 2011
Line 13:		Line 13:
	See [http://tools.ietf.org/html/rfc4038 RFC 4038] for more details		See [http://tools.ietf.org/html/rfc4038 RFC 4038] for more details
	}}		}}
		+	IPv4-mapped IPv6 addresses are used in scenarios where IPv6 an IPv6-only application need to communicate with an IPv4 only application using IPv4 packets.
		+	<source lang=cli>
		+	<input>
		+	C:\Users\Henrik thomsen><notice>ping ::ffff:192.168.146.1</notice>
		+
		+	Pinging 192.168.146.1 with 32 bytes of data:
		+	Reply from 192.168.146.1: bytes=32 time=1ms TTL=255
		+	Reply from 192.168.146.1: bytes=32 time=1ms TTL=255
		+	Reply from 192.168.146.1: bytes=32 time=2ms TTL=255
		+	Reply from 192.168.146.1: bytes=32 time=2ms TTL=255
		+
		+	Ping statistics for 192.168.146.1:
		+	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
		+	Approximate round trip times in milli-seconds:
		+	Minimum = 1ms, Maximum = 2ms, Average = 1ms
		+	</input>
		+	</source>

@@ Line 5: / Line 5: @@
   |GlobalRouteable = Yes
   |GlobalUnique    = Yes
-  |Desc1           = [http://tools.ietf.org/html/rfc4038#section-4.2 rfc4038 section 4.2]
+  |Desc1           = [http://tools.ietf.org/html/rfc4291 rfc4291]
   |CompareIPv4     =  None
   |Example         = ::ffff:83.90.47.30

← Older revision	Revision as of 09:03, 12 June 2011
(No difference)