public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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.] Possible OGM forwarding misbehavior
Date: Mon, 14 May 2012 17:15:27 +0800	[thread overview]
Message-ID: <201205141715.27604.lindner_marek@yahoo.de> (raw)
In-Reply-To: <CAG7VhQQKKv67Qb4ywQmJp7BCvJARRYT29AwBX1rQDgidaCP5iQ@mail.gmail.com>


Hi,

> incidentally I noticed that with the modification that introduced the
> 'NOT_BEST_NEXT_HOP' flag only OGM coming from best next hop neighbour
> are forwarded in case of multi-hop originators.
> 
> The problem is that in the routing code it is forwarded only the first OGM
> received with a fresh sequence number (that could be received from a
> sub-optimal router).
> 
> This means that if the OGM from best next hop neighbour is not received as
> the first OGM, it is not forwarded and I think this can be a problem.
> 
> Maybe it can be better to maintain also an index of the last FORWARDED
> sequence number instead of checking the last RECEIVED sequence number.

do you mind sending a patch for this ? That would make it easier to understand 
what you have in mind.

Regards,
Marek
 

      reply	other threads:[~2012-05-14  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAG7VhQSjyQRtCZfC9FUr1f+Fxg6mdwFfBJZOyXowhmW7r+a-eA@mail.gmail.com>
2012-05-13  8:56 ` [B.A.T.M.A.N.] Possible OGM forwarding misbehavior Daniele Furlan
2012-05-14  9:15   ` Marek Lindner [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=201205141715.27604.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