About the IPv6 issue

[MobiusBE]

Hello

So after the problem with the 'whats new' page and the vaults not showing, I just turned off IPv6 in my adapter settings. This has fixed this issue.

On top of that, I notice now that two other of my problems have also disappeared:

-UPNP now forwards my 6112 port correctly through IPv4 (while it gave an error in the log with IPv6 enabled, giving connection issues to some people sometimes). I attached the log which contains both the failing with IPv6 and the success with IPv4. My router says UPNP is enabled for both IPv4 and IPv6, so I'm not sure why it is only working with IPv4.

-My country flag has reappeared. I have had a '?' flag for months now (since that problem started). But now that I turned off IPv6, I suddenly got my Belgian flag again .

So I was wondering how this is all intertwined? Is there any way to enable IPv6 on my adapter but force FAF to use IPv4 instead?
I'm just looking for a little more insight in what is actually going on .
Thanks!

Kind regards
Mobius

[PhilipJFry]

So far we've assumed that the flag issue is related to incorrect GeoIPData; which might be true to some extent regardless.

Now with the sudden increase in issues we see it seems likely that most of the missing flags and the Vault/What's new bugs are related to FAF not managing IPv6 well while IPv6 slowly starts to replace IPv4.

UPNP may or may not work properly depending on your router. That's an entirely different issue but IPv6 most certainly doesn't make it easier either.

It is intertwined but not all issues we have are caused by it.

[MobiusBE]

That's good to know, thanks . I thought it would be interesting to share what happened after I turned off IPv6. I was very surprised to see my flag and upnp problems suddenly fixed as well .

[PhilipJFry]

IPv6 is basically a protocol that allows you to have enough addresses to (hopefully) never ever run out of them because of the sheer amount that you have

most old software relies on IPv4 because that's what has been around and what it has been coded for and if IPv6 comes around then stuff may not work as intended

for the most part this didn't really matter because public/private IP addresses and routing allowed IPv4 to stay around long past its intended time - Brutus wrote a nice blog post about this here

fortunately for us IPv4 is still supported by basically everything you need (or at least i know of no service that requires you to use IPv6) so while the situation as it is now is far from ideal the workaround most likely won't hurt anyone immediately

[Idontknowman]

I don't know if that's helpful and how related it is as I don't know Python or how Faforever is set up but eventually it's helpful for fixing the issue:

https://pythonadventures.wordpress.com/ ... 4-or-ipv6/

https://stackoverflow.com/questions/197 ... -in-python

http://code.activestate.com/recipes/578 ... -and-ipv6/