How to enable IPv6 in the game?

Did you create the AppConfigLocal.xml in the directory where EliteDangerous64.exe is ?

My file looks like this :
<?xml version="1.0" encoding="UTF-8" ?>
<AppConfig>
<Network Port="0" IPv6="1" IPv4="0" IPv6Port="0" ReportSentLetters="0" ReportReceivedLetters="0" VerboseLogging="0" />
<Journal Address="0.0.0.0" Port="0" />
</AppConfig>
 
Last edited:
i created it and i realized i needed to change some settings so the game recreates it "correctly"
but in the end, even with IPv6 at 1, the game setting remains grey. I get no connections with either IP protocol, with or without VPN. I guess my next move will be to get a tethering program to avoid using the Android 10 tethering, and hope to get the possibility to open a port.
It s really weird because i use an ISP that is #1 in v6 (more than 10 millions activated dsl/fiber lines), offers deep technical stuff like full range ip, perm ip, reverse, stuff that no one offers, and i m really surprised they block traffic (and even though, it should work with VPN)

so i guess android is to blame. more news tomorrow, if anyone know a solid android tethering program, i m all in
 
Android tethering probably needs more effort (i'm not sure another program will help). And this is probably not an ISP/Elite/IPv6 problem.

I had to do some research to make it work in april (my fiber stopped working for a few days during the lockdown).
I used my phone to connect my work laptop at home, with the virtual machines at my workplace.

Can you use your web browser ?
Are you using wifi or usb to share the phone connection ?
 
Last edited:
I've been watching this thread for a bit. Is there any benefits to using ip6?
I have an excellent connection to the router, throughput is a stable 300mps.
Since the 1st or 2nd FC update the game never pauses anymore, never crashes, stable fps all the time.
Always willing to learn.
 
Newer versions of the game don't seem to be generating, and may not even be parsing, the AppConfigLocal.xml. So, I just started adding IPv6="1" into the Network settings of the main AppConfig.xml, which definitely enables IPv6 in my client.

Is there any benefits to using ip6?

The benefit is greater connectivity to other players. IPv4 address have all been used up for a while and while most ISPs still assign them (usually by sharing a pool of them) this is not always the case and not everyone will be connectable via IPv4. So, occasionally somone who wouldn't be able to peer with your client if you only had IPv4 enabled will be able to do so with IPv6. This is quite rare in Elite: Dangerous as most people still have IP4, which is what the game prefers, and IPv6 may not even be enabled by default, but I have definitely connected to other players via IPv6, on occasion.
 
i created it and i realized i needed to change some settings so the game recreates it "correctly"
but in the end, even with IPv6 at 1, the game setting remains grey. I get no connections with either IP protocol, with or without VPN. I guess my next move will be to get a tethering program to avoid using the Android 10 tethering, and hope to get the possibility to open a port.
It s really weird because i use an ISP that is #1 in v6 (more than 10 millions activated dsl/fiber lines), offers deep technical stuff like full range ip, perm ip, reverse, stuff that no one offers, and i m really surprised they block traffic (and even though, it should work with VPN)

so i guess android is to blame. more news tomorrow, if anyone know a solid android tethering program, i m all in

If you are not seeing the AppConfigLocal.xml - then I would suggest that you were looking in the wrong place. The game makes it's own. It's not in the top level Elite Dangerous folder, rather it is in Products\elite-dangerous-64\ (this may vary if you are using the 32 bit version.

Most of the hotspot apps use IPv4 rather than IPv6 AFAIK (feel free to correct me guys), be it Android/IOS or Windows.
 
goodmorning.
so in random order

-tried USB and Wifi tethering with no luck for elite
-the LTE network definitely delivers IPv6 adress
-if i add ipv options to AppConfig.xml i get "impossible to connect" way before the screen that shows my ship
-from my laptop using tetheting, i can web, skype, even P2P in leecher mode (no opened ports). Tethering is not UPNP compliant (and therefore, i tried to use the option above UPNP in the netwok config screen of the game, with no luck. I guess activating the first one implies to specify a port in the second line)
-concerning why to try ipv6 instead of ipv4 it s to avoid congestion, i am in a very populated area daytime (there is a beach nearby) and many people eat the bandwith for selfies and other fundamentally important online activities when you are on a beach (....)
-at home ipv6 delivers a reliable service with no disconnections, on the other hand, open mode is a bit empty compared to ipv4
-ISP is Free using Proxad network
-I m not using roaming I have a direct mobile operator connection. It should really work.

i d like to try to force a port opened, is there a tethering app that allows this ?

Finally : way to go to force online connection to play solo :(

edit : Almost forgot, trying through steam and through launcher with 2 different accounts : no luck
 
Holy Macaronis it works

So
1) Android 10 with Tethering over WIFI Local
2) a VPN to bypass inbound traffic blocking
3) Allow all traffic type to applications signed by Frontier in firewall
i can get connected and i get the mission board to show missions (solo mode)

The problem was the firewall (a russian one, wont make any advertisement) that considered i was not in a secure environment. So i allowed all traffic on the Frontier Programs and it seemed to have fixed the problem.

On the other hand, it might just be because today it s raining and people didnt come to the beach. who knows.

Being used to work behind a dsl box firewall, i lost the old reflexes of the analog modems era when firewalls on computer had actually a role to play.

note : IPv6 still greyed out in config even though the option is on in AppConfigLocal. Forcing it in AppConfig doesnt change anything. This can come from the VPN or Android itself.
edit : ok it s the VPN that blocks all IPv6 traffic to avoid IPv6 DNS leak
edit : Scarlet Krait after 1 minutes of flight. Bandwith is inexistant here. Take a 10Gbs antenna and put 3000 people on it and admire the miracle of technology. Thanks for the help to all contributors, but it s hopeless.
 
Last edited:
Sky Broadband - BT, there are more in the UK Provide IPv6 (Virgin keep saying soon...... but thats been for years now)
 
Sky Broadband - BT, there are more in the UK Provide IPv6 (Virgin keep saying soon...... but thats been for years now)

BT don't have a DNS for IPv6 they are IPv4 only. You have to set a DNS server manually but the system (including their supplied hub) supports IPv6.
 
Correct. BT do support IPv6 record queries on their DNS, though the DNS servers listen on IPv4. I have BT customer users connecting to servers I manage natively over IPv6 so they are definitely able to resolve AAAA records and connect.

I run a dual stack IPv4/v6 connection (IPv6 provided via SLAAC by my ISP). EDH (Steam edition) does not allow me to enable IPv6 in its options. A shame, because I'd like to use IPv6 where possible.
 
IPv6="1" in your AppConfigLocal.xml...after making sure IPv6 is fully functional elsewhere.
For the record, that enabled IPv6 for me. And contrary to that Frontier support answer somewhere further up this thread the game does work on v6. No idea what they were smoking.

Really looks like the v6 detection code is just borked.
 
There ought to be a benefit to IPv6: Most connections do not have a dedicated IPv4 address anymore (Dual Stack lite, or worse, CGNAT). That means that between peers, a direct IPv4 connection is impossible (no, even port forwarding won't help: You are sharing a router with other customers in front of your home router).

Using TURN (by Frontier) to bridge such connections introduces an additional hop to go through and a potentially unoptimized routing path which means increased latency between both peers. Having a direct connection also avoids instancing issues and in this regard, IPv6 is superior than IPv4 because due to the prefix mechanism which works similar to call forwarding, no port forwarding is needed (unless you limited prefix forwarding in your router or firewall). There are more IPv6 addresses than grains of sand in the Sahara desert.

I myself am one of the fortunate few to still be able to obtain a dedicated IPv4 address.
 
Last edited:
It does not really matter. You have no control where your packets go once they leave your network. It is very likely you will be routed over both Ipv6 and Ipv4 equipment. The ISP will handle the traffic in any way it suits them. Having a IPV6 or IPv4 guarantees nothing. Loads of connections still use Ipv4. So dont consider yourself fortunate.
 
Back
Top Bottom