public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
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.] Where can i see, sequence number, eq, rq for an originator?
Date: Wed, 18 Sep 2013 12:08:48 +0200	[thread overview]
Message-ID: <20130918100848.GH3053@neomailbox.net> (raw)
In-Reply-To: <CADtP98XqeKBw=T8__wbOprKUVkreAZGhPyrYuCcerYJj5zLuKQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On Wed, Sep 18, 2013 at 10:16:51AM +0200, Eugenio Carocci wrote:
> Thanks you for the reply, just one last question. Is there some paper
> online that explain, how the protocol
> avoid routing loop, may with some examples? :)

The document explaining something closer to what you want can be found on the
wiki: http://www.open-mesh.org/projects/batman-adv/wiki/OGM

However, the current implementation of the protocol is the result of a sort of
"evolution" and for this reason what you read in the document may not reflect
the current implementation 100% (but we always try to keep the two in sync).

Here[1] you also have an explanation of the former protocol, and some of the
things written there are still valid, but I'd use it only to get the flavour
of what is going on (not as a real reference).


Regards,


p.s. don't top-post please

-- 
Antonio Quartulli

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-09-18 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 22:55 [B.A.T.M.A.N.] Where can i see, sequence number, eq, rq for an originator? Eugenio Carocci
2013-09-18  6:19 ` Antonio Quartulli
2013-09-18  8:16   ` Eugenio Carocci
2013-09-18 10:08     ` Antonio Quartulli [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=20130918100848.GH3053@neomailbox.net \
    --to=antonio@meshcoding.com \
    --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