Time To Live?

kareem_nasser

TTL is sometimes high on some websites like FB why is that?

Kassem

I don't get it... what are you talking about?

rolf

TTL of what? TCP? TTL of TCP should be the same, AFAIK

kareem_nasser

Pinging twitter.com [168.143.162.116] with 32 bytes of data:

Reply from 168.143.162.116: bytes=32 time=543ms TTL=232
Reply from 168.143.162.116: bytes=32 time=535ms TTL=232
Reply from 168.143.162.116: bytes=32 time=548ms TTL=232
Reply from 168.143.162.116: bytes=32 time=554ms TTL=232
Reply from 168.143.162.116: bytes=32 time=540ms TTL=232
Request timed out.
Reply from 168.143.162.116: bytes=32 time=545ms TTL=232
Reply from 168.143.162.116: bytes=32 time=544ms TTL=232
Reply from 168.143.162.116: bytes=32 time=541ms TTL=232
Reply from 168.143.162.116: bytes=32 time=542ms TTL=232
Reply from 168.143.162.116: bytes=32 time=546ms TTL=232
Reply from 168.143.162.116: bytes=32 time=539ms TTL=232
Reply from 168.143.162.116: bytes=32 time=553ms TTL=232
Reply from 168.143.162.116: bytes=32 time=546ms TTL=232
Reply from 168.143.162.116: bytes=32 time=545ms TTL=232
Reply from 168.143.162.116: bytes=32 time=547ms TTL=232
Reply from 168.143.162.116: bytes=32 time=545ms TTL=232
Reply from 168.143.162.116: bytes=32 time=543ms TTL=232
Reply from 168.143.162.116: bytes=32 time=543ms TTL=232

So TCP/IP.

J4D

Why is that ? , its rather server side or client side (ISP) and i doubt it's the server ;-) .

kareem_nasser

It happens on FB sometimes and it f***s up everything.

Hmmm:

Pinging idm.net.lb [193.188.135.50] with 32 bytes of data:

Reply from 193.188.135.50: bytes=32 time=73ms TTL=123
Request timed out.
Reply from 193.188.135.50: bytes=32 time=75ms TTL=123
Reply from 193.188.135.50: bytes=32 time=72ms TTL=123
Reply from 193.188.135.50: bytes=32 time=77ms TTL=123
Reply from 193.188.135.50: bytes=32 time=74ms TTL=123
Reply from 193.188.135.50: bytes=32 time=68ms TTL=123
Reply from 193.188.135.50: bytes=32 time=120ms TTL=123
Reply from 193.188.135.50: bytes=32 time=72ms TTL=123
Reply from 193.188.135.50: bytes=32 time=77ms TTL=123
Reply from 193.188.135.50: bytes=32 time=72ms TTL=123
Request timed out.
Reply from 193.188.135.50: bytes=32 time=74ms TTL=123
Reply from 193.188.135.50: bytes=32 time=69ms TTL=123
Reply from 193.188.135.50: bytes=32 time=69ms TTL=123
Reply from 193.188.135.50: bytes=32 time=67ms TTL=123
Reply from 193.188.135.50: bytes=32 time=69ms TTL=123
Reply from 193.188.135.50: bytes=32 time=68ms TTL=123
Reply from 193.188.135.50: bytes=32 time=68ms TTL=123
Reply from 193.188.135.50: bytes=32 time=69ms TTL=123
Reply from 193.188.135.50: bytes=32 time=71ms TTL=123
Reply from 193.188.135.50: bytes=32 time=63ms TTL=123
Reply from 193.188.135.50: bytes=32 time=65ms TTL=123
Reply from 193.188.135.50: bytes=32 time=72ms TTL=123
Reply from 193.188.135.50: bytes=32 time=72ms TTL=123
Reply from 193.188.135.50: bytes=32 time=68ms TTL=123
Reply from 193.188.135.50: bytes=32 time=70ms TTL=123
Reply from 193.188.135.50: bytes=32 time=67ms TTL=123
Reply from 193.188.135.50: bytes=32 time=71ms TTL=123
Reply from 193.188.135.50: bytes=32 time=74ms TTL=123
Reply from 193.188.135.50: bytes=32 time=71ms TTL=123
Reply from 193.188.135.50: bytes=32 time=73ms TTL=123
Reply from 193.188.135.50: bytes=32 time=76ms TTL=123
Reply from 193.188.135.50: bytes=32 time=73ms TTL=123
Reply from 193.188.135.50: bytes=32 time=66ms TTL=123
Reply from 193.188.135.50: bytes=32 time=70ms TTL=123
Reply from 193.188.135.50: bytes=32 time=68ms TTL=123
Reply from 193.188.135.50: bytes=32 time=70ms TTL=123
Reply from 193.188.135.50: bytes=32 time=72ms TTL=123
Reply from 193.188.135.50: bytes=32 time=64ms TTL=123
Reply from 193.188.135.50: bytes=32 time=65ms TTL=123

