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: Fri, 14 Aug 2009 00:00:29 +0800 [thread overview]
Message-ID: <200908140000.30125.lindner_marek@yahoo.de> (raw)
In-Reply-To: <OFB71ACC02.50DE5AF7-ONC1257611.0052A304-C1257611.00530C28@CHASCOM.INT>
On Thursday 13 August 2009 23:07:06 Yang Su wrote:
> Maybe I miss some thing here. What do you think would prevent A from
> choosing via the long route (via B) ?
The starting point (still using your example):
* A points to E as it never learned about the long path.
* B points to C because it learned about the long path but does not
rebroadcast the packets from C because they are slower than the
packets via A.
* C uses the longer path.
Your idea: Use the echo cancellation's answer to retrieve more information,
especially when the TQ which is coming back is worse than my own I update my
routing information.
The situation now:
* A still points to E because the echos coming from B do not contain TQ values
that are worse than its own.
* B will probably never route via A because the TQ values are much worse.
* C is not affected.
Did I overlook something ?
Regards,
Marek
prev parent reply other threads:[~2009-08-13 16:00 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
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 [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=200908140000.30125.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.