search

discord / discord-api-docs

Official Discord API Documentation
https://discord.com/developers/docs/intro
Other
6k stars 1.26k forks source link

Cannot connect with IPv6 #6969

Closed crocofied closed 5 months ago

crocofied commented 5 months ago

Description

We have 2024, so I can only think about it as a bug. How can it be that an application like Discord does not support IPv6 yet? And please don't tell me that this is intentional and that IPv4 is deeply rooted in your system. Systems can be rewritten and the time when people only relied on IPv4 is long gone. I and thousands of other devs and sys admins have long since turned their backs on IPv4 for certain things due to extremely high prices. We finally need IPv6 support!

Steps to Reproduce

Just try to make an api request from an ipv6 device only

Expected Behavior

It should work

Current Behavior

It doesn’t

Screenshots/Videos

No response

Client and System Information

IPv6 only

GoldenAngel2 commented 5 months ago

Not a bug, it's intended (also duplicate):

See comments from Discord Staff regarding it:

Luna-devv commented 5 months ago

I wouldn’t call such “not a bug, it’s intended” anymore - a very large part of the internet nowadays uses IPv6, and the numbers will only continue to grow. More and more home/consumer IPs are IPv6 only

https://www.google.com/intl/en/ipv6/statistics.html

crocofied commented 5 months ago

Yes and this is exactly why i cannot understand, discord is not adding ipv6 support on their end or at least at their api

Rodentman87 commented 5 months ago

We still do not currently support IPv6 at this time as there are still internal systems that depend on IPv4 addresses that haven't been upgraded to support IPv6

Rapptz commented 5 months ago

Why not leave an issue open to track it for everyone else instead of the whack-a-mole currently being done?

crocofied commented 5 months ago

This is a great idea!

booth-f commented 3 months ago

Not a bug, it's intended (also duplicate):

See comments from Discord Staff regarding it:

* [Cannot connect on IPv6 #6695 (comment)](https://github.com/discord/discord-api-docs/issues/6695#issuecomment-1977302538)

* [Cannot connect on IPv6 #6695 (comment)](https://github.com/discord/discord-api-docs/issues/6695#issuecomment-2051952479)

* [Cannot connect on IPv6 #6695 (comment)](https://github.com/discord/discord-api-docs/issues/6695#issuecomment-2052085681)

All do respect, this is absolutely not acceptable as something to just close as "working as intended".

Understand that mobile carriers have already made the transition to IPv6-only networks and rely on NAT64 translation methods (RFC 6877 464XLAT) to keep IPv4-only resources reachable. To do this they force users to what is called a CGNAT address, this means many users on the carrier network share a single public IPv4 address. What this means in practice is that Discord's security is severely hindered in the process. I do not think Discord and their staff understand the severity of continuing to disregard IPv6 is going to cost the business in both user experience (degraded through CGNAT gateways that occasionally get overloaded) and in users who will be unable to reach the service as ISPs start phasing out IPv4. As already mentioned, there are networks that exist today where Discord is completely unreachable because these networks are IPv6-only.

How does this impact Discord's security you may ask? Blocking a single bad actor on IPv4 will block more than just the trouble user, you may block an entire region of people from your service. This is not ideal for any cyber security posture and only angers the users who just happen to be caught in the crosshairs.

Continuing to shrug off a protocol that has been standardized for over 20 years is absolutely not defensible. Face the music, IPv4 is the minority protocol as far as traffic handling on the Internet is concerned.

According to Google's own stats on the matter a fair number of countries have achieved 50%, close to, or higher traffic split that favors IPv6.

Germany - 72.53% France - 72.41% Malaysia - 66.70% Saudi Arabia - 60.48% Greece - 57.26% Japan - 53.19% US - 52.33% Hungary - 51.16% Brazil - 50.07% Puerto Rico - 49.62% Mexico - 49.62% Canada - 40.75%

Source

Would you kindly reconsider opening the issue and getting IPv6 on the roadmap?