euryale

isn't that related to the OS the server is running on?

darko

do a traceroute and paste result

kareem_nasser

Tracing route to idm.net.lb [193.188.135.50]
over a maximum of 30 hops:

  1    20 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3    47 ms    45 ms    45 ms  172.50.1.1
  4    43 ms    43 ms    46 ms  10.0.1.6
  5    52 ms    54 ms    58 ms  213.175.184.203
  6    44 ms    45 ms    46 ms  193.188.135.50

Tracing route to twitter.com [128.242.240.20]
over a maximum of 30 hops:

1 81 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 * * * Request timed out.
3 47 ms 47 ms 45 ms 172.50.1.1
4 50 ms 60 ms 46 ms 10.0.1.6
5 43 ms 44 ms 43 ms 213.175.184.193
6 43 ms 46 ms 45 ms 212.36.211.33
7 * * * Request timed out.
8 433 ms 435 ms 439 ms 12.118.94.97
9 433 ms 444 ms 431 ms cr2.n54ny.ip.att.net [12.122.130.166]
10 428 ms 453 ms 436 ms n54ny01jt.ip.att.net [12.122.81.69]
11 * * * Request timed out.
12 440 ms 427 ms 434 ms 129.250.2.220
13 460 ms 454 ms 448 ms as-0.r20.chcgil09.us.bb.gin.ntt.net [129.250.6.1
3]
14 469 ms 456 ms 464 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.9
8]
15 513 ms 531 ms 524 ms as-5.r20.snjsca04.us.bb.gin.ntt.net [129.250.3.7
7]
16 517 ms 517 ms 503 ms ae-2.r20.mlpsca01.us.bb.gin.ntt.net [129.250.5.6
]
17 503 ms 510 ms 506 ms mg-1.c20.mlpsca01.us.da.verio.net [129.250.28.81
]
18 501 ms 516 ms 497 ms 128.241.122.197
19 505 ms 508 ms 509 ms 128.242.240.5
20 496 ms 497 ms 522 ms 128.242.240.20

these tests were taken at 1:40 am and i was using xfire's voice chat.

rolf

TTL is a variable in the packet. Everytime a router recieves a packet, it is supposed to decrement the TTL (by 1 I think) then forward the packet. When TTL reaches 0, the router receiving the packet must discard it. The aim of this mechanism is to discard packets that enter infinite loops.
Maybe some routers are changing the TTL in a non-compliant way, increasing it for example. I think this is what is happening here.

kareem_nasser

Kassem wroteI don't get it... what are you talking about?

This is TTL
and Rolf explained it too.
According to This site the TTL should normaly be 64.

rolf

kareem_nasser wrote
Kassem wroteI don't get it... what are you talking about?
This is TTL
and Rolf explained it too.
According to This site the TTL should normaly be 64.

The initial TTL, the one on your Packet when it leaves your machine. But I think the ping output shows the TTL of returning packets after they have traveled through the network.

kareem_nasser

Did the same thing in my students home, they have the same ISP IDM but 256k plan and the TTL and Latency was the same even though the post is different.
omg websites are taking so much time to respond as if i have Dial-up.

sandbox

Just to clarify things, TTL is irrelevant to the speed.
You will get the same TTL even if you ping from the internet :
http://www.his.com/cgi-bin/ping?

The Latency is obviously high(That is what is affecting the speed) and as you can see, the time it is taking to get a return packet jumps from 45milliseconds to 439milliseconds as soon you leave the DM network(212.36.211.33) so it must be a problem on their side..

It is funny you say you feel like you are on dialup because the previous IP address is registered as residential dial up - That does it mean it is dialup though :-)
http://tools.whois.net/whoisbyip/

inetnum: 212.36.199.0 - 212.36.223.255
netname: IDM-RESIDENTIAL-DIALUP

Hope that helps.

Sandbox

kareem_nasser

Yup every time i check my ip it detects it as Dial up and as for the prob is on their side to be more specific it is on the Ogero side. ;)

sandbox

Out of interest, how do you know it is ogero and not DM ?

sandbox

kareem_nasser

I meant the gov as usual probably testing something.