From: Jan Hetges <tran@ms20.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop
Date: Mon, 21 Apr 2008 14:30:02 -0600 [thread overview]
Message-ID: <20080421203002.GA4490@apoderado.ometepe.net> (raw)
In-Reply-To: <560c7c9a0804210557v2c94a553w5a2c8dd2efb8eead@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
On Mon, Apr 21, 2008 at 02:57:44PM +0200, Benjamin Henrion wrote:
> On Mon, Apr 21, 2008 at 2:39 PM, Jan Hetges <tran@ms20.net> wrote:
> > i'm running bmxd_rv972 for almost three months now, without
> > any mayor problems :-)... thanks.
> > what i recognized lately, on two nodes (the ones with more than
> > one bmx interface), show alternativeNextHops, which are *NO*
> > alternative. It seems there gets some 'information' lost between
> > the two IFs. I suppose that's a known issue ;-), any ideas how to
> > fix/workaround ? iirc, i saw once or twice a node "on the other
> > interface" even listed as the bestNextHop.
> >
> Can you describe a little more extensively your network configuration?
sorry ;-):
x.x.0.0/24---x.x.0.1/x.x.3.1---x.x.3.0/24---x.x.3.160/x.x.4.1---x.x.4.0/24
|
internet
batman network x.x.0.0/20.
.0.1/.3.1 is one node with two radios, and .3.160/.4.1 the other one.
and, .3.160/.4.1 lists .4.162 as alternativeNextHop to .3.128.
where .3.1 and .3.137 can see .3.128, but .4.162 can not. So, there is a real
alternativeNextHop to .3.128 ... .3.137, which is listed after .4.162
on .3.160/.4.1. I attach the output of bmxd -cbd8.
But after i really think through it, it shouldn't really matter,
because, if the connection between .3.160 and .3.1 gets interrupted,
.4.162 should probably fall back behind .3.137 in .3.160's statistic.
--Jan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-21 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 12:39 [B.A.T.M.A.N.] two radio nodes and alternative next hop Jan Hetges
2008-04-21 12:57 ` Benjamin Henrion
2008-04-21 20:30 ` Jan Hetges [this message]
2008-04-22 14:01 ` [B.A.T.M.A.N.] two-radio " Axel Neumann
2008-04-23 0:04 ` Jan Hetges
2008-04-23 7:54 ` Axel Neumann
2008-04-23 23:02 ` Jan Hetges
2008-04-24 7:33 ` Axel Neumann
2008-04-24 3:55 ` Jan Hetges
2008-04-24 8:09 ` Axel Neumann
2008-04-21 20:33 ` [B.A.T.M.A.N.] two radio " Jan Hetges
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=20080421203002.GA4490@apoderado.ometepe.net \
--to=tran@ms20.net \
--cc=b.a.t.m.a.n@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