From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: Please support download setup-x86_64.exe on IPv6-only network
Date: Thu, 16 Nov 2023 13:40:35 -0700 [thread overview]
Message-ID: <635d3f94-f104-49e0-9248-1cace4da9fa6@Shaw.ca> (raw)
In-Reply-To: <20231116101858.vxbvtipwtvwucwjs@lucy.dinwoodie.org>
On 2023-11-16 03:18, Adam Dinwoodie via Cygwin wrote:
> On Thu, Nov 16, 2023 at 08:13:30AM +0100, Martin Wege via Cygwin wrote:
>> On Thu, Nov 16, 2023 at 2:40 AM Bin W via Cygwin wrote:
>>>
>>> https://www.cygwin.com/setup-x86_64.exe
>>> IPv6-only network can't download the installer.
>>
>> Details please. Does
>> https://www.cygwin.com/setup-x86_64.exe
>> not work on an IPv6-only network?
>>
>> Or can setup-x86_64.exe not download data on an IPv6 network?
>
> I've just checked: cygwin.com and www.cygwin.com only have DNS A
> records, no AAAA records, so there's no way to get the installer (or
> indeed anything else) from cygwin.com if you're on an IPv6-only network.
There are many other org and ISP issues that could block Cygwin access, like
A/V, End Point Protection, GPO, firewall, but that may also mean that they do
not support compatible transitional services and interconnection designed to
make the difference transparent, possibly except to allowed domains or hosts,
similarly to depending on insecurity-featuring-obscurity.
> Fixing this will require setting up the web servers for cygwin.com to be
> accessible over IPv6, and configuring the corresponding IPv6 addresses
> in the domain's DNS records.
The whole IP v4 internet is available as a compatibility subnet ::ffff:0:a.b.c.d
on IP v6, so there is no excuse for not supporting interconnection, as it will
be required until the last backbone routers drop IP v4 support.
If the OP's org or ISP do not support interconnections to IP v4 hosts, they may
not have the competence or knowledge to configure and run the appropriate stacks
and services to support transitional 6over/to4-4over/to6 interconnections, as
most other hosts and routers on the Internet still do, or it may be policy.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-11-16 20:40 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 [this message]
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 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
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=635d3f94-f104-49e0-9248-1cace4da9fa6@Shaw.ca \
--to=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).