These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Launcher issue - workaround
Author
Previous Topic Next Topic
Mac Chicovski
Capts Deranged Cavaliers
#1 - 2015-05-29 03:31:01 UTC  |  Edited by: Mac Chicovski
From my reddit post of earlier today.

TL;DR work-around:
If you don't use IPv6, then disable IPv6 on your network adapter. (On Windows 7: Control Panel -> Network and Sharing Center, click the blue 'Local Area Connection' or 'Ethernet' under Access type: Internet, click Properties, scroll down to Internet Protocol Version 6 (TCP/IPv6) and uncheck the box next to it, click OK.)

Summary:
I believe I've root-caused (or at least proximally-caused) the launcher delays that some people have experienced.
This is, the excessive amount of time it takes for the launcher to start up, to draw the login screen and large right pane, to bring up the login yellow box, and then for the updated yellow bar to be fully updated: this can delay starting the client anywhere from 30 seconds to a couple of minutes in my experience.

Steps to reproduce:
When IPv6 is enabled on the LAN adapter on my desktop, and I start the launcher, I see the above delays. Disabling IPv6 on my adapter causes the launcher to start and show ready to launch almost instantly. Re-enabling IPv6 and restarting the launcher has the launcher delay as it did in the first case.
Is this reproducible: yes.

Environmental factors:
In my environment (which is not true for everybody), I have IPv6 setup so that it would work fully when a particular VPN tunnel is enabled. I believe this makes it worse than other people might experience. But, I surmise that if one's DHCP server is returning you some v6 addresses and DNS servers which aren't actually routeable (i.e. your home router supports IPv6 but your service provider doesn't route IPv6), you will see similar issues.

Suggested root causes:

  • Either DNS is attempting to query the IPv6 DNS server for a hostname and timing out, or
  • Having gotten a successful DNS AAA record (IPv6) via regular DNS, the launcher attempts to make an IPv6 connection and times out before trying the IPv4.
SFR SaFeRa
Doomheim
#2 - 2015-05-30 02:51:53 UTC
Mac Chicovski wrote:
From my reddit post of earlier today.

TL;DR work-around:
If you don't use IPv6, then disable IPv6 on your network adapter. (On Windows 7: Control Panel -> Network and Sharing Center, click the blue 'Local Area Connection' or 'Ethernet' under Access type: Internet, click Properties, scroll down to Internet Protocol Version 6 (TCP/IPv6) and uncheck the box next to it, click OK.)

Summary:
I believe I've root-caused (or at least proximally-caused) the launcher delays that some people have experienced.
This is, the excessive amount of time it takes for the launcher to start up, to draw the login screen and large right pane, to bring up the login yellow box, and then for the updated yellow bar to be fully updated: this can delay starting the client anywhere from 30 seconds to a couple of minutes in my experience.

Steps to reproduce:
When IPv6 is enabled on the LAN adapter on my desktop, and I start the launcher, I see the above delays. Disabling IPv6 on my adapter causes the launcher to start and show ready to launch almost instantly. Re-enabling IPv6 and restarting the launcher has the launcher delay as it did in the first case.
Is this reproducible: yes.

Environmental factors:
In my environment (which is not true for everybody), I have IPv6 setup so that it would work fully when a particular VPN tunnel is enabled. I believe this makes it worse than other people might experience. But, I surmise that if one's DHCP server is returning you some v6 addresses and DNS servers which aren't actually routeable (i.e. your home router supports IPv6 but your service provider doesn't route IPv6), you will see similar issues.

Suggested root causes:

  • Either DNS is attempting to query the IPv6 DNS server for a hostname and timing out, or
  • Having gotten a successful DNS AAA record (IPv6) via regular DNS, the launcher attempts to make an IPv6 connection and times out before trying the IPv4.

You just used a lot of big words I don't understand.... gimme a tl;dr: What should I be doing with my Airport Extreme settings, if anything?
Mac Chicovski
Capts Deranged Cavaliers
#3 - 2015-05-30 04:37:46 UTC
SFR SaFeRa wrote:
[quote=Mac Chicovski]
You just used a lot of big words I don't understand.... gimme a tl;dr: What should I be doing with my Airport Extreme settings, if anything?


Nothing on your Airport Extreme. Disable IPv6 on the computer you run Eve on.

If that doesn't mean anything to you, try googling "disable ipv6 [your OS and version]", for instance "disable ipv6 windows 8", or "disable ipv6 mac osx".
SFR SaFeRa
Doomheim
#4 - 2015-05-30 10:24:47 UTC  |  Edited by: SFR SaFeRa
Mac Chicovski wrote:
SFR SaFeRa wrote:
[quote=Mac Chicovski]
You just used a lot of big words I don't understand.... gimme a tl;dr: What should I be doing with my Airport Extreme settings, if anything?


Nothing on your Airport Extreme. Disable IPv6 on the computer you run Eve on.

If that doesn't mean anything to you, try googling "disable ipv6 [your OS and version]", for instance "disable ipv6 windows 8", or "disable ipv6 mac osx".

I disabled it. Whether that will help, I don't know. Disabling it did require a bit of messing about in terminal, something I am much more familiar with than I am with the network :). The off setting does not appear by default in Settings > Network > Advanced > TCP/IP. You will this need to use either or both of these terminal commands, as written exactly. (All info for OSX Mavericks!) '-setv6off wi-fi' '-setv6off ethernet' . Thanks, hope this helps all the other poor mac users!


EDIT: Worked like a charm, launcher is functioning beautifully! +1 on this great solution! Calling all debs to please provide a fix based on this, thanks!



(not that I know if it worked yet.....)