PTCL dsl ping result

Here is my ping to server result

its not consistent. what could be the reason. im getting slow web browsing. using 4mb connection.

Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 8ms, Maximum = 368ms, Average = 246ms

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=30ms TTL=255

Reply from 192.168.1.1: bytes=32 time=28ms TTL=255

Request timed out.

Request timed out.

Request timed out.

Reply from 192.168.1.1: bytes=32 time=8ms TTL=255

Reply from 192.168.1.1: bytes=32 time=106ms TTL=255

Reply from 192.168.1.1: bytes=32 time=233ms TTL=255

Reply from 192.168.1.1: bytes=32 time=172ms TTL=255

Request timed out.

Reply from 192.168.1.1: bytes=32 time=5ms TTL=255

Reply from 192.168.1.1: bytes=32 time=88ms TTL=255

Reply from 192.168.1.1: bytes=32 time=3ms TTL=255

Reply from 192.168.1.1: bytes=32 time=11ms TTL=255

Reply from 192.168.1.1: bytes=32 time=25ms TTL=255

Reply from 192.168.1.1: bytes=32 time=135ms TTL=255

Reply from 192.168.1.1: bytes=32 time=253ms TTL=255

Reply from 192.168.1.1: bytes=32 time=116ms TTL=255

Reply from 192.168.1.1: bytes=32 time=16ms TTL=255

Request timed out.

Reply from 192.168.1.1: bytes=32 time=178ms TTL=255

Reply from 192.168.1.1: bytes=32 time=244ms TTL=255

Reply from 192.168.1.1: bytes=32 time=94ms TTL=255

Reply from 192.168.1.1: bytes=32 time=104ms TTL=255

Reply from 192.168.1.1: bytes=32 time=14ms TTL=255

Request timed out.

Reply from 192.168.1.1: bytes=32 time=6ms TTL=255

Reply from 192.168.1.1: bytes=32 time=107ms TTL=255

Reply from 192.168.1.1: bytes=32 time=117ms TTL=255

Reply from 192.168.1.1: bytes=32 time=11ms TTL=255

Reply from 192.168.1.1: bytes=32 time=5ms TTL=255

Reply from 192.168.1.1: bytes=32 time=140ms TTL=255

Request timed out.

Reply from 192.168.1.1: bytes=32 time=8ms TTL=255

Reply from 192.168.1.1: bytes=32 time=84ms TTL=255

Reply from 192.168.1.1: bytes=32 time=79ms TTL=255

Reply from 192.168.1.1: bytes=32 time=70ms TTL=255

Reply from 192.168.1.1: bytes=32 time=6ms TTL=255

Reply from 192.168.1.1: bytes=32 time=3ms TTL=255

Reply from 192.168.1.1: bytes=32 time=7ms TTL=255

Reply from 192.168.1.1: bytes=32 time=5ms TTL=255

Reply from 192.168.1.1: bytes=32 time=3ms TTL=255

Request timed out.

Reply from 192.168.1.1: bytes=32 time=629ms TTL=255

Reply from 192.168.1.1: bytes=32 time=969ms TTL=255

Reply from 192.168.1.1: bytes=32 time=72ms TTL=255

Reply from 192.168.1.1: bytes=32 time=2ms TTL=255

Request timed out.

Reply from 192.168.1.1: bytes=32 time=3ms TTL=255

Reply from 192.168.1.1: bytes=32 time=4ms TTL=255

Reply from 192.168.1.1: bytes=32 time=4ms TTL=255

Reply from 192.168.1.1: bytes=32 time=3ms TTL=255

Ping statistics for 192.168.1.1:

Packets: Sent = 52, Received = 43, Lost = 9 (17% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 969ms, Average = 97ms

looks like a wireless connection to me, try wired for better ping and try to ping when all applications for e.g utorrent are closed..

yes, its a wireless connection.

its etisalat wireless router.

Actually, a wireless connection shouldn't have so high a ping for local networks.

Could you try changing the channel number in your wifi router and see if that helps anything?

OR - try another modem. Or try connecting via LAN and see if the problem persists.

i have 2 wireless routers. one is connected to dsl and other is used as an access point. Both are connected via wireless bridge.

the other one gives me this

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time=19ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=1ms TTL=255

Reply from 192.168.1.2: bytes=32 time=1ms TTL=255

Reply from 192.168.1.2: bytes=32 time=9ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=3ms TTL=255

Reply from 192.168.1.2: bytes=32 time=3ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=9ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=6ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=5ms TTL=255

Reply from 192.168.1.2: bytes=32 time=84ms TTL=255

Reply from 192.168.1.2: bytes=32 time=122ms TTL=255

Reply from 192.168.1.2: bytes=32 time=19ms TTL=255

Reply from 192.168.1.2: bytes=32 time=1ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=1ms TTL=255

Reply from 192.168.1.2: bytes=32 time=4ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=3ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=7ms TTL=255

Reply from 192.168.1.2: bytes=32 time=2ms TTL=255

Reply from 192.168.1.2: bytes=32 time=69ms TTL=255

Reply from 192.168.1.2: bytes=32 time=1ms TTL=255

Ping statistics for 192.168.1.2:

Packets: Sent = 34, Received = 34, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 122ms, Average = 11ms

I've never used bridging on my wifi router - but I think it would be a good idea to assign different IPs to each router instead of sticking to one IP range.

The second router seems to function well.

Perhaps its a channel-conflict (random speculation) or your router needs a (re)boot!