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.net>
Subject: Re: [B.A.T.M.A.N.] batman goes looping...
Date: Mon, 10 Aug 2009 15:48:40 +0800	[thread overview]
Message-ID: <200908101548.53459.lindner_marek@yahoo.de> (raw)
In-Reply-To: <OF6771C76D.6C69E95B-ONC125760E.002641B8-C125760E.0028535B@CHASCOM.INT>

On Monday 10 August 2009 15:20:28 Yang Su wrote:
> For the echo cancellation example: the problem happens with the interaction
> between A and B. Because of the asym link, A chooses B as its next neighbor
> towards F. Because the asym path is short, B always receives F's OGM from A
> first  (before B receives the OGM with the same seqno from C). As a result,
> from A's point of view, F's OGMs rebroadcasted by B are always echoes and A
> will never update the TQ information towards F via B.
>
> When the quality of any links on the path B to F drops down, B might choose
> A as its next neighbor towards F and a loop forms between A and B.

Ah, here we have the misunderstanding. Let me briefly outline how the echo 
cancellation works (I refer to your PDF-example):

1. Node C emits a packet.
2. Node B receives it and writes the address of Node C in the previous sender 
field because it received that packet via C. Now, B rebroadcasts the OGM.
3. Node C receives the packet it sent before and discards it as the packet 
contains its own address in the previous sender field.
4. Node A happily receives the packet (and goes back to step 2).

The echo cancellation will not kill the packets coming via the longer path. 

Does this help ? 

Regards,
Marek


  reply	other threads:[~2009-08-10  7:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 10:56 [B.A.T.M.A.N.] batman goes looping Andrew Lunn
2009-07-27 16:20 ` Marek Lindner
2009-07-30 14:32   ` Yang Su
2009-08-03 10:21     ` Marek Lindner
2009-08-04 15:59       ` [B.A.T.M.A.N.] Routing help? nick farrow
2009-08-06  8:44       ` [B.A.T.M.A.N.] batman goes looping Yang Su
2009-08-06 14:15         ` Marek Lindner
2009-08-07 15:13           ` Yang Su
2009-08-07 15:58             ` Marek Lindner
2009-08-10  7:20               ` Yang Su
2009-08-10  7:48                 ` Marek Lindner [this message]
2009-08-10  7:57                   ` Yang Su
2009-08-10  8:16                     ` Marek Lindner
2009-08-11 16:42                       ` Marek Lindner
2009-08-12 14:34                         ` Yang Su
2009-08-13  9:56                           ` Marek Lindner
2009-08-13 15:07                             ` Yang Su
2009-08-13 16:00                               ` Marek Lindner

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=200908101548.53459.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    /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