Re: [B.A.T.M.A.N.] bridging problem

Walter Robert Ditzler
2012-06-05T22:16:07Z

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

hi sven,

thank you very much for your reply, in fact my email hasn't arrived as
wished!

attached i send you a pdf to have a look, if you dont mind, would be very
cool!

so what works:
1) lan to lan bridge (10.41.200.11 <> 10.41.200.12)

what i am too stupid to do:
1) attached wireless ad-hoc devices to give a dhcp lease
2) that ex. a attached laptop has a address 10.41.200.71 > bridged analogue
tot he base lan

so my question is:
1) do i need 2 wireless network card for each batman host?
2) can i connect tot he batman mesh essid to get access the base lan?

thank you very much for your time!

walter

-----Original Message-----
From: Sven Eckelmann [mailto:sven@narfation.org]
Sent: Dienstag, 5. Juni 2012 22:47
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Walter Robert Ditzler
Subject: Re: [B.A.T.M.A.N.] bridging problem

On Tuesday 05 June 2012 22:09:51 Walter Robert Ditzler wrote:
> hi batman list,
>
> i have problem setting up batman-adv "clients". i could need some help
> indeed.

Can you please describe "problems" a little bit more in detail.

> what i want
> **********
>
> | eth0 bat0(wlan0) | <mesh network> | bat(wlan0) eth0 | <ethernet>
>
> (backbone lan)
>
> | wlan0 (Client) |

I think this part was destroyed by your mail client.

> my questions:
> ***********
> 1) do i need 2 wifi network cards in the mp box to connect with
> wireless hosts (laptop's)?

No, many drivers can create VAPs (so you can easily have one VAP in master
mode and one in Adhoc mode)

> 2) if yes, how can i make the bridging to work form connected hosts
> (laptop's) and eth0?

I think this sentence could not be parsed by me. Do you want that mesh
unaware clients (here called laptopts) can connect through your mesh node's
eth0 interface to the mesh (and beyond)?

The answer to this question is given in the script you showed bellow. You
should just check that you don't create loops when attaching multiple
devices to a bridge.

> with what i work
> **************
> 1) alix2 boards
> 2) debian 6.0.5

Just as small info: hostapd on debian 6.0.5 has some problems with multissid
setups. Could be a problem when you start to experiment with VAPs

> 3) kernel 3.4 486
>
> what i did
> ********
> #!/bin/bash
>
> ifconfig eth0 down
> ifconfig wlan0 down
> ifconfig wlan1 down
>
> iw dev wlan0 del
> iw dev wlan1 del
>
> iw phy phy0 interface add mesh0 type adhoc ifconfig mesh0 mtu 1528
> iwconfig mesh0 mode ad-hoc essid adradix_mesh ap 02:12:34:56:78:9A
> channel 3
>
> batctl if add mesh0
>
> ifconfig mesh0 0.0.0.0 up
> ifconfig bat0 0.0.0.0 up
> ifconfig eth0 0.0.0.0 up
>
> brctl addbr br0
> brctl addif br0 bat0
> brctl addif br0 eth0
> ifconfig br0 10.10.10.11 netmask 255.255.255.0 up
>
> route add default gw 10.10.10.1
>
> exit 0;

I don't understand why you set ip addresses and routes here... but ok, i
will not stop you doing that.

Kind regards,
Sven

[-- Attachment #2: sven.pdf --]
[-- Type: application/pdf, Size: 79803 bytes --]