From: Marek Lindner <lindner_marek@yahoo.de>
To: "Vasiliy Kulikov" <segooon@gmail.com>,
"Linus Lüssing" <linus.luessing@web.de>
Cc: "Greg Kroah-Hartman" <gregkh@suse.de>,
Andrew Lunn <andrew@lunn.ch>,
Sven Eckelmann <sven.eckelmann@gmx.de>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: batman-adv: design suggestions
Date: Sat, 14 Aug 2010 16:59:13 +0200 [thread overview]
Message-ID: <201008141659.14868.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20100813181833.GA5632@albatros>
On Friday 13 August 2010 20:18:33 Vasiliy Kulikov wrote:
> d) Why do you send icmp TTL exceeded for the icmp itself? E.g. in case
> of loop or/and small default TTL you'll probably get a storm of icmps.
> Exactly in this case IP silently drops TTL exceeded icmps ;)
These layer2 icmp packets are not ordinary icmp packets. We needed to provide
a mechanism to make the network topology visible to debug tools like ping or
traceroute which normally "see" no more than one hop as they operate on
layer3. Hence, batman-adv does not send an icmp packet for each payload TTL
exceeded but for traceroute only. I recommend reviewing the traceroute code to
understand how this is supposed to work:
http://www.open-mesh.org/browser/trunk/batctl/traceroute.c
I'd be interested to learn about a problematic scenario in which this
mechanism breaks.
Regards,
Marek
next prev parent reply other threads:[~2010-08-14 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 20:34 batman-adv: design suggestions Vasiliy Kulikov
2010-08-09 20:53 ` Sven Eckelmann
2010-08-12 12:48 ` Vasiliy Kulikov
2010-08-14 14:50 ` Marek Lindner
2010-08-14 16:19 ` Vasiliy Kulikov
2010-08-14 17:10 ` Marek Lindner
2010-08-13 18:18 ` Vasiliy Kulikov
2010-08-13 23:25 ` Sven Eckelmann
2010-08-14 14:59 ` Marek Lindner [this message]
2010-08-14 16:13 ` Vasiliy Kulikov
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=201008141659.14868.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=andrew@lunn.ch \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linus.luessing@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=segooon@gmail.com \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=sven.eckelmann@gmx.de \
/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