Good to know, thanks for posting. I didn't get round to making a ticket due to IRL things but did just add my voice to the one already open. It appears the September update disabled it. Oh well, I only wanted to see if I had less server disconnects. I'll just wait for the next patch.I received this reply today from Frontier Support:
This is not something that has been brought to our attention. We have not disabled Ipv6, nor are we aware of other players experiencing this issue. What exactly is preventing you from enabling IPV6?
Could you please provide us with a screenshot of the Network options available to you so that we can see for ourselves?
So presumably it would be helpful if others with this issue could submit tickets on the frontier support site, thanks. https://support.frontier.co.uk
Do you have a link to your ticket? I'd gladly add a voice to it. IPv6 is working, active and usable, just not in Elite Dangerous.Got a further reply from support:
"Looking at your Netlog, it would seem that your NIC is not reporting an IPv6 address to us at all: ..... "
So washing their hands it seems since my PC reports an IPv6 address to other sources. It seems to me that it must be down to the netlog not showing IPv6 since the game is permanently set to IPv6 disabled.
Needless to say I am rejecting this fob-off and re-opening the ticket. How is anyone else getting on?
Do you have a link to your ticket? I'd gladly add a voice to it. IPv6 is working, active and usable, just not in Elite Dangerous.
ETA I posted on a ticket that has been open since the September update (ticket was dated end of September IIRC). I managed to find 2 tickets both reporting the same problem with several people adding their confirmation of brokenness.
IPv6="1" in your AppConfigLocal.xml...after making sure IPv6 is fully functional elsewhere.
So was I, once upon a time. Do you play in Open? I ask because many of us are still on IPv4, and in a P2P network, I wonder what advantage there is to using IPv6 when ED is going to have to "downgrade" to IPv4 to talk to computers like my own. I suppose you get some advantages for traffic between you and the servers, especially if your ISP is IPv6 only and is doing a conversion on IPv4 traffic.With all due respect, I am a sys/network admin. The IPv6 internet connection from my provider is native and active and on my NIC too. Windows 10, if that makes a difference.
IPv6="1" in your AppConfigLocal.xml...after making sure IPv6 is fully functional elsewhere.
I've been out of IT for a few years myself. I hit 40 and couldn't find an employer anymore. From what I understand the world or large parts of it at least were supposed to upgrade to IPv6 eventually. As to benefits, I was hoping to use it to test if my server drops decrease. I get them fairly frequently sometimes but restarting the game immediately connects to a server again..Strange. It's usually just as I locate or crack a core asteroid too.So was I, once upon a time. Do you play in Open? I ask because many of us are still on IPv4, and in a P2P network, I wonder what advantage there is to using IPv6 when ED is going to have to "downgrade" to IPv4 to talk to computers like my own. I suppose you get some advantages for traffic between you and the servers, especially if your ISP is IPv6 only and is doing a conversion on IPv4 traffic.
Anyway, just curious....
Disabled IPv6 on my network card in Windows 10. Internet works fine, most sites I use are reachable via IPv6. So I go to start the game via the launcher. The loader page opens with a blank screen (presumably it can't reach the page that contains the latest Galnet (?) articles one is usually greeted with in the launcher. Click on the Start Game button, it dims for a second or two then lights up again. It would appear that the launcher doesn't like using IPv6 because I couldn't start the game.Just for completeness as I can't be bothered wasting time investigating this further:
Today I received this from Frontier Support:
"The IPv6 option in the Network settings is not interactable, it is merely for display purposes. So that's actually working as intended.
We have seen many reports of dual stack connections utilizing both IPv6 and IPv4, and sometimes the game gets a bit muddled up with which one to use, that's why my colleague suggested that you disable IPv4, if only as a temporary measure to see if this improves the situation at all. "
Disabling IPv4 in windeys just left me with no internet presumably as the IPv6 on BT doesn't use a DNS server. Sticking IPv4 back enabled gives internet access reported on both IPv4 and IPv6 - nothing makes E D use IPv6 as far as I can see. So I am putting it down to not using a DNS server on IPv6 and I can't be bothered to assign one.
Try the workaround posted by Morbad. I just edited my AppConfigLocal.xml file and now as if by magic, IPv6 is enabled in the game! (Mine is located in Program FIles (x86) - Frontier - EDLaunch - Products - elite-dangerous-64) ETA You don't need to disable IPv4 on the network card in Windows either, you can do that from within the game itself. I played 4 hours and had 1 disconnect. I will test more.Just for completeness as I can't be bothered wasting time investigating this further:
Today I received this from Frontier Support:
"The IPv6 option in the Network settings is not interactable, it is merely for display purposes. So that's actually working as intended.
We have seen many reports of dual stack connections utilizing both IPv6 and IPv4, and sometimes the game gets a bit muddled up with which one to use, that's why my colleague suggested that you disable IPv4, if only as a temporary measure to see if this improves the situation at all. "
Disabling IPv4 in windeys just left me with no internet presumably as the IPv6 on BT doesn't use a DNS server. Sticking IPv4 back enabled gives internet access reported on both IPv4 and IPv6 - nothing makes E D use IPv6 as far as I can see. So I am putting it down to not using a DNS server on IPv6 and I can't be bothered to assign one.
So I am putting it down to not using a DNS server on IPv6 and I can't be bothered to assign one.
..............The complete contents of my file is:
<AppConfig>
<Network
IPv6="1"
VerboseLogging="1">
</Network>
</AppConfig>
.......
You could just paste one of Google's or Cloudflare's public IPv6 DNS servers in to your router settings or Window's TCP/IPv6 properties to see if this is indeed the issue.