📜 ⬆️ ⬇️

EVE Online players are having trouble logging in to the game due to the blocking of RosKomNadzor


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


The 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, links to useful resources and, in fact, the entry form to the game. Without launching the launcher, the game cannot be started.


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



Fortunately for the players, the lanucher contains a self-diagnostic tool with which you can find out the list of ip addresses needed for the launcher.


The result of the self-test

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
54.192.98.158


Host lookups done


Packet exchange with d1hoqe10mv32pv.cloudfront.net [54.192.98.106] with 32 data bytes:
[...]
Packet exchange with d17ueqc3zm9j8o.cloudfront.net [54.192.98.101] with 32 data bytes:
[...]
Packet exchange with dm794883twbxj.cloudfront.net [54.192.98.160] with 32 data bytes:
[...]


The gaming community noticed that some of the addresses (for example, 54.192.98.202) are not available due to entering the roster of unoccupations



The whole absurdity of the situation lies in the fact that, as you can see, the addresses mainly belong to the Amazon Content Delivery Network.


  IP- 54.192.98.235   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 PostalCode: 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 suggests that the blocking is in no way connected with the game itself, but most likely the addresses simply fell under the distribution due to the incorrect setting of the traffic blocking of the provider, since the same CDN address may contain content from different, unrelated CDN clients.


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



According to the players who unsubscribed on the forum, the problem is not local in nature, since manifested in people of different providers.


References:


Branch on the official forum
Vetka on the unofficial Russian-speaking forum
There are many more similar topics on the official forum in the technical section.


UPD:


User KorDen32 explains:


Transtelecom has such a problem, through which many providers go. Copy your message here from another post:

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

At the trunk level, TTK blocks random IPs that are not listed in the registry (it can be seen just because they detect other IPs for blocked domains, and someone trolls / or CDN).
')
As a result, random sites do not open. Of the last major ones that have been noticed - the Uniquiti sites, the service domains of EVE Online, Ingress - though they all sit on the CDN. Recently, a pair of IP Github.com was blocked, with all the consequences - the githab stupidly did not open for several hours, but it was not very massively ...

Not everyone who walks through the TTC blocks, probably depends on the peculiarities of the provider’s interface with the TTC. 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

Source: https://habr.com/ru/post/402893/


All Articles