LAG issue - HowTo solve it

voobscout · Post by **voobscout** » Tue Apr 28, 2009 5:33 pm

sgt_baker wrote:QUOTE (sgt_baker @ Apr 28 2009, 06:57 PM) I'm pretty certain that this isn't native IPv6. All packets are being routed via 6to4.ipv6.microsoft.com [192.88.99.1]. We sure that Windoze hasn't been instructed in a recent update to set up said tunnel by default?

^^At least that's what the firewall packet logger is telling me. Initial tests on the IPv4 end seems to suggest that that server is indeed in London somewhere, yet the MS domain etc???

microsoft could be involved in some weird peering, especially when it comes to ipv6.... it could also be that your ISP is participating in some joint activity.... what i can assure you, completely and truthfully, is that unless your ISP isn't giving you dstm dhcpv6, you wouldn't ever get an ipv6 address, not a chance... none at all, trust me on this one, if i'm wrong i should go and hang myself by my balls quietely on some pole in stepney....

Now, i want everybody to start testing their ipv6 connectivity, especially AU pilots, i want to hear some feedback and i want server admins to at least try this whole issue once ! Lag is the thing of the past !

sgt_baker · Post by **sgt_baker** » Tue Apr 28, 2009 5:34 pm

The bad news. I just performed a trace comparing IPv6 vis HE and IPv4 via normal internet. It is worth noting that I'm only able to trace as far as HE's Dallas router on the IPv6 end of things. Packets destined for the planet servers would be required to traverse the IPv4 infrastructure between HE's Dallas router and the actual planet server in addition to the IPv6 results listed below.

The tests

Trace IPv6 to HE's Dallas router:

Code: Select all

Tracing route to 10gigabitethernet1-2.core1.dal1.he.net [2001:470:0:3a::2]
from 2001:470:1f08:d0f::2 over a maximum of 30 hops:

  1       30 ms    22 ms    21 ms  sgtbaker-1.tunnel.tserv5.lon1.ipv6.he.net [2001:470:1f08:d0f::1]
  2       70 ms    21 ms    21 ms  gige-g4-6.core1.lon1.he.net [2001:470:0:67::1]
  3       89 ms    91 ms   122 ms  10gigabitethernet2-3.core1.nyc4.he.net [2001:470:0:3e::1]
  4      103 ms   105 ms   103 ms  10gigabitethernet2-3.core1.ash1.he.net [2001:470:0:36::1]
  5      138 ms   131 ms     *     10gigabitethernet1-2.core1.dal1.he.net [2001:470:0:3a::2]
  6      131 ms   130 ms   132 ms  10gigabitethernet1-2.core1.dal1.he.net [2001:470:0:3a::2]

Ping IPv6 to HE's Dallas router:

Code: Select all

Pinging 2001:470:0:3a::2
from 2001:470:1f08:d0f::2 with 32 bytes of data:

Reply from 2001:470:0:3a::2: bytes=32 time=145ms
Reply from 2001:470:0:3a::2: bytes=32 time=131ms
Reply from 2001:470:0:3a::2: bytes=32 time=134ms
<snip>
Reply from 2001:470:0:3a::2: bytes=32 time=132ms

Ping statistics for 2001:470:0:3a::2:
    Packets: Sent = 51, Received = 49, Lost = 2 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 129ms, Maximum = 159ms, Average = 135ms

And now for a IPv4 trace/ping direct to planet.dras.us:

Code: Select all

Tracing route to planet.dras.us [70.86.91.82]
over a maximum of 30 hops:

  1    20 ms     7 ms     7 ms  10.14.252.1
  2     9 ms     7 ms     7 ms  popl-t3core-1a-ge-500-665.network.virginmedia.net [62.255.161.37]
  3     9 ms    19 ms    25 ms  pop-bb-a-as2-0.network.virginmedia.net [213.105.174.234]
  4     8 ms     7 ms     7 ms  pop-bb-b-ae0-0.network.virginmedia.net [213.105.174.230]
  5     9 ms    26 ms     8 ms  tele-ic-2-as0-0.network.virginmedia.net [62.253.184.6]
  6     *        *        *     Request timed out.
  7   134 ms   128 ms   126 ms  bd.fd.5746.static.theplanet.com [70.87.253.189]
  8   128 ms   127 ms   137 ms  te7-1.dsr01.dllstx3.theplanet.com [70.87.253.2]
  9   128 ms   126 ms   127 ms  po31.dsr01.dllstx5.theplanet.com [70.85.127.106]
 10   129 ms   127 ms   128 ms  po1.car04.dllstx5.theplanet.com [70.87.254.26]
 11   128 ms   127 ms   126 ms  planet.dras.us [70.86.91.82]

And the pings:

Code: Select all

Pinging planet.dras.us [70.86.91.82] with 32 bytes of data:

Reply from 70.86.91.82: bytes=32 time=134ms TTL=119
Reply from 70.86.91.82: bytes=32 time=127ms TTL=119
<snip>
Reply from 70.86.91.82: bytes=32 time=127ms TTL=119
Reply from 70.86.91.82: bytes=32 time=125ms TTL=119

Ping statistics for 70.86.91.82:
    Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 125ms, Maximum = 149ms, Average = 128ms

The results

IPv6 Average Ping: 135ms (EXCLUDING latency between HE's router and actual game server)
IPv4 Average Ping: 128ms (INCLUDING getting all the way to the game server)

IPv6 Packet Loss: 3%
IPv4 Packet Loss: 0%

Conclusion

For me, it's better to stick with IPv4 for connecting to alleg servers for now. The experience may differ for other users, particularly when you're experiencing funky routing between you and the game servers which may be alleviated by using a smaller network such as HE's. By all means, go to HE's Network Map and try to find out whether IPv6 will work better for you. My case is probably fortunate since planet have recently decided to peer directly with London. Your milage may vary.

B

sgt_baker · Post by **sgt_baker** » Tue Apr 28, 2009 5:36 pm

voobscout wrote:QUOTE (voobscout @ Apr 28 2009, 06:33 PM) microsoft could be involved in some weird peering, especially when it comes to ipv6.... it could also be that your ISP is participating in some joint activity.... what i can assure you, completely and truthfully, is that unless your ISP isn't giving you dstm dhcpv6, you wouldn't ever get an ipv6 address, not a chance... none at all, trust me on this one, if i'm wrong i should go and hang myself by my balls quietely on some pole in stepney....

LOL

badpazzword · Post by **badpazzword** » Tue Apr 28, 2009 5:36 pm

Quick IPv6 connectivity test: http://www.ipv6porn.co.nz/

voobscout · Post by **voobscout** » Tue Apr 28, 2009 5:59 pm

sgt_baker wrote:QUOTE (sgt_baker @ Apr 28 2009, 07:34 PM) For me, it's better to stick with IPv4 for connecting to alleg servers for now. The experience may differ for other users, particularly when you're experiencing funky routing between you and the game servers which may be alleviated by using a smaller network such as HE's. By all means, go to HE's Network Map and try to find out whether IPv6 will work better for you. My case is probably fortunate since planet have recently decided to peer directly with London. Your milage may vary.

B

That's the whole point, some people are better off not going ipv6, others might benefit a lot, otherwise, if ipv6 would have been awesome for absolutely everybody without exception, i'm sure there wouldn't even be an option to connect with ipv4. And i'm talking only about alleg.

As to the fact of where should servers be connected, we simply have to test, it might very well be, that a planet server in dallas would have better ipv4 connectivity to NY or fremont, rather then locally in dallas. Physical distances play extremely small role in network peering.

Besides HE, there're more ipv6 tunnel brokers, everybody's results will invariably vary ! That's why i created a survey form in a first place and that's why i'm crying for people to test with different brokers.

Now, the real test would be to actually have a machine in the same subnet as planet/gpz servers to have ipv6 connectivity to it's closest (network wise, not geographically) ipv6 POP. For this we don't need to touch anything on running servers, we'll simply be able to traceroute/ping to a box in the same network and everyone would be able to figure out the results for themselves.

out of curiousity, if Baker wants to, he can perform same tests with other tunnel brokers, listed in my first post...

sgt_baker · Post by **sgt_baker** » Tue Apr 28, 2009 6:02 pm

voobscout wrote:QUOTE (voobscout @ Apr 28 2009, 06:59 PM) out of curiousity, if Baker wants to, he can perform same tests with other tunnel brokers, listed in my first post...

Will do. It's 7pm, though. Time to stop saying "wtf hex... wtf double colon... wtf OOOH. Right. wtf firewall... wtf ipv6". You get the picture.

sgt_baker · Post by **sgt_baker** » Tue Apr 28, 2009 6:51 pm

C'mon people. I did it. You can too!

Jeruwafi · Post by **Jeruwafi** » Tue Apr 28, 2009 6:58 pm

I demand some action from planet admins! :]

EDIT:
I think that HE instructions for XP are easier and shorter, is there any advantage of using netsh?

sgt_baker · Post by **sgt_baker** » Tue Apr 28, 2009 7:01 pm

Jeruwafi wrote:QUOTE (Jeruwafi @ Apr 28 2009, 07:58 PM) I demand some action from planet admins! :]

I demand some action from planet admins where TAG is concerned ! :]

(what's the point in having a stats collection system etc etc etc blah baker goes off on one again blah blah)

Jeruwafi · Post by **Jeruwafi** » Tue Apr 28, 2009 7:06 pm

I demand some motivational posters for planet admins ! :]

Does anyone know what is meant by sixxs' "Note that a static tunnel requires it to be available
24/7 and if you fail to do that credits will be taken from your account." ? Wtf credits? Currency-v6?

I dont feel like installing anything and static tunnel would be fine for me, but I'm not going to have it 24/7... nearest sixxs pop is a few ms closer than HE