Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Cherub]

I have my router all set up and everything SEEMS to be right.  When I get into my game (World of Warcraft) my latency meter is always red.  I'm getting 60 frames a second, but always over 600 ms.  Frankly, I don't know what the numbers mean, but I know it's hard to play.

I put my DOS shell up and ran "ping yahoo.com -t" like a Comcast service tech did once, and I get a near consistant result.  The ping comes back at or around 90ms, but approximately every 60 seconds it will "Time out" and then go back to normal.

Any suggestions or questions?  After buying a brand new computer and network setup, I really just wanna play and have fun, but in order to do that I have to tell the whole family "the internet is down for now" and bypass my router to my computer.

[EddieZ]

Are you playing wireless? In that case the latency is probably due to two things: latency that wireless has by nature (it's normally not really fit to use with gaming) and the latency that is added because of the connection quality (i.e. the distance, interference and obstacles the signal meets). Although I must say that 90 ms while pinging yahoo.com also means that your ISP is doing a lousy job. My ping with my ISP is 7 ms... (but there are even better connections)

[Lycan]

Are you running QoS? Post your statetable if you are. I'd like to see it.

[anon]

For an online game such as WoW, using a wireless connection would not play a big role (if any) in performance as if it were a FPS, Racing, or Fighting game.

One problem you might have is packet loss. A friend I know that plays WoW said anything from 200-350 is good and 350-500 is playable.

Also keep this in mind; they’re a lot of factors out of your control that effect your ping.

[Cherub]

Are you playing wireless? In that case the latency is probably due to two things: latency that wireless has by nature (it's normally not really fit to use with gaming) and the latency that is added because of the connection quality (i.e. the distance, interference and obstacles the signal meets). Although I must say that 90 ms while pinging yahoo.com also means that your ISP is doing a lousy job. My ping with my ISP is 7 ms... (but there are even better connections)

Ok, first, let me just state that I am a novice at best when it comes to networking.  Yes, I am playing wireless, although, I've been playing wireless for the last 2 or 3 years with no trouble at all using a Linksys router. 

As far as some of the other obstacles, distance is only approximately 10-15 feet.  There is only 1 wall between my adapter and my router.  I'm using a D-link DWA-160 Xtreme N Dual Band USB adapter(rev.A).  The signal is traveling straight through the wall that is in the signal path at a 90 degree angle to the wall.  My D-Link Wireless Connection Manager reports my network's signal strength at 100%.

As far as my ISP is concerned, I will not defend Comcast.  Although, when I do the same ping without the router, I get a consistant 42ms ping.  Using an ethernet cable from the router I never pinged, but the latency in game was even worse than it was with the wireless adapter.

[Cherub]

Are you running QoS? Post your statetable if you are. I'd like to see it.

Lycan, please elaborate.  Your query went straight over my head.  How would I find out that information and obtain the statetable if it is indeed running?

[Cherub]

For an online game such as WoW, using a wireless connection would not play a big role (if any) in performance as if it were a FPS, Racing, or Fighting game.

One problem you might have is packet loss. A friend I know that plays WoW said anything from 200-350 is good and 350-500 is playable.

Also keep this in mind; they’re a lot of factors out of your control that effect your ping.

Correct.  In game, anything that is under 600ms is easily playable and cons yellow until you get below 375 where it begins to con green.  Above 700 is red.  Wirelessly my in-game meter is reporting at or around 1000ms.  Today, while I played for 30-45 mins I used a wire from my router and I was getting a report of 1800ms.  If I bypass the router with the cable, I get 100-300 and life is good.

----  Here is a question that may or may not matter ----

Would my OS make a difference?   I just bought this system, and I have a 32 bit WinXP loaded.  I found out that my system is actually a 64bit system.  I've ordered WinXP 64 bit, but I'm still waiting for it's arrival.  Other than that, this system is nearly fresh out of the box.  Everything is new, and I hardly have anything loaded on it.

[Reinvented]

Correct.  In game, anything that is under 600ms is easily playable and cons yellow until you get below 375 where it begins to con green.  Above 700 is red.  Wirelessly my in-game meter is reporting at or around 1000ms.  Today, while I played for 30-45 mins I used a wire from my router and I was getting a report of 1800ms.  If I bypass the router with the cable, I get 100-300 and life is good.

----  Here is a question that may or may not matter ----

Would my OS make a difference?   I just bought this system, and I have a 32 bit WinXP loaded.  I found out that my system is actually a 64bit system.  I've ordered WinXP 64 bit, but I'm still waiting for it's arrival.  Other than that, this system is nearly fresh out of the box.  Everything is new, and I hardly have anything loaded on it.

Why would you get XP 64?  It's one of the buggiest OS's out.  After so many years of being out, it still hasn't matured, or gotten better.  Networking is just POOR.  In fact, you should get Vista maybe.  At least that'll be more stable for you.  I play WoW as well.  And a lot of the times, the latency problems aren't from hardware alone.  It's settings that YOU use. 

Turn off DNS Relay in the router, and see if it improves.

[EddieZ]

OS does not make a difference.

You can find the things from Lycan here: http://192.168.0.1/Advanced/Traffic_Shaping.shtml

[Cherub]

Why would you get XP 64?  It's one of the buggiest OS's out.  After so many years of being out, it still hasn't matured, or gotten better.  Networking is just POOR.  In fact, you should get Vista maybe.  At least that'll be more stable for you.  I play WoW as well.  And a lot of the times, the latency problems aren't from hardware alone.  It's settings that YOU use. 

Turn off DNS Relay in the router, and see if it improves.

I'll see if I can find that and turn it off (assuming it's on).  I'm actually here on the assumption that I have something set wrong, otherwise I wouldn't bother asking, I'd just go exchange the router.  Although, the pings that I do to yahoo.com exist outside the game, and I don't think the ethernet ports are any better, in fact I think they are worse.

My problem is that even though I am quick to learn about computers and such, I have literally no experience in networking, and I don't know what to look for to see if something is wrong.  I'll try your suggestion and hope for the best.

As far as WinXP 64 goes...it was what the guy in our IS dept suggested.  I hope I dont wind up sorry.  But, I suspect I'll probably buy Windows 7 when it hits the shelf.  I have the beta version and a license to use it, but I didn't know if it would be wise considering I'm already experiencing problems elsewhere.

[Cherub]

OS does not make a difference.

You can find the things from Lycan here: http://192.168.0.1/Advanced/Traffic_Shaping.shtml

Thanks Eddie

[Cherub]

Are you running QoS? Post your statetable if you are. I'd like to see it.

Ok, I find that the QoS engine is indeed enabled.  I don't know what a statetable is though.  This is how the section is set:

WAN Traffic Shaping

Enable Traffic Shaping:     (checked)
Automatic Uplink Speed :  (checked)
Measured Uplink Speed :   8149 kbps
Manual Uplink Speed :      128  kbps  (this is greyed out) <<
Connection Type :           [auto-detect]
Detected xDSL or Other Frame Relay Network : No

QoS Engine Setup

Enable QoS Engine :        (checked)
Automatic Classification : (checked)
Dynamic Fragmentation :  (checked)

[There are no checked options under QoS Engine Rules.]

[Reinvented]

Ok, I find that the QoS engine is indeed enabled.  I don't know what a statetable is though.  This is how the section is set:

WAN Traffic Shaping

Enable Traffic Shaping:     (checked)
Automatic Uplink Speed :  (checked)
Measured Uplink Speed :   8149 kbps
Manual Uplink Speed :      128  kbps  (this is greyed out) <<
Connection Type :           [auto-detect]
Detected xDSL or Other Frame Relay Network : No

QoS Engine Setup

Enable QoS Engine :        (checked)
Automatic Classification : (checked)
Dynamic Fragmentation :  (checked)

[There are no checked options under QoS Engine Rules.]

Well, again...try QoS disabled.  Although, I believe it to do a good job even without rules, and set to automatic classification.

Statetable can be found in Status and "Sessions". 

[Cherub]

Well, again...try QoS disabled.  Although, I believe it to do a good job even without rules, and set to automatic classification.

Statetable can be found in Status and "Sessions". 

Tried without QoS enabled, and also disabled WAN traffic shaping, no change in behavior. 

Although I did upgrade the firmware to 1.21   This didn't change anything on the wireless end, but I was getting no packetloss or ping timeouts while connected to my router with a cable.  So now the problem seems only to be a wireless issue.

[Reinvented]

Tried without QoS enabled, and also disabled WAN traffic shaping, no change in behavior. 

Although I did upgrade the firmware to 1.21   This didn't change anything on the wireless end, but I was getting no packetloss or ping timeouts while connected to my router with a cable.  So now the problem seems only to be a wireless issue.

Well, you can go ahead and enable it then.  Also, turn off "WISH", and post up your wireless settings while you are at it.  This can be found in the Setup tab, and "Wireless'.  Let's see if we can tweak it a bit.