Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop

Jan Hetges
2008-04-21T20:30:02Z

[-- 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