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

Sven Eckelmann
2012-06-06T06:59:00Z

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

On Wednesday 06 June 2012 00:16:07 Walter Robert Ditzler wrote:
> 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

You need another vap/vif [1] adhoc device to serve such devices. This one
would have to run in 4addr mode to be able to get bridged. Usually you don't
do this because the client also needs to understand the 4addr mode. Therefore,
just create a master mode vap/vif and attach it to the bridge (you get it into
master mode using hostapd... please keep in mind that squeeze's hostapd is
buggy and maybe has problems with that setup).

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

Not really. It could be a good idea to run the mesh on another frequency and
use another wlan device for this.

But the basic setup is really to create two interfaces (VAPs) for phy0 using
iw. One is added to bat0 (the adhoc one) and the other one (managed) is
transformed using hostapd in an master mode/AP interface and added to the same
bridge.

> 2) can i connect tot he batman mesh essid to get access the base lan?

Using non mesh aware clients? No.

batman-adv is a layer on top of the adhoc layer and clients that don't
understand batman-adv cannot decode this extra layer information.

Kind regards,
Sven

[1] http://linuxwireless.org/en/users/Documentation/iw/vif/

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