From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Brian Inglis <Brian.Inglis@Shaw.ca>
Subject: RE: [EXTERNAL] Re: Please support download setup-x86_64.exe on IPv6-only network
Date: Tue, 21 Nov 2023 18:11:42 +0000 [thread overview]
Message-ID: <DM8PR09MB7095F60B16110AB198C0AF1AA5BBA@DM8PR09MB7095.namprd09.prod.outlook.com> (raw)
In-Reply-To: <db86fa40-991c-4977-9bff-668cb28fff93@Shaw.ca>
> ::ffff:0:0:0/96 == ::ffff:0:a.b.c.d
https://www.ibm.com/docs/en/zos/2.1.0?topic=addresses-ipv4-mapped-ipv6
Mapped IPv4 addresses have the ::ffff:a.b.c.d short form, without any intervening 0 word. The CIDR form above just denotes that 96 bits
are the prefix (the "network" part) and, thus, the remaining 32 bits is the host part within the network. IPv6 addresses are 128 bit long.
But the ::ffff:0:a.b.c.d notation is not a mapped IPv4 address, it's just some IPv6 address which is written with last
four octets in the IPv4 notation (any IPv6 address can be accepted this way), but when you convert it back from its binary
form, that won't re-emerge the same way because only IPv4 compatible (all 96 leading bits zero) or IPv4 mapped (80 zero bits
followed by 16 one bits) followed by 4 bytes of IPv4 address) can be conventionally written in the IPv4 form (depending
on the system settings).
E.g. 1.2.3.4 (input) -> (binary rep) ::ffff:1.2.3.4 -> (output) 1.2.3.4
but
::ffff:0:1.2.3.4 -> (binary rep, same) -> (output) ::ffff:0:102:304
HTH,
Anton Lavrentiev
Contractor NIH/NLM/NCBI
next prev parent reply other threads:[~2023-11-21 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 1:40 Bin W
2023-11-16 7:13 ` Martin Wege
2023-11-16 10:18 ` Adam Dinwoodie
2023-11-16 20:40 ` Brian Inglis
2023-11-21 0:12 ` Backwoods BC
2023-11-21 0:45 ` Lee
2023-11-21 5:35 ` Brian Inglis
2023-11-21 7:36 ` Backwoods BC
2023-11-21 8:01 ` Lee
2023-11-21 18:11 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2023-11-20 13:55 ` Jon Turney
2023-11-20 23:58 ` Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM8PR09MB7095F60B16110AB198C0AF1AA5BBA@DM8PR09MB7095.namprd09.prod.outlook.com \
--to=lavr@ncbi.nlm.nih.gov \
--cc=Brian.Inglis@Shaw.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).