From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Dan Luedtke <maildanrl@googlemail.com>
Cc: netdev@vger.kernel.org
Subject: Re: ping6: why TTL instead of Hop Limit?
Date: Sun, 8 Jan 2012 00:33:04 +0100 [thread overview]
Message-ID: <20120107233304.GA618@hell> (raw)
In-Reply-To: <CAAfuxnJX0ULFvUbrNag2TE3brTZiBv6x9X9_bKnAuD9Q_Oe1Jg@mail.gmail.com>
* Dan Luedtke | 2012-01-07 19:07:03 [+0100]:
>I was just wondering why there is a TTL-field in ping6, although the
>corresponding field in the IPv6 header is called "Hop Limit". [1]
>
>Example:
>> ping6 -c 1 www.linux-ipv6.org
>> 64 bytes from 2001:200:dff:fff1:216:3eff:fea4:f9e9: icmp_seq=1 ttl=48 time=309 ms
>
>What I expected:
>> 64 bytes from 2001:200:dff:fff1:216:3eff:fea4:f9e9: icmp_seq=1 hl=48 time=309 ms
>
>Anyone an idea?
>Should I write a patch or is there a special reason for this?
Sorry, to late! You will break scripts/programms that parse ping6.
Hagen
prev parent reply other threads:[~2012-01-07 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 18:07 ping6: why TTL instead of Hop Limit? Dan Luedtke
2012-01-07 23:33 ` Hagen Paul Pfeifer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120107233304.GA618@hell \
--to=hagen@jauu.net \
--cc=maildanrl@googlemail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).