[B.A.T.M.A.N.] Problem after configuring a bridge

[B.A.T.M.A.N.] Problem after configuring a bridge

[Dr. Stefan Radtke]

Hello *,

I set up batman-adv-2010  on OpenWRT (backfire 10.3.x). Mesh interface  
is wlan0 and another non-batman-LAN is connected to eth0. non-batman 
clients should connect via the eth0 interface. (Full description and 
network diagram here: 
https://forum.openwrt.org/viewtopic.php?pid=129226#p129226 ).

After setting up batman-adv 2010.x with

batctl if add wlan0
ifconfig wlan 0 0.0.0.0
ifconfig bat0 192.168.10.2    (previous ip address of wlan0)
ifconfig bat0 up

I have to configure a bridge  (according to quick start guide 
http://www.open-mesh.org/wiki/batman-adv-quick-start-guide) because I 
want batman-adv to announce MAC-addresses connected to eth0 (see network 
diagram):

brctl addbr mesh-bridge
brctl addif mesh-bridge eth0
brctl addif mesh-bridge bat0
ifconfig eth0 up
ifconfig bat0 up
ifconfig mesh-bridge up


Although the translation tables (global and local) seem fine in this moment, at the same momentof bringing up the bridge I cannot send any more packets through bat0 or ent0.
Both don't even reply to a ping.

Network setup and outputs of ifconfig onhttp://www.open-mesh.org/wiki/batman-adv-quick-start-guide  

Any hint is appreciated.

Stefan

Re: [B.A.T.M.A.N.] Problem after configuring a bridge

[Antonio Quartulli]

Hello!

On mer, feb 23, 2011 at 08:45:03 +0100, Dr. Stefan Radtke wrote:
> I have to configure a bridge  (according to quick start guide 
> http://www.open-mesh.org/wiki/batman-adv-quick-start-guide) because I 
> want batman-adv to announce MAC-addresses connected to eth0 (see network 
> diagram):
> 
> brctl addbr mesh-bridge
> brctl addif mesh-bridge eth0
> brctl addif mesh-bridge bat0
> ifconfig eth0 up
> ifconfig bat0 up
> ifconfig mesh-bridge up

Did you also do
	ifconfig bat0 0.0.0.0 up
	ifconfig mesh-bridge 192.168.10.2 u
?
You have to remove the IP address from the real interface and add it to
the bridge one.

Regards

-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara

Re: [B.A.T.M.A.N.] Problem after configuring a bridge

[Sven Eckelmann]

[-- Attachment #1: Type: Text/Plain, Size: 3535 bytes --]

On Wednesday 23 February 2011 08:45:03 Dr. Stefan Radtke wrote:
> Hello *,
> 
> I set up batman-adv-2010  on OpenWRT (backfire 10.3.x). Mesh interface
> is wlan0 and another non-batman-LAN is connected to eth0. non-batman
> clients should connect via the eth0 interface. (Full description and
> network diagram here:
> https://forum.openwrt.org/viewtopic.php?pid=129226#p129226 ).

entX == ethX? You should set the mtu of wlan0 to 1530 and all other mtus (br0, 
bat0, eth0, ...) to 1500. I would also recommend to update to batman-adv 
v2011.0.0. None of the mentioned should fix you problem, but are recommended 
to fix other glitches.

You don't tell us what sending means in you initial description - which 
card/node wants to sent to which other card/node. What he wants to send? What 
did your sensors (tcpdump, batctl td, ...) tell you how far those packets 
travel through the mesh/lan? I would recommend to test the functionality of 
layer two with a layer two protocol - or test application. A good idea is to 
use raw l2 sockets to send some packets from A to B and check if it arrives 
[1].

> After setting up batman-adv 2010.x with
> 
> batctl if add wlan0
> ifconfig wlan 0 0.0.0.0
> ifconfig bat0 192.168.10.2    (previous ip address of wlan0)
> ifconfig bat0 up
> 
> I have to configure a bridge  (according to quick start guide
> http://www.open-mesh.org/wiki/batman-adv-quick-start-guide) because I
> want batman-adv to announce MAC-addresses connected to eth0 (see network
> diagram):
> 
> brctl addbr mesh-bridge
> brctl addif mesh-bridge eth0
> brctl addif mesh-bridge bat0
> ifconfig eth0 up
> ifconfig bat0 up
> ifconfig mesh-bridge up

As Floh1111 already said, this IP setup cannot work. Here a little bit more 
information about that:

You set an ip to bat0 and then add the bat0 to br0 - this cannot work. The 
bridge will prevent packets from being received through bat0. All packets of 
attached interfaces will be received through br0. The tcp/ip stack will simply 
drop the packet when the bridge isn't configured to receive for that ip. This 
behavior can be changed slightly using ebtables broute - but I would strongly 
recommend not to mess with that stuff.

Best way is to either setup IP routing or use IPs only on br0 (and br0:0 for 
the second IP). You should also check your routing table for invalid entries 
after you replaced the IPs. 

> Although the translation tables (global and local) seem fine in this
> moment, at the same momentof bringing up the bridge I cannot send any more
> packets through bat0 or ent0. Both don't even reply to a ping.
> 
> Network setup and outputs of ifconfig
> onhttp://www.open-mesh.org/wiki/batman-adv-quick-start-guide
> 
> Any hint is appreciated.

Please first try to bisect your setup on layer 2 for clients which have a 
direct link (switched or switched over mesh, but not routed). Use tcpdump and 
"batctl td" to detect where packets may get dropped. In case no problem was 
found, please continue to do the same on l3. But keep in mind that eth0/bat0 
will not received packets for the host directly - br0 is the interface you 
want to use.

What exactly are you trying to achieve using the IP in the wrong physical 
subnet thing? There are better tunneling protocols for that purpose and you 
don't need use some weird bridging-routing-in-parallel-something-monster.

Best regards,
	Sven

[1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2010-January/002234.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [B.A.T.M.A.N.] Problem after configuring a bridge

[Dr. Stefan Radtke]

Hello Antonio, Sven,

thanks for your comments. With your help I could set it up. The mistake 
was in fact the ip-address on bat0.

I removed all IP addresses and set them to the bridge. That worked !

For those who might run into the same problem, here is the correct setup:
http://www.radtke.eu/tmp/Leitzberg-Mesh-corrected.gif

But a question is remaining: once the mesh was running, I wanted to turn 
on enrcyption but this seems not working in ad-hoc mode with OpenWRT . 
If I select Access Point mode for wlan0 the WPA2 encryption works....but 
this is not supported with batman-adv since the wifis need to run in 
ad-hoc mode. Any hint for this if I want to run the mesh encrypted ?

P.D. Same happens if I run IEEE 802.11s mode (without batman-adv). Works 
well but encryption setting doesn't work.

Best regards, Stefan





On 23.02.2011 08:45, Dr. Stefan Radtke wrote:
> Hello *,
>
> I set up batman-adv-2010  on OpenWRT (backfire 10.3.x). Mesh 
> interface  is wlan0 and another non-batman-LAN is connected to eth0. 
> non-batman clients should connect via the eth0 interface. (Full 
> description and network diagram here: 
> https://forum.openwrt.org/viewtopic.php?pid=129226#p129226 ).
>
> After setting up batman-adv 2010.x with
>
> batctl if add wlan0
> ifconfig wlan 0 0.0.0.0
> ifconfig bat0 192.168.10.2    (previous ip address of wlan0)
> ifconfig bat0 up
>
> I have to configure a bridge  (according to quick start guide 
> http://www.open-mesh.org/wiki/batman-adv-quick-start-guide) because I 
> want batman-adv to announce MAC-addresses connected to eth0 (see 
> network diagram):
>
> brctl addbr mesh-bridge
> brctl addif mesh-bridge eth0
> brctl addif mesh-bridge bat0
> ifconfig eth0 up
> ifconfig bat0 up
> ifconfig mesh-bridge up
>
>
> Although the translation tables (global and local) seem fine in this 
> moment, at the same momentof bringing up the bridge I cannot send any 
> more packets through bat0 or ent0.
> Both don't even reply to a ping.
>
> Network setup and outputs of ifconfig 
> onhttp://www.open-mesh.org/wiki/batman-adv-quick-start-guide
> Any hint is appreciated.
>
> Stefan
>
>
>

Re: [B.A.T.M.A.N.] Problem after configuring a bridge

[Sven Eckelmann]

[-- Attachment #1: Type: Text/Plain, Size: 1326 bytes --]

On Wednesday 23 February 2011 18:42:58 Dr. Stefan Radtke wrote:
> Hello Antonio, Sven,
> 
> thanks for your comments. With your help I could set it up. The mistake
> was in fact the ip-address on bat0.
> 
> I removed all IP addresses and set them to the bridge. That worked !
> 
> For those who might run into the same problem, here is the correct setup:
> http://www.radtke.eu/tmp/Leitzberg-Mesh-corrected.gif

I've noticed two IPs for br0:0 in node1 but no for br0 - is this correct?

> But a question is remaining: once the mesh was running, I wanted to turn
> on enrcyption but this seems not working in ad-hoc mode with OpenWRT .
> If I select Access Point mode for wlan0 the WPA2 encryption works....but
> this is not supported with batman-adv since the wifis need to run in
> ad-hoc mode. Any hint for this if I want to run the mesh encrypted ?

This is wrong. batman-adv doesn't need a network which is setup in adhoc mode. 
It only needs a layer which has roughly the characteristics of ethernet (frame 
header, broadcast/multicast addresses, ...).

If you want some kind of encryption in adhoc mode as part of the wifi layer 
then please try WPA_NONE or similar protocols. Authorisation, authentication 
and encryption in higher layers are still highly recommended.

Best regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]