Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 
194 posts

Master Geek

Trusted

  Reply # 206908 14-Apr-2009 17:39
Send private message

Ragnor: Do a tracert to your wow server and compare it to a tracert to a few of the wowtunnels ssh servers (eg:  tunnel5.wowtunnels.com and tunnel2.wowtunnels.com) and compare the route taken see if you bypass the problematic AT&T router.

Ragnor that page is badly in need of an update.

I found a thread where people were posting their traceroutes to their realm IP's

They found it by running a netstat command and picking the IP adress which had ":3724" at the end (going through port 3724 ?)

Every traceroute I found listed a different IP to the one listed on that wow wiki page.




==================================
- Hone , Often accused of Excess Verbosity
==================================

194 posts

Master Geek

Trusted

  Reply # 206910 14-Apr-2009 17:48
Send private message

Baboon: Server: Feathermoon 12.129.233.96
Location: New Zealand

*snipped*

12  mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246)  146.851 ms  147.421 ms  145.941 ms

1) Are you sure that's your realm IP ? 

You can find it out by logging into game then alt tabbing and running a netstat command

Your realm IP will be the one with ":3724" at the end

2) I don't see a problem with that traceroute. Although out of date that wow wiki page did say the last hop is meant to be either 

12.129.193.246 or 12.129.193.242

3) Many companies will block traceroute requests for security reasons.

You'd be better off taking a traceroute when you have your normal latency

Save this to a file

Then wait until you get really really bad latency tonight. Then run another few traceroutes and compare them.





==================================
- Hone , Often accused of Excess Verbosity
==================================

 
 
 
 


8027 posts

Uber Geek
+1 received by user: 387

Trusted
Subscriber

  Reply # 206926 14-Apr-2009 18:56
Send private message

honem:

Ragnor that page is badly in need of an update.



Used to be up to date guess no one is updating it anymore or blizzard are changing their ip addresses more frequently.



I found a thread where people were posting their traceroutes to their realm IP's

They found it by running a netstat command and picking the IP adress which had ":3724" at the end (going through port 3724 ?)



Yes that's the port wow uses and how those ip address lists were made in the first place.

The LAX >> AT&T hops have had numerous problems over the years which is why many people use ssh tunnels that have LA endpoints that bypass those particular hops.  I'm suprised there are people who don't know about using wowtunnels a heck of a lot of oceanic guilds use wowtunnels, lowerping or similar setups.




41 posts

Geek


  Reply # 206927 14-Apr-2009 19:11
Send private message

Wait, so using SSH/WoWtunnels fixes all of those kinds of issues?


I doubt it, but thats the impression you give me.

230 posts

Master Geek
+1 received by user: 4


  Reply # 206943 14-Apr-2009 20:42
Send private message

Ragnor:
honem:

Ragnor that page is badly in need of an update.



Used to be up to date guess no one is updating it anymore or blizzard are changing their ip addresses more frequently.



I found a thread where people were posting their traceroutes to their realm IP's

They found it by running a netstat command and picking the IP adress which had ":3724" at the end (going through port 3724 ?)



Yes that's the port wow uses and how those ip address lists were made in the first place.

The LAX >> AT&T hops have had numerous problems over the years which is why many people use ssh tunnels that have LA endpoints that bypass those particular hops.  I'm suprised there are people who don't know about using wowtunnels a heck of a lot of oceanic guilds use wowtunnels, lowerping or similar setups.



I can locate no IP using that port. I'm not sure why that is - I'm on OSX using netstat within Network Utility.app




"The surest sign that intelligent life exists elsewhere in the universe is that it has never tried to contact us."

 

- Calvin and Hobbes (Bill Watterson)

230 posts

Master Geek
+1 received by user: 4


Reply # 206950 14-Apr-2009 21:20
Send private message

Ok, turns out netstat within Network Utility.app names some ports. Not helpful. The IP I've found is 12.129.233.112.

Ping has started ...

PING 12.129.233.112 (12.129.233.112): 56 data bytes

--- 12.129.233.112 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss

Traceroute has started ...

traceroute to 12.129.233.112 (12.129.233.112), 64 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  2.156 ms  0.895 ms  0.858 ms
 2  ip-58-28-15-31.wxnz.net (58.28.15.31)  13.716 ms  23.485 ms  15.293 ms
 3  ip-58-28-13-83.wxnz.net (58.28.13.83)  20.418 ms  16.828 ms  15.532 ms
 4  ge-0-0-0-akl-core1.wxnz.net (58.28.8.8)  14.959 ms  17.048 ms  40.460 ms
 5  Gi9-1.gw1.akl1.asianetcom.net (203.192.166.105)  14.638 ms  15.069 ms  17.058 ms
 6  po10-0.gw4.lax1.asianetcom.net (202.147.61.189)  145.151 ms  146.850 ms  144.408 ms
 7  po3-0.gw2.lax1.asianetcom.net (202.147.61.117)  144.607 ms  147.413 ms  146.435 ms
 8  12.119.138.33 (12.119.138.33)  165.005 ms  169.626 ms  162.616 ms
 9  * cr1.la2ca.ip.att.net (12.122.128.78)  147.484 ms  146.737 ms
10  gar5.la2ca.ip.att.net (12.122.128.25)  144.676 ms  144.567 ms  146.821 ms
11  12.122.255.74 (12.122.255.74)  148.383 ms *  148.822 ms
12  mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242)  247.837 ms  145.396 ms  158.957 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *
61  * * *
62  * * *
63  * * *
64  * * *




"The surest sign that intelligent life exists elsewhere in the universe is that it has never tried to contact us."

 

- Calvin and Hobbes (Bill Watterson)

194 posts

Master Geek

Trusted

  Reply # 206983 15-Apr-2009 00:36
Send private message

I can locate no IP using that port. I'm not sure why that is - I'm on OSX using netstat within Network Utility.app


me too :D *gush*

Ok go Applications->Utilities->Terminal

netstat -n

Your realm server will be the one with .3724 at the end. Take the .3724 off to get the IP for your realm

EG mine outputs a whole lot of goobley gook which includes the line

tcp4       0      0  10.0.0.240.60189       12.129.236.96.3724     ESTABLISHED

10.0.0.240 is mine own computers IP address so I can assume that the next bit is the foreign address (sez it up the top as well :D)

12.29.236.96 in this example is the realm server IP. I'm logged into the PTR which is curiously still up :D





==================================
- Hone , Often accused of Excess Verbosity
==================================

8027 posts

Uber Geek
+1 received by user: 387

Trusted
Subscriber

  Reply # 207197 16-Apr-2009 02:05
Send private message

Ellisande: Wait, so using SSH/WoWtunnels fixes all of those kinds of issues?


I doubt it, but thats the impression you give me.


Check the difference between the routes like I said, if your route to a tunnel endpoint (doesn't matter whether it's lowerping, wowtunnels or personal guild setup ssh server) in the US is significantly different from your route directly to your wow server you can bypass the problem routers.  Last time I checked traffic from the ssh server went into the AT&T network via a different router (for local US traffic) and not over the problem routers that are causing the problems now and frequently in the past.

If I was still playing wow (which I'm not) I would not play without using some kind of ssh tunnel, on most connections it makes at least 50-100ms difference.  I can't actually imagine arena/pvp without using it.

Lots of them (ssh tunnel services for wow) have free trials.  Most oceanic guilds have setup their own personal ssh servers or simply use lowerping or wowtunnels, at worst it's a couple of bucks per month for -100ms on your ping. 

All I'm saying is I'm surprised there are people playing wow from NZ that haven't heard about ssh tunneling from guildmates etc.  Give it a try if you don't like it or it doesn't work effectively for you oh well no loss.




1 | 2 
View this topic in a long page with up to 500 replies per page Create new topic



Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Geekzone Live »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.