Re: [B.A.T.M.A.N.] Can't create new originator

["puyou.lu" <puyou.lu@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2778 bytes --]

Hi, Marek.
Every nodes run the same version of batman.
I attatch the topology of my mesh network.When b0:c6:9b:80:01:53 is on (working),b0:c6:9b:80:01:5f can reach b0:c6:9b:80:01:43,and the hole network is ok.b0:c6:9b:80:01:5b's nexthop to b0:c6:9b:80:01:43 is b0:c6:9b:80:01:57 or b0:c6:9b:80:01:6c, and sometimes b0:c6:9b:80:01:53.
But when I shut b0:c6:9b:80:01:53 down,it seems b0:c6:9b:80:01:5b can't reach b0:c6:9b:80:01:57 neither b0:c6:9b:80:01:6c,as I mentioned in my firt email.
When I turn b0:c6:9b:80:01:53 on again,the hole mesh is ok again.
Marek,can you tell me what the problem probably is.


> -----Original Message-----
> From: Marek Lindner [mailto:lindner_marek@yahoo.de]
> Sent: Saturday, May 26, 2012 10:55 PM
> To: b.a.t.m.a.n@lists.open-mesh.org
> Cc: puyou.lu
> Subject: Re: [B.A.T.M.A.N.] Can't create new originator
> 
> 
> Hi,
> 
> 
> > I saw strange batman logs while testing a batman-adv mesh. Batman-adv
> > module was continuously generating the same logs including a " Creating
> > new originator: b0:c6:9b:80:01:43". But b0:c6:9b:80:01:43 never appears in
> > the output of 'batctl o': admin@HND-Mesh:~# batctl o
> > [B.A.T.M.A.N. adv 2012.0.0, MainIF/MAC: wlan0/b0:c6:9b:80:01:5b (bat0)]
> >   Originator      last-seen (#/255)           Nexthop
> > [outgoingIF]:   Potential nexthops ... b0:c6:9b:80:01:5c    0.010s   (255)
> > b0:c6:9b:80:01:5c [     wlan0]: b0:c6:9b:80:01:5f (209) b0:c6:9b:80:01:6b
> > (231) b0:c6:9b:80:01:6b (227) b0:c6:9b:80:01:5c (255) b0:c6:9b:80:01:5c
> > (  0) b0:c6:9b:80:01:45    3.830s   (223) b0:c6:9b:80:01:5f [     wlan0]:
> > b0:c6:9b:80:01:5c (209) b0:c6:9b:80:01:6b (  0) b0:c6:9b:80:01:6b (  0)
> > b0:c6:9b:80:01:5f (223) b0:c6:9b:80:01:6b    4.520s   (255)
> > b0:c6:9b:80:01:6b [     wlan0]: b0:c6:9b:80:01:5f (206) b0:c6:9b:80:01:5c
> > (245) b0:c6:9b:80:01:6b (255) b0:c6:9b:80:01:6b (251)
> > b0:c6:9b:80:01:3b    1.570s   (237) b0:c6:9b:80:01:5f [     wlan0]:
> > b0:c6:9b:80:01:5c (226) b0:c6:9b:80:01:6b (  0) b0:c6:9b:80:01:6b (  0)
> > b0:c6:9b:80:01:5f (237) b0:c6:9b:80:01:5f    3.520s   (255)
> > b0:c6:9b:80:01:5f [     wlan0]: b0:c6:9b:80:01:6b (231) b0:c6:9b:80:01:6b
> > (227) b0:c6:9b:80:01:5c (244) b0:c6:9b:80:01:5f (255)
> >
> > Now I can nerver reach b0:c6:9b:80:01:43. Anyone tell me why this happens?
> 
> according to your logs OGMs from b0:c6:9b:80:01:43 are received via nodes that
> are not in your routing table either:
>  * b0:c6:9b:80:01:57
>  * b0:c6:9b:80:01:6c
> 
> Therefore you see the warning: Drop packet: OGM via unknown neighbor!
> Batman-adv can't create a route to a an originator without having a next hop.
> 
> Do all nodes in your network run the same batman-adv version (2012.0.0) ?
> 
> Regards,
> Marek

[-- Attachment #2: t.PNG --]
[-- Type: image/png, Size: 11721 bytes --]