From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] ping icmp ttl exceeded
Date: Mon, 4 Feb 2013 15:17:09 +0100 [thread overview]
Message-ID: <CAMZR1YDvoSh15hN0Y72P_gs3aVGS8xh=_UcYguCiD+jr16TNLQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6NCyW6OaXzcqtA0KpozV+Mt7NtM=7P0D+7294__-Sbhw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
On Mon, Feb 4, 2013 at 8:41 AM, Dave Taht <dave.taht@gmail.com> wrote:
> Heh. I turned out I'd left mtr running in another window...
Yeah, exactly. Decreasing TTLs suggest traceroute tools :-)
As Ketan noted, it's best to decode what's in the ICMP TTL exceeded payload
to see what packet triggered this.
traceroute uses ICMP ECHO REQUEST
tracepath uses UDP
tcptraceroute uses TCP SYN (this tools is actually usefull to check if your
packets go different routes depending on the port they're going to, e.g.
detecting a transparent proxy which shows up for port 80, but not for
others)
There are other tools which could be used to do the same with different
types of packets, say, crafting a fake ICMP ECHO REPLY to see how good at
being stateful are the firewalls on the path.
Regards,
Maciej
[-- Attachment #2: Type: text/html, Size: 1225 bytes --]
next prev parent reply other threads:[~2013-02-04 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 7:10 Dave Taht
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 [this message]
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='CAMZR1YDvoSh15hN0Y72P_gs3aVGS8xh=_UcYguCiD+jr16TNLQ@mail.gmail.com' \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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