From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] ping icmp ttl exceeded
Date: Sun, 3 Feb 2013 23:10:14 -0800 [thread overview]
Message-ID: <CAA93jw6JDTQP6b6hqVgHbOv5YcALQ7a0jd9DnEOoNGb-cSE5ww@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
I have been largely looking at packet captures for tcp streams. today I
noticed that I was oddly getting icmp ttl exceeded messages back on the
network from various devices on the path when I wasn't even pinging...
I have to admit parsing icmp is not in my skillset. Is there useful
information in the icmp messages in this capture?
http://snapon.lab.bufferbloat.net/~d/ttl_exceeded.cap
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 679 bytes --]
next reply other threads:[~2013-02-04 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 7:10 Dave Taht [this message]
2013-02-04 7:33 ` Ketan Kulkarni
2013-02-04 7:34 ` Ketan Kulkarni
2013-02-04 7:41 ` Dave Taht
2013-02-04 14:17 ` Maciej Soltysiak
2013-02-04 16:37 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6JDTQP6b6hqVgHbOv5YcALQ7a0jd9DnEOoNGb-cSE5ww@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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