Router and Internet connection

[derekliu]

This thread is regd my concerns abt GAMING and ROUTER connection


The problem is this. Last time when im playing games like Battlefield 2 or DOTA, i will not experience any lags at all with my Starhub MOL. Last time im using direct connection from modem to my comp USB.

I had been using Linksys router and USB adapter for the past few mths due to i moved my comp further away from the modem and into my own room. So a router had to be used. But ever since i went on wireless, the online games i played are not enjoyable as i will always experience lag spike.

Lag spikes occurs like when im moving ard in the game. It would stop for a few secs then back to normal again. This intermitten start/stop had been irritating.

I had not do any settings to my router yet. Is there any settings i need to config so that i can enjoy lag-free online gaming?

Or shld i juz dump my wireless and installed a SCV point in my room as a last resort?

Thanks for hearing my whinning.

[Pokémon]

First of all, was the wireless router setup by you? Did you ensure that wireless access is secured?

[derekliu]

First of all, was the wireless router setup by you? Did you ensure that wireless access is secured?

of cos la -.-

This basic security i know, when install new router must lock my router to prevent other ppl to use...

[liangtam]

ping 192.168.1.1 -n 1000

[derekliu]

ping 192.168.1.1 -n 1000

Muz put -n??

[misato]

yup. in fact -n 1000 is considered too low.
For gaming activities, you should consider ping -n 10240 to check your latency to your router.
For your local network (wired / wireless) if latency is greater then 5ms, it suggest that you might have some minor issue with your network.

[iCuteCube]

The exact instruction for noob is.

Start > Run > Cmd

Key in "Ping 192.168.1.1 -n 10240"

If your default gateway is not 192.168.1.1 change it to your gateway address.
Press control+C to break the operation.

[theView]

stable wrieless is subjected to placement and location

so it is a highly subjective to situation and at time configuration has a part to play too.

so you have the time, they have their troubles

[derekliu]

yup. in fact -n 1000 is considered too low.
For gaming activities, you should consider ping -n 10240 to check your latency to your router.
For your local network (wired / wireless) if latency is greater then 5ms, it suggest that you might have some minor issue with your network.

ok i followed wat u asked me to do.

90% of the time i got 1ms, the rest is 2 or 3ms, got one is 1000+ms.

Is my latency good? Seriously im feeling frustrated playing games with spike lag :s22:

[liangtam]

Give us the average value instead, or preferably the whole summarized statistics information

[derekliu]

Give us the average value instead, or preferably the whole summarized statistics information

Roger Sir



Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1600ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 65, Received = 65, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1600ms, Average = 25ms

[MrJacky]

A wireless connection is always subjected to interference.

When you play connection-sensitive games like BF2 wirelessly you will definitely get a choppy experience, this is what I normally encounter (I have yet the time to set up my wireless network properly, hence).

Like what others said, placement of the router is very important if you want a stable wireless connection. The difference is very obvious when I play BF2 wirelessly on my Linksys router placed in a central location as compared to the 2WIRE modem router placed further.

You don't have to install another cable point in your room. You got tons of other option, including using Powerline Networking to get an Ethernet connection through the use of your power lines.

[derekliu]

You don't have to install another cable point in your room. You got tons of other option, including using Powerline Networking to get an Ethernet connection through the use of your power lines.

Thanks for the heads-up. But can explain how this works? I networking noob :s22: And which guide shld i start reading on...

[MrJacky]

Thanks for the heads-up. But can explain how this works? I networking noob :s22: And which guide shld i start reading on...
I have never used it before but I have read about it and have also seen it on sale.

You are basically using your power lines to act as Ethernet cables.

Plug one Powerline adapter into a power point and connect it to your router.

Plug the other Powerline adapter into another power point and connect it to your PC.

It makes use of your power line to provide you an Ethernet connection.

Like I said I have never used it before but I think that's how it works.

[liangtam]

Eh, 65 count only ah. I thot you did a 10240 count job liao. Too few for generalization

Anyway 1-2ms is good. Your gaming issue is probably somewhere else.

[theView]

Roger Sir



Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1600ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 65, Received = 65, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1600ms, Average = 25ms

saw your problems liao

this is the problems
Reply from 192.168.1.1: bytes=32 time=1600ms TTL=64

this glitch will repeat at interval in the ping list if you let the ping run for 30 mins

that cause the jerk in your game play

[derekliu]

saw your problems liao

this is the problems
Reply from 192.168.1.1: bytes=32 time=1600ms TTL=64

this glitch will repeat at interval in the ping list if you let the ping run for 30 mins

that cause the jerk in your game play

ya i believe so too. there will be a rise in latency once awhile, and thats when my game will experience the lag spikes.

Do u have any solution to this?

[MrJacky]

Either
1) Keep playing around with your wireless setup. You may be able to fix it, but it's mostly trial and error. Interference will always be there.

OR
2) Use a wireless connection if that's the most convenient to you, but try to switch to an Ethernet connection for games that are sensitive to latency (BF2 for instance).

[daniel0ng]

The exact instruction for noob is.

Start > Run > Cmd

Key in "Ping 192.168.1.1 -n 10240"

If your default gateway is not 192.168.1.1 change it to your gateway address.
Press control+C to break the operation.

Got a question to ask, is it -n or -l? You're doing a 10240 counts of ping test, not 10240 bytes (10kB) test right?

[misato]

both -l and -n is important.

-l 10240 is stipulate gaming packet size
-n is the number of counts ping, a sizable amount like 3000 would be good to analysis the frequency of the spikes and high latency.