[wp-meta] [Making WordPress.org] #3090: WordPress.org API not accessible over IPv6
Making WordPress.org
noreply at wordpress.org
Mon Mar 4 02:07:10 UTC 2024
#3090: WordPress.org API not accessible over IPv6
-------------------------+-------------------------
Reporter: deaky | Owner: (none)
Type: enhancement | Status: closed
Priority: high | Milestone:
Component: API | Resolution: maybelater
Keywords: |
-------------------------+-------------------------
Changes (by dd32):
* status: reopened => closed
* resolution: => maybelater
Comment:
I've escalated this to a Systems request;
https://make.wordpress.org/systems/2024/03/04/ipv6-support/ for tracking
and feedback from the network/systems administrators.
While I understand your interest, and frustration caused by providers who
provide limited services not designed for hosting popular applications,
the same reason why those providers don't provide IPv6-to-4 gateways and
why WordPress.org hasn't deployed IPv6 is very similar.
Keeping this ticket open isn't helpful to us, as we (The Meta team of
WordPress.org) are unable to influence this, and those who run the
systems/network side of WordPress.org don't follow tickets here actively.
IPv6 support will be made available at some stage; but it's my opinion
that it'll likely only happen with a significant infrastructure redesign,
which is unlikely to have any priority to it.
----
Similar to the above comments on this ticket;
> AWS EC2 instance to IPv6-only connectivity
DNS64 is available for the purpose of providing IPv4 connectivity for
outgoing requests on AWS services; I've not used it, but it appears to
exist.
https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-
nat64-dns64.html#nat-gateway-nat64-dns64-walkthrough-internet
> most mobiles do v6-only [..] while on cellular connectivity
All IPv6 deployments that I've heard of in the mobile scene will be using
a NAT64 approach; while to the client it may seem like IPv6 only, it still
has IPv4 connectivity ability. IPv6 in the mobile industry was heavily
encouraged by VoLTE And their historic use of CGNAT/NAT44 (IPv4 NAT)
devices, which is a very different scale than hosting deployments.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3090#comment:20>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list