Add IPv6 support
Add IPv6 support to all discord services.
- IPv6 offers lower latency
- Many ISPs sell IPv6 with shared IPv4 addresses (Dualstack Lite) only. This often leads to a poor connection quality for IPv4 connections.
- Some internet providers, especially in poorer regions, will only sell IPv6 in the future.
- IPv4 is hitting it's limits. This leads to higher prices which will be forwarded to customers.
- The standard is out for over 20 years. It's about time I think.
-
I just encountered hurt feelings and unnecessary vengeance, due to an IP block that on IPv4 affected unintended targets. Discord is causing literal discord by disabling IPv6.
5 -
Somebody clipped the cable on the right?
src: https://chrisgrundemann.com/index.php/2011/nat444-cgn-lsn-breaks/
5 -
It's particularly amusing that Discord now loads over HTTP/3, a protocol that has not yet been ratified by the IETF, but still does not load over IPv6, which was made an Internet Standard four years ago.
2 -
While waiting, why not playing at the justification for not deploying ipv6 bingo? https://ipv6bingo.com/
2 -
IPv4 addresses is already run out so please do native IPv6 support Discord
1 -
Wake up team
1 -
Hetzner solds dedicated servers without IPv4 now (you must pay extra 2 EUR per month to get IPv4). Discord API doesn't work on IPv6-only servers.
1 -
For years the common response has been "no one would run an IPv6-only network". Well, now they're here.
Fire up a bot or other such API-using app on one of these servers, then open up a support ticket with the actual logged error message you get. It will probably be something like "No route to host", "Network unreachable" or just a plain could not establish connection. Whatever it is, include it as is and don't let on that it's an IPv6-only issue. Make support figure it out. Then once they do and they try to give you the "We don't support that", remind them that this is an actual system in the wild and not some lab environment and that you'd like some estimation of when this problem will be fixed.
4 -
Why can't we have nice things?
2 -
Why? Greed. Discord is still making mad bank, so they have no incentive to fix this.
And, well, we can have nice things. We just have to look elsewhere. There are plenty of services out there that are IPv6 enabled today.
3 -
Enabling IPv6 would allow many more users to connect to Discord's services, so there's definitely a financial incentive to fix this. I think this is a just a problem of ignorance.
6 -
Adding my voice in favour of IPv6 support!
4 -
I would also really appreciate IPv6 support. Discord is the only thing keeping me from disabling IPv4 at the moment.
At least make voice/video work with NAT64/DNS64 . Try to avoid using IPv4 literals.
3 -
Please file a ticket with support about media not working in NAT64/DNS64. "This is broken in my environment" carries a lot more weight than "This would be nice to have."
4 -
+1 here
As for the nat64, I have opened an issue with discord, but the guy that's handling me is completely ignoring me mentioning "nat64" and asking questions like "can you run the app as admin", the dumb part? I'm using the browser version and I told him that...
2 -
Same here. As I expected.
A bot also keeps automatically closing the ticket every week requiring a response to reopen it. Amazing stuff.
1 -
It has been 8 months and this not only happens to Discord website, but also when I tried to host my bot in VPS with only IPv6 address (no IPv4) and I don't want to paid for IPv4 address. Please add IPv6 support so I can host my bot in my VPS
2 -
Still no IPv6 on Discord in 2022 !
My ISP have now IPv4 as a paid option since less and less services are IPv4-only.
And because Discord doesn't work in IPv6 nor NAT64 I will have to leave the platform or pay for the IPv4 option (funny enough it's the same price as discord nitro :)).
2 -
Hello!
I am for adding this protocol.
I am in Ukraine and my provider now provides only IPv6 and the Service does not open with it. Other popular messengers support this protocol. I recommend to add support for this protocol as soon as possible.
1 -
Hi Kravchenko Andrii Oleksiiovych, would you mind telling me which internet provider you're referring to?
1 -
Hello!
Triolan.
1 -
I don't understand how it can take this long for them.
0 -
bro
it takes the piss that this still isn't a thing.
We've had ipv6 since '98 and yet its not supported by the largest chat application in 2022.C'mon, the protocol is 24 years old and yet MODERN chat applications still haven't grasped how to make it work (probably gonna work if you reenable it on cloudflare!)
0 -
I don't understand how it can take this long for them.
Simple: Inertia and money.
Discord, as it exists today, works for nearly 100% of its intended audience. To add IPv6 support would require both infrastructure and code engineering support. Those resources cost money and therefore cut into their profit. Why mess with the money printing machine?
At this moment, this feature request has 85 followers. How does that compare to other requests in other sections of this forum? It's probably a pittance. So while we here may understand the importance, to the bean counters it's a pure numbers game. All cost, no gain.
I finally got around to following my own suggestion I made months ago: I have a support ticket open for voice not working on my NAT64/DNS64 network. I went through all the same fun others reported (Did you reboot everything? Can you run Malwarebytes?) I've indulged them on this, because for most problems in their model, this fixes it. At no point have I let on that my network is different from that model. We're going through the whole process. Why? Because this is my operational network. It works. Their stuff doesn't. They're going to need to figure out how to solve this *problem*. Not feature request. Problem.
I continue to encourage others to get their environments configured and submit issue reports. An attached log from a real environment is worth more than a bunch of hypotheticals. As ARIN said in their slogan: "IPv6: It's not new, it's now."
0 -
Discord, as it exists today, works for nearly 100% of its intended audience. To add IPv6 support would require both infrastructure and code engineering support. Those resources cost money and therefore cut into their profit. Why mess with the money printing machine?
At this moment, this feature request has 85 followers. How does that compare to other requests in other sections of this forum? It's probably a pittance. So while we here may understand the importance, to the bean counters it's a pure numbers game. All cost, no gain.
This is a huge misconception. You only think about the audience Discord already serves, but what about all the potential users which don't even consider Discord because they can't connect? Also even if they cared, how are they supposed to write here? This forum is ipv4 only too.
1 -
You don't understand, Discord can't sell IPv6 as a nitro feature, as such it's not important!
0 -
It's 2023, still not support IPv6.
0 -
I have a support ticket open for voice not working on my NAT64/DNS64 network.
Whew, finally able to get logged back in to this forum! This ticket is still open. They keep throwing a "Try it now" over the wall and I keep sending back a "nope". The most recent message they asked if I went and got help on the Linux Discord. I booted this laptop into Windows (thankfully I still can) and reproduced the issue and sent in the debug logs. At some point this was supposedly escalated to engineering, but I'm questioning that. In my most recent reply I begged them to have an engineer contact me directly so we can discuss this on a quick call.
Those of you filing tickets: keep it up! The more support time this takes will hopefully show up on their metrics and cause it to rise in the priority list.
0 -
So let's take a look at this nslookup result of Discord and other chat platform
Another chat platform (known as Revolt) have IPv6 support via Cloudflare, meanwhile Discord doesn't have it even though they use Cloudflare
0 -
Discord doesn't use Cloudflare for their voice servers.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
64 Kommentare