Re: [B.A.T.M.A.N.] Can't create new originator
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_ma...@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:5c0.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:453.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:6b4.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:3b1.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:5f3.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: t.PNG
Re: [B.A.T.M.A.N.] Problem with multi-radio, multi-channel in batman-adv
Hi Simon, I have tried again, and I think the problem is caused by the same ESSID, as you said. I used the same ESSID on every wireless cards of every nodes.When I use different ESSIDs in different channel, the problem seems diappeared. Another question, does the two wireless cards(wlan0 and wlan1) of one node have any differences in receiving and forwarding unicast and broadcast package? Can a gw_client node get IP address from a dhcp server from both wireless cards? -Original Message- From: b.a.t.m.a.n-boun...@lists.open-mesh.org [mailto:b.a.t.m.a.n-boun...@lists.open-mesh.org] On Behalf Of Simon Wunderlich Sent: Tuesday, April 17, 2012 5:26 PM To: The list for a Better Approach To Mobile Ad-hoc Networking Subject: Re: [B.A.T.M.A.N.] Problem with multi-radio, multi-channel in batman-adv Hey Puyou, On Mon, Apr 16, 2012 at 06:35:04PM +0800, puyou.lu wrote: Hi guys. I’m trying to make a for nodes WMN using four devices with two wireless cards each. I would like to use three different channels to reduce the interference, like this: [Node A] - channel 1 - [Node B] - channel 2 - [Node C] - channel 3 - [Node D] First I configure eight wireless cards to the specific channel in ad-hoc mode using “iw dev wlan0 ibss join …”. Then, I think I should add wlan0 and wlan1 to the same batman-adv interface (that is bat0) in every device. So I need to configure four nodes with the same commands like: echo bat0 /sys/class/net/wlan0/batman_adv/mesh_iface echo bat0 /sys/class/net/wlan1/batman_adv/mesh_iface Last configure an IP address to each bat0. (Node A-10.0.0.1, Node B-10.0.0.2, Node C-10.0.0.3, Node D-10.0.0.4). But it seem Node A can reach Node B and Node C(using ping), but can’ t for Node D. Am I following the right procedure? Sorry for my poor English. Any help would be appreciated. The procedure looks right in general. A few questions to debug: * do you use different ESSIDs for the IBSS-networks? ad-hoc devices joining may override the configured channel and select another IBSS-network instead when it has the same ESSID. * have you confirmed that the WiFi connection works without batman-adv? just set up your WiFi, configure different IP addresses and ping for each hop to test. * does the output of batctl originators helps you? Are the other nodes displayed on node 4? Cheers, Simon
[B.A.T.M.A.N.] Problem with multi-radio, multi-channel in batman-adv
Hi guys. I’m trying to make a for nodes WMN using four devices with two wireless cards each. I would like to use three different channels to reduce the interference, like this: [Node A] - channel 1 - [Node B] - channel 2 - [Node C] - channel 3 - [Node D] First I configure eight wireless cards to the specific channel in ad-hoc mode using “iw dev wlan0 ibss join …”. Then, I think I should add wlan0 and wlan1 to the same batman-adv interface (that is bat0) in every device. So I need to configure four nodes with the same commands like: echo bat0 /sys/class/net/wlan0/batman_adv/mesh_iface echo bat0 /sys/class/net/wlan1/batman_adv/mesh_iface Last configure an IP address to each bat0. (Node A-10.0.0.1, Node B-10.0.0.2, Node C-10.0.0.3, Node D-10.0.0.4). But it seem Node A can reach Node B and Node C(using ping), but can’t for Node D. Am I following the right procedure? Sorry for my poor English. Any help would be appreciated. Puyou Lu.
