Round-trip an IPv4-mapped address from a saved log
Admin ·
A test inventory contains a dotted IPv4 address and a hexadecimal address from another program. Use the mapped form to tell whether they carry the same four IPv4 octets.
IPv4 and IPv6 Address Converter
Compare the two mapped spellings
Load the example and choose Convert address. The IPv4 value is 192.0.2.37. Mapped IPv6 shows ::ffff:192.0.2.37 and the compressed hexadecimal form shows ::ffff:c000:225.
Replace the input with 0000:0000:0000:0000:0000:FFFF:C000:0225. Convert again. The IPv4 output returns 192.0.2.37, and the mapped notation stays the same.
RFC 4291, IPv4-mapped IPv6 addressesRFC 5952, handling IPv4-embedded IPv6 addresses
Identify an address with different semantics
Try 2001:db8::37. The tool reports that it falls outside ::ffff:0:0/96. Its last four bytes don’t establish a mapped IPv4 value.
The tool accepts a literal address. Remove brackets and any port displayed around the address before checking the literal itself.
Check which form you are saving
The Converted address field gives the output of the direction you just ran. The TXT file contains the same value. Copy from the corresponding display row if your project needs the alternative form.
For an inventory comparison, decide whether your source uses mapped IPv6 representations or records IPv4 and IPv6 as separate address families.
Common questions
Does using the mapped form change the four IPv4 bytes?
The four bytes stay the same. The mapping adds the standard IPv6 prefix before those bytes.
Is a NAT64 address handled here?
Reverse conversion uses ::ffff:0:0/96. NAT64 uses translation prefixes with their own rules.