FEATURED

EVE Online players are having problems entering the game due to the blocking of RosKomNadzor

About two weeks some EVE Online players are forced to watch the error message instead of the usual game login window

EVE Online game client, like many modern online games, works in such a way that before launching the main client program, the launcher mini-program is first launched.

On its main screen, the launcher contains the latest news, information about the status of servers, Shortcuts to useful resources and, in fact, the login form in the game.

Recently, some players (including me) have stopped working in normal mode, sometimes giving out a message as on KDPV, sometimes showing more informative messages

Fortunately for the players, the launcher contains a self-diagnostic tool that can help you find out the list of ip addresses needed for the launcher's work.

The result of the self-diagnostics work

Starting basic diagnostics

Looking up hosts:
launcher.eveonline.com
Binaries.eveonline.com
Resources.eveonline.com

Host lookup for launcher.eveonline.com returned:
54.192.98.106
54.192.98.111
54.192.98.152
54.192.98.202
54.192.98.224
54.192.98.25
54.192.98.56
54.192.98.65

Host lookup for binaries.eveonline.com returned:
54.192.98.101
54.192.98.124
54.192.98.219
54.192.98.234
54.192.98.252
54.192.98.37
54.192.98.43
54.192.98.87

Host lookup for resources.eveonline.com returned:
54.192.98.160
54.192.98.188
54.192.98.225
54.192.98.20
54.192.98.33
54.192.98.54
54.192.98.126

Host lookups done

Exchange of packages with d1hoqe10mv32pv.cloudfront.net [54.192.98.106] with 32 bytes of data:
[…]
Exchange of packages with d17ueqc3zm9j8o.cloudfront.net [54.192.98.101] with 32 bytes of data:
[…]
Exchange packages with dm794883twbxj.cloudfront.net [54.192.98.160] with 32 bytes of data:

The game community noticed that some of the addresses (for example, 54.192.98.202) are unavailable due to the entry in the registry of the ILV

The absurdity of the situation is that, as you can see, the addresses are mostly owned by the Amazon Content Delivery Network.

  Information about the IP-address 54.192.98.235
According to ARIN:

NetRange: 54.192.0.0 - 54.207.255.255
CIDR: 54.192.0.0/12
NetName: AMAZON-2011L
Organization: Amazon Technologies Inc. (AT-88-Z)
RegDate: 2013-06-19
Updated: 2013-06-19
Ref: https://whois.arin.net/rest/net/NET-54-192-0-0-1

OrgName: Amazon Technologies Inc
OrgId: AT-88-Z
Address: 410 Terry Ave N.
City: Seattle
StateProv: WA
Postal code: 98109
Country: US
RegDate: 2011-12-08
Updated: 2017-01-28

OrgTechName: Amazon EC2 Network Operations
OrgTechPhone: + 1-206-266-4064
OrgTechEmail: amzn-noc-contact@amazon.com
OrgTechRef: https://whois.arin.net/rest/poc/ANO24-ARIN

OrgNOCName: Amazon AWS Network Operations
OrgNOCPhone: + 1-206-266-4064
OrgNOCEmail: amzn-noc-contact@amazon.com
OrgNOCRef: https://whois.arin.net/rest/poc/AANO1-ARIN

This leads to the idea that the lock is not connected with the game itself, but most likely the addresses just got under the distribution Due to incorrect configuration of traffic locks from the provider, because On the same CDN address can contain content from different, unrelated CDN clients.

Currently, players are forced to solve the problem on their own:

  • Restart Client until the desired launcher domains are decoded into unlocked ip addresses
  • register in the local hosts for the still working ip addresses

According to the players who have unsubscribed at the forum, the problem is not of a local nature, because Manifested in people of different providers.

Links:

→ Branch on the official forum
→ The branch at the informal Russian-language forum
→ Many more similar topics on the official forum in the technical section

UPD:

KorDen32 user explains:

There is such a problem for Transtelecom, through which many providers go. I copy here my message from another post:

Alas, in February-March this is exactly what happens at the TTK mainline
It is easy to google a bunch of disparate topics on "filter-gw.transtelecom.net" (or "blacklist-gw.transtelecom.net").

The TTK on the main level blocks random IP addresses not listed in the registry , That other IPs are detected for blocked domains, and someone trolls / or CDN).

As a result, random sites are not opened. Of the last large ones that were noticed – Uniquiti sites, EVE Online service domains, Ingress – though they all sit on the CDN. Recently, the IP Github.com couple was blocked, with all the ensuing – the githab stupidly did not open for several hours, but it was not very mass …

It does not blob for everyone who walks through the TTK, apparently depends on the specifics of the provider's interface with TTK. Make a trace to the address of interest. If there is a hop filter-gw.transtelecom.net, blacklist-gw.transtelecom.net, or bl-gw.transtelecom.net – this is it

About the author

admin

Add Comment

Click here to post a comment

Your email address will not be published. Required fields are marked *