Add IPv6 support

Comentários

74 comentários

  • advaith

    Here is Discord's statement from their December 2022 developer event:

    ipv6 status: we want to support this but it requires many complex changes to how we handle routing within our internal network. we are not actively working on these changes but combined with other projects and future work we want to do, it is likely we will support ipv6 at some point in the future.

    0
  • givetordlove

    Not much of a commitment in that statement. I realize that the Discord backend comes with a level of complexity, but I find it hard to believe that routing should be one of them. Without knowing much about the Discord internals, it is hard to say more.. But if they rely on FQDNs and not IP addresses, adding IPv6 in a dual-stack environment would at least be a start. They might be using IP Anycast, but that should also work fine with IPv6. I am sure if they really wanted to, they'd be able to sort this out.

    1
  • Null

    Florian, 

    They use i3D as supplier for the low-latency voice servers but that doesn't take away the fact that they do in fact use cloudflare as reverse proxy. Even for VC.

    When you connect to a voice server, you connect to 'rotterdam7980.discord.media' for instance. Proxied by CF. (IPv6 appears not to be disabled!)
    However when you dig a little deeper, CF proxies it to the following domain 'rotterdam7980.discord.gg'. Not proxied by CF. IPv6 disabled.

    Screenshot for further clarification:

    2
  • 7odaifa_ab

    in my region, we are maxed out of IPv4 since 2019, being behind a CG-NAT is really causing lots of issues to discord, I can only play with my friends with a VPN and it affects on latency, and other millions of users like I have the same issue, what I don't get is why discord not addressing this issue!

    2
  • nivex

    My support ticket for voice calls failing from an IPv6 (NAT64) network will have been open for one year as of tomorrow. As near as I can tell, I am the only one who has filed such a ticket. As such they don't appear to be dedicating any engineering resources to fixing the issue. If anyone else here can reproduce the issue and open a ticket, that would probably raise the importance more than posting here.

    Put another way: This forum seems to be for us talking to each other. Discord doesn't seem to be reading it.

    2
  • Eliah

    Yeah, my isp give us shared IPv4's and fully public IPv6 (DS-Lite) and discord lags a lot by being v4 only and if i turn v4 of my my router be sure everything will work except for Discord, and idk if they actually read this forum tbh like someone upside said at this point we're just talking one an other and discord not doing anything to fix this problem that will cost them money in the future

    1
  • Tech

    Same here, Discord is super laggy often due to DS-Lite, and at other times I'm on a V6 only network (mobile data) I can't even use it. Also the reason for me not to get Nitro since it is barely usable

    2
  • Brendan K.

    Discord, you should make this more of a priority. I understand that this will take some work, but you will need to do it eventually. Yall shouldn't wait until the last minute to implement something like this, you are already stopping potential customers from joining your platform due to some ISPs being IPv6 only. I think it is time to get IPv6 ready.

    0
  • IPv6

    I am gonna add a “+1” to this. I was shocked when I knew that DISCORD doesn't support IPv6.

    0
  • nivex

    I tried to follow up on my old ticket only to find it had been closed. I opened a new one, with references to the old one that has been open for a year (that they completely ignored), and eventually got this response:

    We have exhausted most of the troubleshooting steps that can be performed without a more in-depth look into your system configuration, the reason why we highly suggest you contact a trained computer technician in order to get further assistance in this matter. 
     
    That being said, I can let you know that we've escalated this to our teams, so you can be assured that we'll continue to keep a pulse on this issue moving forward. Additionally, as always, I would encourage keeping your client up to date, and it may be helpful to give some of the previous troubleshooting steps a try again in case they work.

    I was particularly amused at the “trained computer technician” bit. I think after >25 years in the field, I'm pretty well trained :) I don't particularly have the spoons to try and explain my bona fides to support again though.

    Despite assurances that the ticket has been escalated, I got the post-ticket survey email, where I obviously expressed my displeasure. I know responses are going to be slower during the holidays, but don't kill the ticket!

    Anyway, if anyone else out there wants to try tilting at this windmill along with me, that would be helpful. As it is I'm probably the only “weirdo” with a production IPv6-only network actually submitting tickets.

    0
  • Daniel Berry

    I moved my home network to IPv6 only with NET64 for connections to legacy IPs but the Discord app on windows just doesn't work in a setup like this. I'm trying to work out a way around it now but a better fix would be to just support IPv6 or at the very lest support NET64. The biggest ISP in Australia is going to be moving to IPv6 only with NET64 on all connections. you will really want this fixed before then or look at losing a lot of users.

    0
  • razmus

    AWS is now charging US$0.12/day just to have a public IPv4 address for each address, starting this month.  Sure would help me in my transitioning my discord bot to an IPv6 if discord supported IPv6.

    0
  • Roddy

    The money that I was gonna use for Discord Nitro is now going for an IPv4 address to my server only so my bots can reach the Discord servers. Good job Discord team.

    0
  • razmus

    Oh, good call.  I can step back from Nitro to Nitro:Basic so I can cover the change in my AWS bill.

    0

Por favor, entrar para comentar.