IPv4-Mapped IPv6 Address
From Teknologisk videncenter
IPv4 Mapped
| IPv6 Address Type: | IPv4 Mapped |
| Prefix: | ::ffff/96 |
| Local Routeable: | Yes |
| Global Routeable: | Yes |
| Global Unique: | Yes |
| Example: | ::ffff:83.90.47.30 |
| IPv4 Equivalent: | None |
| Described in: | rfc4291 |
| rfc4038 section 4.2 | |
Explanation
These addresses are used to embed IPv4 addresses in an IPv6 address. One use for this is in a dual stack transition scenario where IPv4 addresses can be mapped into an IPv6 address.
See 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.
<input>
C:\Users\Henrik thomsen><notice>ping ::ffff:192.168.139.50</notice>
Pinging 192.168.139.50 with 32 bytes of data:
Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
Ping statistics for 192.168.139.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
</input>or same as
<input>
C:\Users\Henrik thomsen><notice>ping ::ffff:c0a8:8b32</notice>
Pinging 192.168.139.50 with 32 bytes of data:
Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
Reply from 192.168.139.50: bytes=32 time<1ms TTL=62
Ping statistics for 192.168.139.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
</input>