Announcement

Collapse
No announcement yet.

The euro day lag

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Ok I did those now, here is what I got:

    tracert.txt
    Code:
    Tracing route to sls-cb9p7.dca2.superb.net [66.36.241.110]
    over a maximum of 30 hops:
      1    23 ms    23 ms    43 ms  10.197.0.1 
      2    79 ms   131 ms    47 ms  62.92.249.105 
      3    17 ms    55 ms    39 ms  ti0048d320-ge0-1-4-10.ti.telenor.net [146.172.108.93] 
      4   164 ms   116 ms   147 ms  ti0001c310-xe7-1-2.ti.telenor.net [146.172.98.1] 
      5   135 ms   232 ms   103 ms  ti3004c310-ae5-0.ti.telenor.net [146.172.100.53] 
      6   206 ms   170 ms   142 ms  ti9004b300-as0-0.ti.telenor.net [146.172.105.98] 
      7     *        *        *     Request timed out.
      8     *        *        *     Request timed out.
      9   120 ms   231 ms   180 ms  sls-cb9p7.dca2.superb.net [66.36.241.110] 
    Trace complete.
    ping.txt
    Code:
    Pinging 66.36.241.110 with 32 bytes of data:
    Reply from 66.36.241.110: bytes=32 time=161ms TTL=120
    Reply from 66.36.241.110: bytes=32 time=174ms TTL=120
    Reply from 66.36.241.110: bytes=32 time=298ms TTL=120
    Reply from 66.36.241.110: bytes=32 time=187ms TTL=120
    Ping statistics for 66.36.241.110:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 161ms, Maximum = 298ms, Average = 205ms
    ping2.txt
    Code:
    Pinging 66.36.224.209 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 66.36.224.209:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    Edit: I forgot my torrents again, but I doubt it matters.
    Da1andonly> man this youghurt only made me angry

    5:ph> n0ah will dangle from a helicopter ladder and just reduce the landscape to ashes by sweeping his beard across it

    Comment


    • #17
      I've tried to use several different proxy servers to see if I could find something that didn't trace through the faulty hopone router, but so far neither me or Turban has managed to find anything good. We can be lucky and find something that changes the trace without adding any significant lag, but there are alot of different proxies to go through.

      If someone knows of a proxy that could work please let us know, maybe we can find a decent solution to this. I'm going to try out more proxies myself, and I'll post any proxy that improves my lag.
      Da1andonly> man this youghurt only made me angry

      5:ph> n0ah will dangle from a helicopter ladder and just reduce the landscape to ashes by sweeping his beard across it

      Comment


      • #18
        So far the only proxy that I've found that helps at least a little (still not playable) is a Socks5 proxy from Russian Federation.

        Open Continuum.exe

        View => Proxy Options => Proxy Settings

        [Enable SOCKS5 Proxy Server]

        HOST: 87.249.9.253
        PORT: 1080

        Worked for me and lowered my PING from 790ms to 250-460ms, but as I said, not playable. Didn't work for Noah though as far as I know. :fear:

        Comment


        • #19
          U need to contact ure internet provider, they can reroute u. The problem is that they wont do anything about it unless they can see it effects multiple people.
          Dont call, send an email with your traceraport and a working traceraport from someone in your region and maybe a link to this thread. It might take a week or 2 but they can help.

          Comment


          • #20
            yall got shitty internetz, i never get hopone or any other bullshit lag. EVER :wub:

            Might and his stoner connection
            Displaced> I get pussy every day
            Displaced> I'm rich
            Displaced> I drive a ferrari lol
            Displaced> ur a faggot with no money
            Thors> prolly
            Thors> but the pussy is HAIRY!

            best comeback ever

            Comment


            • #21
              The chances of your ISP caring about this, or willing to doing something, is about 0. Like Dutch said, if the ISP heard from a large percentage of its customers, it MIGHT be willing to bring pressure on the part of the backbone that is causing the problem. But even in that case, most ISP cannot dictate how traffic gets routed across the internet.
              My opinion is that you guys are wasting your time with this.

              Comment


              • #22
                <votes for an easy, maybe a bit pricey, fix>

                Move.. server.. to.. New York!

                fixed. :wub:

                Comment


                • #23
                  for a comparison, here are my results:

                  TRACERT:
                  Code:
                  Tracing route to sls-cb9p7.dca2.superb.net [66.36.241.110]
                  
                  over a maximum of 30 hops:
                  
                    1     1 ms    <1 ms    <1 ms  192.168.1.1 
                    2     6 ms     5 ms     6 ms  dsl-hkibrasgw2-fed0de00-1.dhcp.inet.fi [80.222.208.1] 
                    3    47 ms    51 ms    47 ms  141.208.151.62 
                    4     6 ms     6 ms     6 ms  hkicore1-e-1-2-0.datanet.tele.fi [141.208.12.97] 
                    5     8 ms    25 ms    23 ms  hkiasbr1-s0-0-0.datanet.tele.fi [141.208.8.10] 
                    6     6 ms     6 ms     6 ms  hls-b2-link.telia.net [213.248.75.17] 
                    7    12 ms    13 ms    13 ms  s-bb1-link.telia.net [80.91.251.33] 
                    8    13 ms    13 ms    12 ms  s-b3-link.telia.net [80.91.249.220] 
                    9    34 ms    34 ms    35 ms  global-ic-120468-s-b1.c.telia.net [213.248.77.214] 
                   10     *        *        *     Request timed out.
                   11     *        *        *     Request timed out.
                   12     *        *        *     Request timed out.
                   13     *        *        *     Request timed out.
                   14   125 ms   125 ms   117 ms  sls-cb9p7.dca2.superb.net [66.36.241.110] 
                  
                  Trace complete.
                  PING
                  Code:
                  Pinging 66.36.241.110 with 32 bytes of data:
                  Request timed out.
                  Request timed out.
                  Request timed out.
                  Request timed out.
                  
                  Ping statistics for 66.36.241.110:
                  
                      Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
                  PING2
                  Code:
                  Pinging 66.36.224.209 with 32 bytes of data:
                  
                  Request timed out.
                  Request timed out.
                  Request timed out.
                  Request timed out.
                  
                  Ping statistics for 66.36.224.209:
                  
                      Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
                  Displaced> I get pussy every day
                  Displaced> I'm rich
                  Displaced> I drive a ferrari lol
                  Displaced> ur a faggot with no money
                  Thors> prolly
                  Thors> but the pussy is HAIRY!

                  best comeback ever

                  Comment


                  • #24
                    I have found myself a temporary solution to fix the HopOne lag; though it's not perfect it will do for now.

                    <trying to find a better alternative, but this one is pretty good and at least playable>

                    STEP 1: Download the free trial (30 days) of ProxyCap and install it. Restart computer.
                    STEP 1.2: Open ProxyCap and make sure your firewall does not block the program.

                    It will look something like this:



                    STEP 2: Go to Ruleset -> Proxies and create a New Proxy Server:
                    STEP 2.1: Make a SOCKS V5 Proxy with 204.188.222.180:23998 (IP:Port)



                    STEP 3: Go to Ruleset -> Rules and create a New Tunnel Rule
                    STEP 3.1: Make sure you set Rule Type as Tunnel through Proxy.
                    STEP 3.2: Make sure your Transports (TCP/UDP) are both checked.
                    STEP 3.3: Make sure your application is specified as Continuum.exe
                    STEP 3.4: If it doesn't work, then just simply Disable the rule.



                    STEP 4: Open up Continuum.exe and have fun playing without the annoying 790ms.

                    Comment


                    • #25
                      Another way (though it doesn't work for all players) is to just simply open Continuum.exe and go to View => Proxy Options and enter this there:

                      [X] ENABLE SOCKS5 PROXY SERVER

                      Host: 204.188.222.180
                      Port: 23998

                      Though suddenly that proxy has given me high ploss. Had a steady 230ms with 0.2 0.1 earlier. Now it's up to 250ms and high plosses.

                      Comment

                      Working...
                      X