Page 6 of 8 FirstFirst ... 45678 LastLast
Results 51 to 60 of 79

Thread: Please fix the servers

  1. #51

    Default

    Some discoveries with respect to kiagsuva's situation...

    The 64.156.194.8 IP that every server traces to would appear to be their central login server farm.

    Once you go beyond that, you will be routed by the name-based routing that gets embedded with the HTTP request in the browser to the appropriate game server IP.

    For example, logging into server 145 gives a connection to m00002-ad.evony.com currently clear over at IP 208.88.18.4.

    Kiagsuva, if you're watching, a trace to that from your side would be good. I go through some interesting hops to get there from where I'm at:

    Tracing route to m00002-ad.evony.com [208.88.18.4]
    over a maximum of 30 hops:

    6 104 ms 152 ms 108 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.4.182]
    7 * * * Request timed out.
    8 113 ms 111 ms 110 ms ge-1-3.r00.sttlwa01.us.ce.gin.ntt.net [198.104.202.114]
    9 113 ms 115 ms 115 ms er6-1-0-25-6.issywa.adtaq.NET [66.228.208.43]
    10 102 ms 102 ms 101 ms m00002-ad.evony.com [208.88.18.4]

    Trace complete.


    Logging into server 150, however, gives a connection to a different subnet. The name there is not listed in DNS, at IP 64.156.195.110.

    Oddly enough, kiagsuva stated that they could log into 150, but not 145. However, in the other thread that was referenced, someone else stated that they can log into 146, but nothing else, and they too are a Primus user.

    Logging into server 146 gives a connection to m00031-lw.evony.com at IP 64.156.195.80.

    In both instances, a trace passes through an additional router that is not present for the 64.156.194.xxx IPs:

    Tracing route to m00031-lw.evony.com [64.156.195.80]
    over a maximum of 30 hops:

    12 85 ms 85 ms 85 ms vl3506.na21.b006590-1.san01.atlas.cogentco.com [66.28.67.70]
    13 89 ms 89 ms 88 ms 38.96.10.250
    14 87 ms 85 ms 86 ms 38.96.14.246
    15 85 ms 87 ms 87 ms m00031-lw.evony.com [64.156.195.80]

    Trace complete.

    It does not make sense that these random IPs would all be getting blocked by a local ISP. It makes a lot more sense to look a lot closer at Evony / colocation equipment, specifically at the devices at / around 38.96.10.250 and 38.96.14.246, and anything else in Evony's LAN or their colocation partner's LAN, to make sure they have their routing tables in proper working order.
    Last edited by neko_lord; 05-02-2011 at 02:20 AM.

  2. #52

    Default

    Quote Originally Posted by neko_lord View Post
    Some discoveries with respect to kiagsuva's situation...

    The 64.156.194.8 IP that every server traces to would appear to be their central login server farm.

    Once you go beyond that, you will be routed by the name-based routing that gets embedded with the HTTP request in the browser to the appropriate game server IP.

    For example, logging into server 145 gives a connection to m00002-ad.evony.com currently clear over at IP 208.88.18.4.

    Kiagsuva, if you're watching, a trace to that from your side would be good. I go through some interesting hops to get there from where I'm at:

    Tracing route to m00002-ad.evony.com [208.88.18.4]
    over a maximum of 30 hops:

    6 104 ms 152 ms 108 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.4.182]
    7 * * * Request timed out.
    8 113 ms 111 ms 110 ms ge-1-3.r00.sttlwa01.us.ce.gin.ntt.net [198.104.202.114]
    9 113 ms 115 ms 115 ms er6-1-0-25-6.issywa.adtaq.NET [66.228.208.43]
    10 102 ms 102 ms 101 ms m00002-ad.evony.com [208.88.18.4]

    Trace complete.


    Logging into server 150, however, gives a connection to a different subnet. The name there is not listed in DNS, at IP 64.156.195.110.

    Oddly enough, kiagsuva stated that they could log into 150, but not 145. However, in the other thread that was referenced, someone else stated that they can log into 146, but nothing else, and they too are a Primus user.

    Logging into server 146 gives a connection to m00031-lw.evony.com at IP 64.156.195.80.

    In both instances, a trace passes through an additional router that is not present for the 64.156.194.xxx IPs:

    Tracing route to m00031-lw.evony.com [64.156.195.80]
    over a maximum of 30 hops:

    12 85 ms 85 ms 85 ms vl3506.na21.b006590-1.san01.atlas.cogentco.com [66.28.67.70]
    13 89 ms 89 ms 88 ms 38.96.10.250
    14 87 ms 85 ms 86 ms 38.96.14.246
    15 85 ms 87 ms 87 ms m00031-lw.evony.com [64.156.195.80]

    Trace complete.

    It does not make sense that these random IPs would all be getting blocked by a local ISP. It makes a lot more sense to look a lot closer at Evony / colocation equipment, specifically at the devices at / around 38.96.10.250 and 38.96.14.246, and anything else in Evony's LAN or their colocation partner's LAN, to make sure they have their routing tables in proper working order.
    Neko Lord;

    Thanks for the information and the effort you are putting into helping out with this. Dave Mata had requested i do a tracert to battle.145.evony.com and battle 150.evony.com. I did get a route to 150 but not to 145. He advised me Friday that he had passed that off to his network guys but I have not heard back from him yet.

    It's funny how posting things on the bbs gets a person way more help than from customer service. I have never heard anything back on my ticket but your efforts and your criticisms, constructive ones by the way, has led to at least some efforts being made to find out what is going on.

    I do hope you feel some vindication for your position that there was something other then clearing caches and customer problems that are the difficulties. Thank you so much.

  3. #53

    Default

    Quote Originally Posted by Kiagsuva View Post
    Neko Lord;

    Thanks for the information and the effort you are putting into helping out with this. Dave Mata had requested i do a tracert to battle.145.evony.com and battle 150.evony.com. I did get a route to 150 but not to 145. He advised me Friday that he had passed that off to his network guys but I have not heard back from him yet.
    Could you please post the trace going to battle145.evony.com? Make sure that you're not putting a period in where none should go. It is battle145.evony.com, not battle.145.evony.com.

    What is very important is where it stops, if it even stops.

    >tracert battle145.evony.com

    Tracing route to battle145.evony.com [208.88.18.104]
    over a maximum of 30 hops:

    6 108 ms 108 ms 113 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.4.182]
    7 * * * Request timed out.
    8 1310 ms 197 ms 507 ms ge-1-3.r00.sttlwa01.us.ce.gin.ntt.net [198.104.202.114]
    9 110 ms 110 ms 111 ms er6-1-0-25-6.issywa.adtaq.NET [66.228.208.43]
    10 107 ms 106 ms 108 ms 208.88.18.104

    Trace complete.

  4. #54

    Default investigating networking issues

    Hello, I'm one of our system administrators.

    First off, thanks for the information everyone has been posting about these problems and thanks to those who responded off-thread to davemata with some other traceroutes.

    Thanks especially to those of you who are helping others.

    As to the problems, I think neko_lord is correct that there are likely problems on our side. We are investigating, but have not yet figured out where they're occuring. The data posted to this thread has helped even if we haven't yet solved the problem.

    I believe there is a completely different problem as well. It looks like Primus is blocking traffic to one of our datacenters, while traffic to the other is being allowed. Traceroutes datamata received off-thread show traffic being blocked at a Primus router. I contacted Primus last week, but had not yet received a response, so I followed up again earlier tonight. I just checked and there is a response from Primus stating that the questions and traceroutes are being forwarded to Primus' networking group.

    Thanks for your patience thus far. We are working on it even if you're not yet seeing resolution.

  5. #55

    Default

    Quote Originally Posted by Amethyst Farmer View Post
    I believe there is a completely different problem as well. It looks like Primus is blocking traffic to one of our datacenters, while traffic to the other is being allowed. Traceroutes datamata received off-thread show traffic being blocked at a Primus router.
    The thing is, did the person type in the trace correctly? No offense intended to them, but I had to correct the attempt that was made by someone (kiagsuva?).

    One other thing is you need to distinguish between tracert and traceroute, the former using ICMP and the latter using TCP. I'm seeing a likely ICMP block on one hop on my way to the 208.88.18.xxx IPs... I'm leaving my provider's hop in this time, so that you know I'm coming in from Cox Communications...

    tracert battle145.evony.com

    Tracing route to battle145.evony.com [208.88.18.104]
    over a maximum of 30 hops:

    5 19 ms 20 ms 20 ms ashbbprj01-ae7.0.rd.as.cox.net [68.1.1.25]
    6 116 ms 105 ms 108 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.4.182]
    7 * * * Request timed out.
    8 361 ms 371 ms 170 ms ge-1-3.r00.sttlwa01.us.ce.gin.ntt.net [198.104.202.114]
    9 114 ms 115 ms 115 ms er6-1-0-25-6.issywa.adtaq.NET [66.228.208.43]
    10 102 ms 102 ms 101 ms 208.88.18.104

    Trace complete.

    I contacted Primus last week, but had not yet received a response, so I followed up again earlier tonight. I just checked and there is a response from Primus stating that the questions and traceroutes are being forwarded to Primus' networking group.
    My suggestion is to double/triple-check the firewall rules for inbound TCP blocks containing Primus IP address ranges on your routers in/around the Seattle datacenter...

  6. #56
    Join Date
    Mar 2010
    Location
    In Evony HQ, glitching the fixes
    Posts
    896

    Default

    Quote Originally Posted by Amethyst Farmer View Post
    Hello, I'm one of our system administrators.

    First off, thanks for the information everyone has been posting about these problems and thanks to those who responded off-thread to davemata with some other traceroutes.

    Thanks especially to those of you who are helping others.

    As to the problems, I think neko_lord is correct that there are likely problems on our side. We are investigating, but have not yet figured out where they're occuring. The data posted to this thread has helped even if we haven't yet solved the problem.

    I believe there is a completely different problem as well. It looks like Primus is blocking traffic to one of our datacenters, while traffic to the other is being allowed. Traceroutes datamata received off-thread show traffic being blocked at a Primus router. I contacted Primus last week, but had not yet received a response, so I followed up again earlier tonight. I just checked and there is a response from Primus stating that the questions and traceroutes are being forwarded to Primus' networking group.

    Thanks for your patience thus far. We are working on it even if you're not yet seeing resolution.
    THANK YOU AMETHYST FARMER

    Other Evony reps, please make note of the very small effort to respond here, that makes ALL the difference to those with issues
    ~
    I don't believe in thinking before I speak
    I prefer to be just as surprised as everyone else by what I say

  7. #57

    Default

    I have to say Neko is the FREAKIN man!!! Moderators should give him a special title or something.. Heck, the Evony staff should give him coins.

    Neko for president!
    -pier117

    *sitting on a porch enjoying the view*

  8. #58

    Default

    Quote Originally Posted by pier117 View Post
    I have to say Neko is the FREAKIN man!!! Moderators should give him a special title or something.. Heck, the Evony staff should give him coins.

    Neko for president!
    Thanks, but no thanks... Just want the issues to get solved and for the solution to be added for things to check for with similar issues in the future, rather than a continual "delete cache and cookies"...

  9. #59

    Default

    Seriously though, Neko is one smart dude. The community owes you man!
    -pier117

    *sitting on a porch enjoying the view*

  10. #60

    Default

    Quote Originally Posted by Amethyst Farmer View Post
    Hello, I'm one of our system administrators.

    First off, thanks for the information everyone has been posting about these problems and thanks to those who responded off-thread to davemata with some other traceroutes.

    Thanks especially to those of you who are helping others.

    As to the problems, I think neko_lord is correct that there are likely problems on our side. We are investigating, but have not yet figured out where they're occuring. The data posted to this thread has helped even if we haven't yet solved the problem.

    I believe there is a completely different problem as well. It looks like Primus is blocking traffic to one of our datacenters, while traffic to the other is being allowed. Traceroutes datamata received off-thread show traffic being blocked at a Primus router. I contacted Primus last week, but had not yet received a response, so I followed up again earlier tonight. I just checked and there is a response from Primus stating that the questions and traceroutes are being forwarded to Primus' networking group.

    Thanks for your patience thus far. We are working on it even if you're not yet seeing resolution.

    i think a nice big wad of coins for neko_lord is in order what a trooper

    <7:10>[ssfgrgawer]: oh i understand using memebers to descout me, Good move. But causing the lag so i cant close gates is a tad unsporting.
    <7:14>[BUBBAA]: powering down the lagatron2000
    <7:16>[ssfgrgawer]: Nope that was all my scouts, i now have a total of 600k.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •