From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] TTL yes, TTL no
Date: Sat, 26 Mar 2011 16:31:42 +0100 [thread overview]
Message-ID: <201103261631.42903.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20110326130451.GC10750@ritirata.org>
Hi,
> In these days I was wondering whether the TTL field in the OGM packet is
> really useful or not...Due to hop_penalty an OGM will be discarded as
> soon as the TQ will reach 0 (which is a sort of TTL mechanism itself).
> At this point why is the TTL field needed?
uhm.., you probably are right. As long as there is a hop penalty it also
functions as a TTL. Keep in mind that it is possible to set the hop penalty to
zero. With the current default hop penalty of 10 the maximum number of hops is
limited to 25.
> Someone could probably say that a node far at least TTL hops will never
> be reached by a unicast packet, then it is meaningless to let it know
> about me. But then it could be possible to recalibrate the TTL such that
> it has to be equal to the maximum length in number of hops of the longest
> path the OGM can traverse.
Not quite sure what you are proposing. A TTL of TQ_MAX / hop penalty ?
Cheers,
Marek
next prev parent reply other threads:[~2011-03-26 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 13:04 [B.A.T.M.A.N.] TTL yes, TTL no Antonio Quartulli
2011-03-26 15:31 ` Marek Lindner [this message]
2011-03-26 16:14 ` Andrew Lunn
-- strict thread matches above, loose matches on Subject: below --
2011-03-26 17:21 Antonio Quartulli
2011-03-26 17:45 ` Andrew Lunn
2011-03-26 18:15 ` Antonio Quartulli
2011-03-26 18:01 Antonio Quartulli
2011-03-26 18:17 Antonio Quartulli
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=201103261631.42903.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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