Ping on EVDO may or may not be the same as the BSNL data one connection, regardless data rate will be very slow.Why don't you tell us what is it you are exactly trying to figure out?There is a big possibility it may not be worth trying on EVDO!
-
Amazon Deals - ToS - Like us?
Americas Army PING - Please Reply :)
- Thread starter arnold991
- Start date
- Replies 20
- Views 6,815
- Status
neevarp
Regulars
Ok, am on BSNL broadband and here are my ping values*
*Ok i know u r looking forward for ping values of EVDO users only, but i posted this so that u can compare it with wireline users. Please post your ping values for the servers too.
Code:
C:\Documents and Settings\Praveen>ping 63.209.32.63Pinging 63.209.32.63 with 32 bytes of data:Reply from 63.209.32.63: bytes=32 time=463ms TTL=112Reply from 63.209.32.63: bytes=32 time=465ms TTL=112Reply from 63.209.32.63: bytes=32 time=464ms TTL=112Request timed out.Ping statistics for 63.209.32.63: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),Approximate round trip times in milli-seconds: Minimum = 463ms, Maximum = 465ms, Average = 464msC:\Documents and Settings\Praveen>ping 193.200.158.186Pinging 193.200.158.186 with 32 bytes of data:Reply from 193.200.158.186: bytes=32 time=306ms TTL=117Reply from 193.200.158.186: bytes=32 time=306ms TTL=117Reply from 193.200.158.186: bytes=32 time=306ms TTL=117Reply from 193.200.158.186: bytes=32 time=307ms TTL=117Ping statistics for 193.200.158.186: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 306ms, Maximum = 307ms, Average = 306msC:\Documents and Settings\Praveen>ping 85.214.33.247Pinging 85.214.33.247 with 32 bytes of data:Reply from 85.214.33.247: bytes=32 time=350ms TTL=53Reply from 85.214.33.247: bytes=32 time=350ms TTL=53Reply from 85.214.33.247: bytes=32 time=350ms TTL=53Reply from 85.214.33.247: bytes=32 time=350ms TTL=53Ping statistics for 85.214.33.247: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 350ms, Maximum = 350ms, Average = 350msthx cool_techie bro for posting the result...at least I got the dataone ping info. But as you have said I am actually looking for EVDO user reply regarding this. Thx @Mac: Bro bro, I know wired connection will always be better than wireless connection for latency purporse. But in my area there is only possibility of Wireless connection. 
So I am interested in knowing the ping one can get on EVDO. I hope some EVDO user will see this thread and post the results I need. 
@Mac: Bro bro, I know wired connection will always be better than wireless connection for latency purporse. But in my area there is only possibility of Wireless connection. So I am interested in knowing the ping one can get on EVDO. I hope some EVDO user will see this thread and post the results I need. The reason i'm telling you that a ping would not help your cause is that when on a wireless network the data rate is not constant so the rate of flow of data is changing all the time. Which will result in huge amount of lag. Try asking people to put a tracert result is going to be better as then you would know the number of hops between local comp and the american server. The lower the hops the better it is going to be. (tracert gives you info on the ping on each hop.) ping only gives the imp info about TTL.apart from any packets droped.
The reason i'm telling you that a ping would not help your cause is that when on a wireless network the data rate is not constant so the rate of flow of data is changing all the time. Which will result in huge amount of lag. Try asking people to put a tracert result is going to be better as then you would know the number of hops between local comp and the american server. The lower the hops the better it is going to be. (tracert gives you info on the ping on each hop.) ping only gives the imp info about TTL.
apart from any packets droped.
Thats some nice info regarding knowing the correct latency... Gone little above my head...hehe
Thx Mac bro... :ashamed:
apart from any packets droped.
Thats some nice info regarding knowing the correct latency... Gone little above my head...hehe
Thx Mac bro... :ashamed:
neevarp
Regulars
1) Hold down your [windows key + R] to use the run command shortcut or go to your start menu and click on run.2) Once you use the short cut or use the run button in the start menu the run command will popup.3) After you type in "cmd" with out the quotes in the in the command line and click on OK button and the CMD.exe program will open.4) This is the CMD.exe and it can do ms-dos commands and ping website and IP addresses.5) Once you are in the CMD.exe you need to type in the first line. Type "ping" and a space then type in the website address or an IP address and hit the enter key on your keyboard.
BSNL EVDO in Thrissur. Now this could vary if I go to another part of my house.
dont think its really the best choice for gaming
Code:
Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.C:\Documents and Settings\Administrator>ping 63.209.32.6Pinging 63.209.32.63 with 32 bytes of data:Reply from 63.209.32.63: bytes=32 time=737ms TTL=108Reply from 63.209.32.63: bytes=32 time=357ms TTL=108Reply from 63.209.32.63: bytes=32 time=403ms TTL=108Reply from 63.209.32.63: bytes=32 time=496ms TTL=108Ping statistics for 63.209.32.63: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 357ms, Maximum = 737ms, Average = 498ms
Code:
Pinging 193.200.158.186 with 32 bytes of data:Reply from 193.200.158.186: bytes=32 time=589ms TTL=113Reply from 193.200.158.186: bytes=32 time=679ms TTL=113Reply from 193.200.158.186: bytes=32 time=554ms TTL=113Reply from 193.200.158.186: bytes=32 time=1137ms TTL=113Ping statistics for 193.200.158.186: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 554ms, Maximum = 1137ms, Average = 739ms
Code:
Pinging 85.214.33.247 with 32 bytes of data:Reply from 85.214.33.247: bytes=32 time=397ms TTL=47Reply from 85.214.33.247: bytes=32 time=382ms TTL=47Reply from 85.214.33.247: bytes=32 time=449ms TTL=47Reply from 85.214.33.247: bytes=32 time=529ms TTL=47Ping statistics for 85.214.33.247: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 382ms, Maximum = 529ms, Average = 439ms- Status