cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3425
Views
5
Helpful
3
Replies

strange TTL problem

mhogenbirk
Level 1
Level 1

                   Hi all,

I have a cisco airport 1040 attached to a SG300 switch.

The issue i found is strange;if i connect to the network using a wireless client, and perform a ping-test to the default gateway, i get a responce with a low TTL, when i ping my Router i do not have this, and when i ping my server(which is on a different vlan, i get another TTL again.

As far as i noticed, there is no impact to the network.

Ping-test to my server:

C:\Documents and Settings\menno hogenbirk>ping 192.168.5.2

Pingen naar 192.168.5.2 met 32 byte gegevens:

Antwoord van 192.168.5.2: bytes=32 tijd=2 ms TTL=127
Antwoord van 192.168.5.2: bytes=32 tijd=1 ms TTL=127
Antwoord van 192.168.5.2: bytes=32 tijd=1 ms TTL=127
Antwoord van 192.168.5.2: bytes=32 tijd=2 ms TTL=127

Ping-statistieken voor 192.168.5.2:
    Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
    (0% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in mill
iseconden:
    Minimum = 1ms, Maximum = 2ms, Gemiddelde = 1ms

Ping-test to default-gateway:

C:\Documents and Settings\menno hogenbirk>ping 192.168.4.1

Pingen naar 192.168.4.1 met 32 byte gegevens:

Antwoord van 192.168.4.1: bytes=32 tijd=1 ms TTL=64
Antwoord van 192.168.4.1: bytes=32 tijd=1 ms TTL=64
Antwoord van 192.168.4.1: bytes=32 tijd=1 ms TTL=64
Antwoord van 192.168.4.1: bytes=32 tijd=1 ms TTL=64

Ping-statistieken voor 192.168.4.1:
    Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
    (0% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in mill
iseconden:
    Minimum = 1ms, Maximum = 1ms, Gemiddelde = 1ms

Ping-test to router:

C:\Documents and Settings\menno hogenbirk>ping 192.168.1.1

Pingen naar 192.168.1.1 met 32 byte gegevens:

Antwoord van 192.168.1.1: bytes=32 tijd=2 ms TTL=254
Antwoord van 192.168.1.1: bytes=32 tijd=1 ms TTL=254
Antwoord van 192.168.1.1: bytes=32 tijd=1 ms TTL=254
Antwoord van 192.168.1.1: bytes=32 tijd=1 ms TTL=254

Ping-statistieken voor 192.168.1.1:
    Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
    (0% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in mill
iseconden:
    Minimum = 1ms, Maximum = 2ms, Gemiddelde = 1ms

As you can see from the above the TTL to the router is the lowest.

While in my opinion i should have a lower TTL while pinging to my switch, since traffic has to traverse the switch to come to the router.

Please help.

1 Accepted Solution

Accepted Solutions

Richard Burts
Hall of Fame
Hall of Fame

To understand what is going on here we should start with the question of where and how the TTL is set. When you send a ping to some device you set the TTL on the ping request. The device sends a response and the responding device sets the TTL in the response. The TTL value that you see in your results is the TTL of the response coming to you. Various OS will set the TTL differently. Some, like the router will start with 255. Some like the server may start at 128. And some, like your default gateway may start at 64.

So the differences that you are seeing in TTL are no more than the differences in how various OS will set the TTL. It should have no impact on network performance and is not anything to be concerned about.

HTH

Rick

HTH

Rick

View solution in original post

3 Replies 3

Richard Burts
Hall of Fame
Hall of Fame

To understand what is going on here we should start with the question of where and how the TTL is set. When you send a ping to some device you set the TTL on the ping request. The device sends a response and the responding device sets the TTL in the response. The TTL value that you see in your results is the TTL of the response coming to you. Various OS will set the TTL differently. Some, like the router will start with 255. Some like the server may start at 128. And some, like your default gateway may start at 64.

So the differences that you are seeing in TTL are no more than the differences in how various OS will set the TTL. It should have no impact on network performance and is not anything to be concerned about.

HTH

Rick

HTH

Rick

Thanks alot Rick for your reply.

I am glad that my response helped you to understand what is going on with the various TTL values. Thank you for using the rating system to mark this question as answered. It makes the forum more useful when people can read a question and can know that a correct answer was given. Your marking has contributed to this process.

HTH

Rick

HTH

Rick
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco