Jump to content

Roy

Banned
  • Posts

    2,853
  • Joined

  • Last visited

  • Days Won

    383

Posts posted by Roy

  1. Just a heads up, every PoP server besides Dallas is offline at the moment (the BIRD daemon isn't running). We are trying to fix the route from our physical machine to the Dallas PoP and experiencing issues. Once we fix this, we'll put all the rest of the PoPs back up.

     

    This means every trace route performed will route to the Dallas PoP regardless of location, etc.

     

    Thank you.

  2. The machine appears to be online again:

     

    C:\Users\Christian Deacon>ping 185.177.22.161
    
    Pinging 185.177.22.161 with 32 bytes of data:
    Reply from 185.177.22.161: bytes=32 time=130ms TTL=43
    Reply from 185.177.22.161: bytes=32 time=222ms TTL=43
    Reply from 185.177.22.161: bytes=32 time=130ms TTL=43
    Reply from 185.177.22.161: bytes=32 time=242ms TTL=43
    
    Ping statistics for 185.177.22.161:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 130ms, Maximum = 242ms, Average = 181ms

     

    I have restarted the game servers on the machine and requested a reason for outage from our hosting provider.

     

    Thank you.

  3. Hello,

     

    Currently, our GS05 machine located in London, UK is currently down. As of right now, we have no information on why it's down, but our hosting provider is investigating.

     

    All we know is this:

     

    [ChristianDeacon.DESKTOP] ➤ ping gs05.gflclan.com
    
    Pinging gs05.gflclan.com [185.177.22.161] with 32 bytes of data:
    Reply from 185.177.22.161: Destination host unreachable.
    Reply from 185.177.22.161: Destination host unreachable.
    Reply from 185.177.22.161: Destination host unreachable.
    Reply from 185.177.22.161: Destination host unreachable.
    
    Ping statistics for 185.177.22.161:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    

     

    I will reply back here once I have an update.

     

    I apologize for the inconvenience and thank you for understanding.

  4. 1 hour ago, King_Wailord said:

    Location: Zionsville, Indiana

     

    Traceroute:

     

    Tracing route to 92.119.148.5 over a maximum of 30 hops

      1     3 ms     2 ms     4 ms  testwifi.here [192.168.86.1]
      2     3 ms     2 ms     4 ms  192.168.0.1
      3     9 ms     6 ms     8 ms  cytninhed11-dy1001-secondary4.network.tds.net [96.60.208.1]
      4     9 ms    10 ms    10 ms  cytnindst52-tg0-7-0-0.network.tds.net [64.50.231.113]
      5    31 ms    30 ms    32 ms  h64-50-224-143.mdsnwi.tisp.static.tds.net [64.50.224.143]
      6    35 ms    30 ms    31 ms  nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]
      7    29 ms    30 ms    34 ms  vl42-br2.pnj1.choopa.net [108.61.2.89]
      8     *        *        *     Request timed out.
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17     *        *        *     Request timed out.
     18     *        *        *     Request timed out.
     19     *        *        *     Request timed out.
     20     *        *        *     Request timed out.
     21     *        *        *     Request timed out.
     22     *        *        *     Request timed out.
     23     *        *        *     Request timed out.
     24     *        *        *     Request timed out.
     25     *        *        *     Request timed out.
     26     *        *        *     Request timed out.
     27     *        *        *     Request timed out.
     28     *        *        *     Request timed out.
     29     *        *        *     Request timed out.
     30     *        *        *     Request timed out.

    Trace complete.

    You'd probably be better off being routed to the Chicago PoP. I can look into this later.

     

    Thanks.

  5. 5 minutes ago, RainGamma said:

    I have one gig ethernet.

    I hate to break it to ya, but we don't even have a PoP in Virginia and I'm not sure how you're even getting a reply from the Anycast IP itself.

     

    I think your ISP is doing something fucky, lol. I'm just not sure what. Still though, 9ms is pretty good ;)  You're probably getting routed to the NYC PoP.

     

    Thanks.

  6. 8 minutes ago, RainGamma said:

    Location - Sterling, VA

     

    Trace Route -  


    Tracing route to 92.119.148.5 over a maximum of 30 hops

      1    <1 ms    <1 ms    <1 ms  192.168.1.1
      2     9 ms    11 ms     7 ms  92.119.148.5

    Trace complete.

    That is the best trace route I've seen lmao.

     

    I honestly don't even know how you got a reply from the IP itself, lol.

     

    Thanks.

  7. 28 minutes ago, SwegBuster said:

    I do actually get routed to Seattle before going to LA. The others are closer to my state so.

     

    Thanks.

    Yes, but it routes you from a hop in Seattle all the way to the PoP we have in Los Angeles (this would just add latency since you're being routed to Seattle and back to Los Angeles) instead of just going to the PoP we have in Seattle. This is most likely due to the route to Los Angeles having less hops than the route to the Seattle PoP (Anycast picks the closest PoP based off of the amount of hops it takes to get to each PoP I believe). This leads to a routing issue. I may PM you asking if you can perform a trace route to our Seattle PoP server so I can see what route you're taking to there and then make optimizations where necessary.

     

    I will admit though, if our physical server is in Dallas, you're better off being routed to the Los Angeles PoP. However, the Seattle PoP is still technically closer. Therefore, there is still optimizing we have to perform with the routing.

     

    I've noticed our Seattle and Dallas PoPs having the least amount of traffic and these are the two PoPs we have the most routing issues with. Once I get more experience with BIRD/BGP configuration, myself or  @Dreae (he is definitely more experienced with this) should be able to correct this.

     

    I am trying to find out how advanced/specific the BIRD configuration can go. It'd be really cool if we could optimize certain routes based off of the destination IP. For example, the IPs that get forwarded to the physical server in Dallas, it'd be better to prefer you to the Los Angeles PoP but if a physical server is in Chicago, you'd be better off getting routed to the Seattle PoP. I'm not sure if this is even possible, though.

     

    Thanks!

  8. 1 hour ago, Fafy said:

    Location: Argentina, Buenos Aires (Province), La Plata (City)

    
    C:\Users\usuario>tracert 92.119.148.5
    
    Traza a 92.119.148.5 sobre caminos de 30 saltos como máximo.
    
      1    <1 ms    <1 ms    <1 ms  192.168.1.1 [192.168.1.1]
      2     3 ms     2 ms     2 ms  10.100.100.1 [10.100.100.1]
      3     3 ms     3 ms     2 ms  143.208.36.241
      4     5 ms     4 ms     4 ms  static1.100.12.190.cps.com.ar [190.12.100.1]
      5     4 ms     4 ms     4 ms  static.40.192.104.190.cps.com.ar [190.104.192.40
    ]
      6     5 ms     4 ms     4 ms  195.22.220.113
      7    34 ms    33 ms    31 ms  et11-1-0.sanpaolo8.spa.seabone.net [195.22.219.1
    45]
      8   141 ms   141 ms   142 ms  ntt-verio.sanpaolo8.spa.seabone.net [149.3.181.6
    5]
      9   141 ms   140 ms   141 ms  ae-8.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.1
    2]
     10   141 ms   141 ms   140 ms  ae-1.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.1
    81]
     11   141 ms   141 ms   140 ms  ae-0.a02.nycmny01.us.bb.gin.ntt.net [129.250.6.5
    1]
     12   150 ms   141 ms   173 ms  ae-1.choopa.nycmny01.us.bb.gin.ntt.net [128.241.
    2.250]
     13   141 ms   142 ms   141 ms  vl42-br2.pnj1.choopa.net [108.61.2.89]
     14     *        *        *     Tiempo de espera agotado para esta solicitud.
     15     *        *        *     Tiempo de espera agotado para esta solicitud.
     16     *        *        *     Tiempo de espera agotado para esta solicitud.
     17     *        *        *     Tiempo de espera agotado para esta solicitud.
     18     *        *        *     Tiempo de espera agotado para esta solicitud.
     19     *        *        *     Tiempo de espera agotado para esta solicitud.
     20     *        *        *     Tiempo de espera agotado para esta solicitud.
     21     *        *        *     Tiempo de espera agotado para esta solicitud.
     22     *        *        *     Tiempo de espera agotado para esta solicitud.
     23     *        *        *     Tiempo de espera agotado para esta solicitud.
     24     *        *        *     Tiempo de espera agotado para esta solicitud.
     25     *        *        *     Tiempo de espera agotado para esta solicitud.
     26     *        *        *     Tiempo de espera agotado para esta solicitud.
     27     *        *        *     Tiempo de espera agotado para esta solicitud.
     28     *        *        *     Tiempo de espera agotado para esta solicitud.
     29     *        *        *     Tiempo de espera agotado para esta solicitud.
     30     *        *        *     Tiempo de espera agotado para esta solicitud.
    
    Traza completa.

     

    Interesting. I plan to at some point get PoPs in South America. But for some reason you're being routed to the NYC PoP instead of something like Miami (preferred based on your location) or Dallas.

     

    If you can, would you be able to PM me your public IPv4 address? I'd like to investigate this further. I may ask to do trace routes to specific PoPs themselves if that's okay.

     

    Thank you.

  9. 6 minutes ago, Liloz01 said:

    @Roy 

    First - A college computer

    Second - My laptop running off of my mobile hotspot (I've played games like this before, don't judge)

    The first trace route being a college computer makes sense. I think your college may be blocking that IP since it doesn't even leave the internal network, lol.

     

    The high latency on the second trace route now makes sense since you're using a mobile hot spot haha.

     

    Thanks!

  10. 22 minutes ago, Liloz01 said:

    A bit late, don't care :lenny:

     

    Location - Various devices with different connections in various locations in Nottingham, England.

     

    Trace Route -

      Reveal hidden contents

     

      Reveal hidden contents

     

      Reveal hidden contents

    What devices/networks are being used in the first two trace routes? The first one doesn't even leave the internal network and the second one has ~70ms on just the second hop.

     

    The third one looks pretty good though :) 

     

    Thanks!

  11. I just wanted to say thanks again for the results! In the future, we are most likely going to spin up a PoP server in Atlanta, US for players closer to there. However, other than that, things are looking great! We will need to make some routing changes for our physical server's hosting provider, though.

     

    GFL having its own network is very exciting and I really haven't seen any other standard gaming community do that yet.

     

    As stated in the original post, I will be making a more detailed announcement listing what this exactly does and how it benefits GFL once the network is completely rolled out.

     

    Thank you!

  12. 16 minutes ago, Remuchu said:

    Route to Dallas from Louisiana is down I believe, cant trace it and other locals cant connect at the moment

    The timeouts at the end are normal since there isn't anything replying to the request via ICMP. The last hop that sends a reply is usually where you end up at. Most of the results route to Chicago. @Ben and I route to Dallas.

     

    EDIT

    @nblockbuster routes to the NYC PoP.

     

    Thanks.

  13. 2 minutes ago, Ben said:

    Location - Pickens, S.C., US

     

    Tracert - 

    
    Tracing route to 92.119.148.55 over a maximum of 30 hops
    
      1     6 ms     9 ms     9 ms  192.168.0.1
      2     *        *        *     Request timed out.
      3    29 ms    29 ms    29 ms  10.2.1.21
      4    27 ms    19 ms    19 ms  4.34.18.21
      5     *       39 ms     *     ae-1-51.ear3.atlanta2.level3.net [4.69.150.225]
      6    33 ms     *        *     atl-b22-link.telia.net [213.248.84.34]
      7    39 ms    31 ms    37 ms  atl-b22-link.telia.net [62.115.113.24]
      8    71 ms    57 ms    49 ms  dls-b22-link.telia.net [62.115.120.113]
      9    58 ms    59 ms    49 ms  vultr-ic-318447-dls-b22.c.telia.net [62.115.149.45]
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17     *        *        *     Request timed out.
     18     *        *        *     Request timed out.
     19     *        *        *     Request timed out.
     20     *        *        *     Request timed out.
     21     *        *        *     Request timed out.
     22     *        *        *     Request timed out.
     23     *        *        *     Request timed out.
     24     *        *        *     Request timed out.
     25     *        *        *     Request timed out.
     26     *        *        *     Request timed out.
     27     *        *        *     Request timed out.
     28     *        *        *     Request timed out.
     29     *        *        *     Request timed out.
     30     *        *        *     Request timed out.
    
    Trace complete.
    

     

    Looks like you're getting routed to the Dallas PoP. I'm wondering if you'd be better off getting routed to the NYC PoP. I guess it depends on where the physical server is hosted (if it's overseas, NYC is better, if it's in Dallas, TX, that PoP would obviously be better).

     

    Thank you for the results so far everyone! I'm liking the routes and no concerns as of right now:) 

     

    Thanks!

  14. Fixed

    • Performance issues when attempting to post. Sometimes it'd take up to a minute to post a thread depending on the size.

     

    The cause was due to Google's DNS server being somehow blocked by our firewall. We were using Google DNS beforehand on our machines. My guess is when making a post, the server made some DNS look-ups, but since the DNS server was blocked, it was timing out. This not only caused issues on our main website, but also with other services that ran on our web machine.

     

    Since then I've white-listed the Google DNS server on our firewall and I don't expect to run into this issue again.

     

    Thanks.

  15. On 2/25/2019 at 4:51 PM, Bara said:

    Just my opinion:

     

    Is a older non-overclockable 3.50ghz/3,90ghz(boost) cpu with 6 cores (12 threads with hyper threading). It doesn't make sense (for me) to switch to this kind of server, because the 4790k has more single core performance with less cores/threads.

    If we were to purchase this machine, we wouldn't be putting our higher-slot servers on it. Instead, it'd be primarily used to host our mid-range game servers and even out the load on our current machine in Dallas (we would not get rid of the Dallas machine with GMCHosting).

     

    We still plan to purchase the Intel i7-9700K once it becomes available. However, at this point, it's sounding like it won't be available for a while.

     

    Thanks.

×
×
  • Create New...