Sign In
Register
Help
Add ReplyGuest, on Sep 24 2005, 11:30 PM, said:
What kind of figures are you expecting? Do you even know how tcp/ip works? Do you know what tcp/ip means?
ADSL Crawling
MultiQuote
#17
woodyear99 
- Board Warrior
-
- Group: Members
- Posts: 282
- Joined: 16-August 05
Posted 25 September 2005 - 11:30 AM
?
Yeah I guess my pings are too good to tstt (my isp) and all other websites online. Yeah and the 200+ pings I get on game servers also are right.
It really doesn't take an IT specialist to know that it is an unbeatable network.
Yeah I guess my pings are too good to tstt (my isp) and all other websites online. Yeah and the 200+ pings I get on game servers also are right.
It really doesn't take an IT specialist to know that it is an unbeatable network.
#18 Guest_Guest_*
Posted 25 September 2005 - 06:54 PM
Here are some figures for you.
Average ping time to closest point on tstt network with a 256kbps service - 15ms
Same ping with a simple P2P app running - 40 to 200 ms
Same ping with Limewire running - 400 ms to 1300 ms to timeouts
Ping to yahoo - 100 to 110 ms
Ping to google - 103 to 105 ms
Ping to toyota UK which is actually hosted in the UK - 180 ms
Ping to toyota JP which is actually hosted in Japan - 252 ms
Notice where the big jumps are.
By the way, I did these pings AFTER making sure I didn't have any viruses or mass mailing worms.
You need to remember that your 256k bandwidth is shared. All apps you run will take a chunk of bandwidth. Some will take a bigger chunk than others And since you don't know about tcp/ip, there are certain protocols which take precedence over others. ICMP is NOT one of them. Use traceroute (also ICMP) instead of ping to tell you where the longest paths are.
So tell me something, will you still complain so much knowing this now? Are you by chance an online gamer?
Average ping time to closest point on tstt network with a 256kbps service - 15ms
Same ping with a simple P2P app running - 40 to 200 ms
Same ping with Limewire running - 400 ms to 1300 ms to timeouts
Ping to yahoo - 100 to 110 ms
Ping to google - 103 to 105 ms
Ping to toyota UK which is actually hosted in the UK - 180 ms
Ping to toyota JP which is actually hosted in Japan - 252 ms
Notice where the big jumps are.
By the way, I did these pings AFTER making sure I didn't have any viruses or mass mailing worms.
You need to remember that your 256k bandwidth is shared. All apps you run will take a chunk of bandwidth. Some will take a bigger chunk than others And since you don't know about tcp/ip, there are certain protocols which take precedence over others. ICMP is NOT one of them. Use traceroute (also ICMP) instead of ping to tell you where the longest paths are.
So tell me something, will you still complain so much knowing this now? Are you by chance an online gamer?
#19
woodyear99
- Board Warrior
-
- Group: Members
- Posts: 282
- Joined: 16-August 05
Posted 26 September 2005 - 11:31 AM
Yeah I do all my tests when nothing else is running, no file sharing/no virii/no downloads/no spyware. Only my machine connected to the modem. I can verify no activity as well since my windows network neighbourhood lights don't blink when idle.
Yeah so I notice high amounts of packet loss and my pings to tstt are 100+ which should be ALOT lower.
I am an online gamer but most of the time my lowest ping is 170+ so it is kinda crappy.
I know the bandwidth is limited so I don't download/upload anything while actually at the pc.
Yeah so I notice high amounts of packet loss and my pings to tstt are 100+ which should be ALOT lower.
I am an online gamer but most of the time my lowest ping is 170+ so it is kinda crappy.
I know the bandwidth is limited so I don't download/upload anything while actually at the pc.
#20
StarCon
- Post Machine
-
- Group: Members
- Posts: 108
- Joined: 05-October 03
Posted 27 September 2005 - 10:46 AM
Quote
I am an online gamer but most of the time my lowest ping is 170+ so it is kinda crappy.
what games do u play ?
there won't be any improvement in latency to us servers anytime soon.
the best I got was about 90ms to an ut2k4 server - which is actually quite
good considering our remote location
#21
woodyear99
- Board Warrior
-
- Group: Members
- Posts: 282
- Joined: 16-August 05
Posted 27 September 2005 - 11:10 AM
These days CS: Source, DOD:Source and World of Warcraft, you?
#22
StarCon
- Post Machine
-
- Group: Members
- Posts: 108
- Joined: 05-October 03
Posted 27 September 2005 - 11:28 AM
Quote
These days CS: Source, DOD:Source and World of Warcraft, you?
nothing really atm .. used to play ut/ut2k ig - but anything above 30ms ping is useless for that. never tried cs: source although it has been sitting on my hd for the longest while
thinking about signing up for city of heroes again.
are u in gatt ?
#23
woodyear99
- Board Warrior
-
- Group: Members
- Posts: 282
- Joined: 16-August 05
Posted 27 September 2005 - 01:08 PM
Nah I just browse the forums....
Also play some Guild Wars, that works good on any connection.
Also play some Guild Wars, that works good on any connection.
#24
Wolfie
- Advanced Member
-
- Group: Members
- Posts: 82
- Joined: 01-July 04
Posted 28 September 2005 - 11:16 AM
woodyear99, on Sep 24 2005, 08:58 PM, said:
Hmm check out these pings , yes my connection rocks courtesy Tstt and the Unbeatable Network...Saturday 9pm...no p2p .
Pinging tstt.net.tt [196.3.132.8] with 32 bytes of data:
Reply from 196.3.132.8: bytes=32 time=125ms TTL=123
Reply from 196.3.132.8: bytes=32 time=166ms TTL=123
Reply from 196.3.132.8: bytes=32 time=121ms TTL=123
Reply from 196.3.132.8: bytes=32 time=81ms TTL=123
Ping statistics for 196.3.132.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 166ms, Average = 123ms
Dear Valued Customer,
TSTT will be conducting routine maintenance work on our High Speed Internet Access (HSIA / ADSL) service on Monday September 26, 2005 during the hours of 1:00am to 4:00am. During the maintenance period you will not be able to access your High Speed Internet service.
TSTT apologizes for the inconvenience but this is necessary in order to ensure the continued reliable supply of the High Speed Internet service.
We thank you for your continued confidence in TSTT High Speed Internet Access and we look forward to continue serving you.
Sincerely
TSTT Internet Services
Pinging tstt.net.tt [196.3.132.8] with 32 bytes of data:
Reply from 196.3.132.8: bytes=32 time=125ms TTL=123
Reply from 196.3.132.8: bytes=32 time=166ms TTL=123
Reply from 196.3.132.8: bytes=32 time=121ms TTL=123
Reply from 196.3.132.8: bytes=32 time=81ms TTL=123
Ping statistics for 196.3.132.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 166ms, Average = 123ms
Dear Valued Customer,
TSTT will be conducting routine maintenance work on our High Speed Internet Access (HSIA / ADSL) service on Monday September 26, 2005 during the hours of 1:00am to 4:00am. During the maintenance period you will not be able to access your High Speed Internet service.
TSTT apologizes for the inconvenience but this is necessary in order to ensure the continued reliable supply of the High Speed Internet service.
We thank you for your continued confidence in TSTT High Speed Internet Access and we look forward to continue serving you.
Sincerely
TSTT Internet Services
As i said before, these values are unacceptable for internal network communication. Too bad TSTT doesn't know that.
#25
StarCon
- Post Machine
-
- Group: Members
- Posts: 108
- Joined: 05-October 03
Posted 28 September 2005 - 01:39 PM
doesn't look too bad down here right now.
Pinging tstt.net.tt [196.3.132.8] with 32 bytes of data:
Reply from 196.3.132.8: bytes=32 time=14ms TTL=124
Reply from 196.3.132.8: bytes=32 time=24ms TTL=124
Reply from 196.3.132.8: bytes=32 time=13ms TTL=124
Reply from 196.3.132.8: bytes=32 time=22ms TTL=124
Ping statistics for 196.3.132.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 24ms, Average = 18ms
---
emule is still crawling though :/
Pinging tstt.net.tt [196.3.132.8] with 32 bytes of data:
Reply from 196.3.132.8: bytes=32 time=14ms TTL=124
Reply from 196.3.132.8: bytes=32 time=24ms TTL=124
Reply from 196.3.132.8: bytes=32 time=13ms TTL=124
Reply from 196.3.132.8: bytes=32 time=22ms TTL=124
Ping statistics for 196.3.132.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 24ms, Average = 18ms
---
emule is still crawling though :/
#26
woodyear99
- Board Warrior
-
- Group: Members
- Posts: 282
- Joined: 16-August 05
Posted 28 September 2005 - 07:49 PM
Hehe Starcon I've never seen such low pings on my tstt connection...with no downloading etc. goin on.
#27 Guest_Guest_*
Posted 28 September 2005 - 08:56 PM
C:\Documents and Settings\>ping tstt.co.tt
Pinging tstt.co.tt [196.3.132.8] with 32 bytes of data:
Reply from 196.3.132.8: bytes=32 time=19ms TTL=127
Reply from 196.3.132.8: bytes=32 time=17ms TTL=127
Reply from 196.3.132.8: bytes=32 time=18ms TTL=127
Reply from 196.3.132.8: bytes=32 time=34ms TTL=127
Ping statistics for 196.3.132.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 34ms, Average = 22ms
Pinging tstt.co.tt [196.3.132.8] with 32 bytes of data:
Reply from 196.3.132.8: bytes=32 time=19ms TTL=127
Reply from 196.3.132.8: bytes=32 time=17ms TTL=127
Reply from 196.3.132.8: bytes=32 time=18ms TTL=127
Reply from 196.3.132.8: bytes=32 time=34ms TTL=127
Ping statistics for 196.3.132.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 34ms, Average = 22ms
#28
StarCon
- Post Machine
-
- Group: Members
- Posts: 108
- Joined: 05-October 03
Posted 28 September 2005 - 11:47 PM
Quote
C:\Documents and Settings\>ping tstt.co.tt
Pinging tstt.co.tt [196.3.132.8] with 32 bytes of data:
Reply from 196.3.132.8: bytes=32 time=19ms TTL=127
Reply from 196.3.132.8: bytes=32 time=17ms TTL=127
Reply from 196.3.132.8: bytes=32 time=18ms TTL=127
Reply from 196.3.132.8: bytes=32 time=34ms TTL=127
Ping statistics for 196.3.132.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 34ms, Average = 22ms
Pinging tstt.co.tt [196.3.132.8] with 32 bytes of data:
Reply from 196.3.132.8: bytes=32 time=19ms TTL=127
Reply from 196.3.132.8: bytes=32 time=17ms TTL=127
Reply from 196.3.132.8: bytes=32 time=18ms TTL=127
Reply from 196.3.132.8: bytes=32 time=34ms TTL=127
Ping statistics for 196.3.132.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 34ms, Average = 22ms
heh.. I win
but...
Pinging www.t-online.de [212.185.47.88] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 212.185.47.88: bytes=32 time=186ms TTL=242
Ping statistics for 212.185.47.88:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 186ms, Maximum = 186ms, Average = 186ms
lol
#29
Nightwolf
- Advanced Member
-
- Group: Members
- Posts: 49
- Joined: 12-October 04
Posted 29 September 2005 - 12:36 AM
Quote
PING 196.3.132.8 (196.3.132.8): 56 data bytes
64 bytes from 196.3.132.8: icmp_seq=0 ttl=124 time=30.0 ms
64 bytes from 196.3.132.8: icmp_seq=1 ttl=124 time=20.0 ms
64 bytes from 196.3.132.8: icmp_seq=2 ttl=124 time=10.0 ms
64 bytes from 196.3.132.8: icmp_seq=3 ttl=124 time=10.0 ms
--- 196.3.132.8 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 10.0/17.5/30.0 ms
64 bytes from 196.3.132.8: icmp_seq=0 ttl=124 time=30.0 ms
64 bytes from 196.3.132.8: icmp_seq=1 ttl=124 time=20.0 ms
64 bytes from 196.3.132.8: icmp_seq=2 ttl=124 time=10.0 ms
64 bytes from 196.3.132.8: icmp_seq=3 ttl=124 time=10.0 ms
--- 196.3.132.8 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 10.0/17.5/30.0 ms
