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

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

[Walter Robert Ditzler]

hi batman list,

i have problem setting up batman-adv "clients". i could need some help
indeed.

thank you very much for replying!

walter


what i want
**********

| eth0  bat0(wlan0) | <mesh network> | bat(wlan0) eth0 |  <ethernet>
(backbone lan)


| wlan0 (Client)       |

my questions:
***********
1) do i need 2 wifi network cards in the mp box to connect with wireless
hosts (laptop's)?
2) if yes, how can i make the bridging to work form connected hosts
(laptop's) and eth0?

with what i work
**************
1) alix2 boards
2) debian 6.0.5
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;

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

[Sven Eckelmann]

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

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: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

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

[Walter Robert Ditzler]

[-- 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 --]

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

[Antonio Quartulli]

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

Hello Walter,

On Wed, Jun 06, 2012 at 12:16:07AM +0200, Walter Robert Ditzler wrote:
> so my question is:
> 1) do i need 2 wireless network card for each batman host?

This would probably be the best choice, but it is not always possible. Like in
your case, your box has only one wlan device.
What you can do is to create more VIF. Each wireless device is represented by a
phy interface (phy0 in your case) and on top of it you can create more than one
Virtual Interface (VIF). Actually, when you issued the command:

iw phy phy0 interface add mesh0 type adhoc

you are creating a VAP named mesh0 on top of phy0. What you could do to achieve
your goal (and what we usually d in the same scenario) is to create another VIF
which will be used as AccessPoint interface.

At that point you will have 
- mesh0, that will be put in bat0
- ap0 (or whatever the name you chose)

Now I think you know what to do :-) You can bridge bat0 and ap0!

Here is a link that explains how it works:
http://linuxwireless.org/en/users/Documentation/iw/vif/


Cheers,

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

You want to use ap0 at this point.


-- 
Antonio Quartulli

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

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

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

[Sven Eckelmann]

[-- 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 --]

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

[Walter Robert Ditzler]

hi sven,
hi antonio,

thanks a lot for your explanations which helped me finally to understand the
concept. it is that actually what i thought it should be, a transparent
layer 2 thing.

i mean i thought so, it must be possible to serve AP within 1 wireless nic
only! netherthenless i haven't succed to get it run.

But as sven mentioned that could and i beleive it must be a
hostapd/squeeze6.0.5 problem since my ethernet nic's onto the batman mesh
works perfectly.

only this thing with the bridging networks from the wlan's.

thanks walter.

(with madwifi)
***
root@srv-ldeb-basic1:/etc/hostapd# hostapd hostapd.conf
Configuration file: hostapd.conf
ioctl[SIOCSIWMODE]: Invalid argument
Could not set interface to master mode!
madwifi driver initialization failed.
ELOOP: remaining socket: sock=5 eloop_data=0x9f8baf0 user_data=(nil)
handler=0x8086f00
root@srv-ldeb-basic1:/etc/hostapd#
***

(with nl80211)
***
root@srv-ldeb-basic1:/etc/hostapd# hostapd hostapd.conf
Configuration file: hostapd.conf
ioctl[SIOCSIFFLAGS]: Name not unique on network
nl80211 driver initialization failed.
ELOOP: remaining socket: sock=5 eloop_data=0x9141a30 user_data=(nil)
handler=0x80863e0
root@srv-ldeb-basic1:/etc/hostapd#
***

hostapd.conf
***
interface=wlan0
bridge=br0
driver=nl80211 / madwifi
ssid=moses_test
channel=1
hw_mode=g
ieee80211n=1
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=123456123456123456123456
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
***

***
root@srv-ldeb-basic1:/etc/hostapd# iwconfig
gre0      no wireless extensions.

br0       no wireless extensions.

wlan0     IEEE 802.11abg  Mode:Master  Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

bat0      no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

mesh0     IEEE 802.11abg  ESSID:"adradix_mesh"
          Mode:Ad-Hoc  Frequency:2.427 GHz  Cell: 02:12:34:56:78:9A
          Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on

tunl0     no wireless extensions.

root@srv-ldeb-basic1:/etc/hostapd#
***




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

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/

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

[Sven Eckelmann]

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

On Wednesday 06 June 2012 14:26:12 Walter Robert Ditzler wrote:
> 
> (with nl80211)
> ***
> root@srv-ldeb-basic1:/etc/hostapd# hostapd hostapd.conf
> Configuration file: hostapd.conf
> ioctl[SIOCSIFFLAGS]: Name not unique on network
> nl80211 driver initialization failed.
> ELOOP: remaining socket: sock=5 eloop_data=0x9141a30 user_data=(nil)
> handler=0x80863e0
> root@srv-ldeb-basic1:/etc/hostapd#
> ***


You must make sure that each Vif/VAP device has a different mac address.

sudo ifconfig wlan0 down hw ether 02:34:56:78:9a:bc up

Kind regards,
	Sven

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

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

[Walter Robert Ditzler]

sven,

root@srv-ldeb-basic1:/etc/hostapd# ifconfig wlan0 down hw ether
02:34:56:78:9a:bc up
SIOCSIFFLAGS: Link number out of range
root@srv-ldeb-basic1:/etc/hostapd#

cheers walter



-----Original Message-----
From: Sven Eckelmann [mailto:sven@narfation.org] 
Sent: Mittwoch, 6. Juni 2012 14:38
To: Walter Robert Ditzler
Cc: 'Antonio Quartulli'; b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] bridging problem

On Wednesday 06 June 2012 14:26:12 Walter Robert Ditzler wrote:
> 
> (with nl80211)
> ***
> root@srv-ldeb-basic1:/etc/hostapd# hostapd hostapd.conf Configuration 
> file: hostapd.conf
> ioctl[SIOCSIFFLAGS]: Name not unique on network
> nl80211 driver initialization failed.
> ELOOP: remaining socket: sock=5 eloop_data=0x9141a30 user_data=(nil)
> handler=0x80863e0
> root@srv-ldeb-basic1:/etc/hostapd#
> ***


You must make sure that each Vif/VAP device has a different mac address.

sudo ifconfig wlan0 down hw ether 02:34:56:78:9a:bc up

Kind regards,
	Sven

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

[Wayne Abroue]

On Wed, Jun 6, 2012 at 2:59 PM, Walter Robert Ditzler
<ditwal001@gmail.com> wrote:
> sven,
>
> root@srv-ldeb-basic1:/etc/hostapd# ifconfig wlan0 down hw ether
> 02:34:56:78:9a:bc up
> SIOCSIFFLAGS: Link number out of range
> root@srv-ldeb-basic1:/etc/hostapd#
>
> cheers walter
>
>
>
> -----Original Message-----
> From: Sven Eckelmann [mailto:sven@narfation.org]
> Sent: Mittwoch, 6. Juni 2012 14:38
> To: Walter Robert Ditzler
> Cc: 'Antonio Quartulli'; b.a.t.m.a.n@lists.open-mesh.org
> Subject: Re: [B.A.T.M.A.N.] bridging problem
>
> On Wednesday 06 June 2012 14:26:12 Walter Robert Ditzler wrote:
>>
>> (with nl80211)
>> ***
>> root@srv-ldeb-basic1:/etc/hostapd# hostapd hostapd.conf Configuration
>> file: hostapd.conf
>> ioctl[SIOCSIFFLAGS]: Name not unique on network
>> nl80211 driver initialization failed.
>> ELOOP: remaining socket: sock=5 eloop_data=0x9141a30 user_data=(nil)
>> handler=0x80863e0
>> root@srv-ldeb-basic1:/etc/hostapd#
>> ***
>
>
> You must make sure that each Vif/VAP device has a different mac address.
>
> sudo ifconfig wlan0 down hw ether 02:34:56:78:9a:bc up
>
> Kind regards,
>        Sven

Hi Walter

Is it possible to run two drivers at the same time on hostapd?

driver=nl80211 / madwifi

Should be one or the other IIRC.

Wayne

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

[Sven Eckelmann]

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

On Wednesday 06 June 2012 14:59:32 Walter Robert Ditzler wrote:
> sven,
> 
> root@srv-ldeb-basic1:/etc/hostapd# ifconfig wlan0 down hw ether
> 02:34:56:78:9a:bc up
> SIOCSIFFLAGS: Link number out of range
> root@srv-ldeb-basic1:/etc/hostapd#

Ok, this confuses me slightly can you just try to change the mesh0 hwaddr to 
wlan0 + 1?

Kind regards,
	Sven

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

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

[Sven Eckelmann]

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

On Wednesday 06 June 2012 18:13:57 Walter Robert Ditzler wrote:
> hi sven,
> 
> just not to mix many things my procedure bellow. i could change the mac of
> my mesh0
> but i saw that there is a problem to bring up wlan0!

The problem is that you have to change the mac of mesh0 before bringing up 
wlan0. Actually you should change it directly after creating it and before 
doing anything else. So somewhere between `iw phy phy0 interface add mesh0 
type adhoc` and `ifconfig mesh0 mtu 1528`

Kind regards,
	Sven

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

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

[Sven Eckelmann]

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

On Monday 11 June 2012 15:49:24 Walter Robert Ditzler wrote:
> hi sven,
> 
> as promised my final report :-)
> 
> at the end only one question has left, but it is hardware wifi related. i
> have several alix hardware boxes, now all with double ath5 wlan cards.
> strange is sometimes when i create the vif (iw phy phy1) becomes the wlan 0
> and sometimes wlan1. any glue on that?

Sounds a little bit like udev is renaming the device even when you told iw how 
the device should be named (see persistent net settings).

http://www.ducea.com/2008/09/01/remove-debian-udev-persistent-net-rules/

Kind regards,
	Sven

Just for the other people:
> ***
> as you mentioned hostapd and ath5 are very buggy! under debian i only could
> get it to run under following conditions:
> 
> 1) system related
> ***************
> add to apt source list:
> deb http://backports.debian.org/debian-backports squeeze-backports main
> 
> install hostapd from:
> DEBIAN_FRONTEND=noninteractive aptitude -y install -t squeeze-backports
> batctl hostapd
> 
> (hostapd >= 0.6.10)
> 
> kernel:
> ***
> root@srv-ldeb-basic1:/etc/hostapd# cat /boot/config-3.4.0-adx-alix |grep
> "80211"
> CONFIG_CFG80211=m
> CONFIG_NL80211_TESTMODE=y
> CONFIG_CFG80211_DEVELOPER_WARNINGS=y
> CONFIG_CFG80211_REG_DEBUG=y
> CONFIG_CFG80211_DEFAULT_PS=y
> CONFIG_CFG80211_DEBUGFS=y
> CONFIG_CFG80211_INTERNAL_REGDB=y
> CONFIG_CFG80211_WEXT=y
> CONFIG_LIB80211=m
> CONFIG_LIB80211_CRYPT_WEP=m
> CONFIG_LIB80211_CRYPT_CCMP=m
> CONFIG_LIB80211_CRYPT_TKIP=m
> CONFIG_LIB80211_DEBUG=y
> CONFIG_MAC80211=m
> CONFIG_MAC80211_HAS_RC=y
> CONFIG_MAC80211_RC_PID=y
> CONFIG_MAC80211_RC_MINSTREL=y
> CONFIG_MAC80211_RC_MINSTREL_HT=y
> # CONFIG_MAC80211_RC_DEFAULT_PID is not set
> CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
> CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
> CONFIG_MAC80211_MESH=y
> CONFIG_MAC80211_LEDS=y
> CONFIG_MAC80211_DEBUGFS=y
> CONFIG_MAC80211_DEBUG_MENU=y
> CONFIG_MAC80211_NOINLINE=y
> CONFIG_MAC80211_VERBOSE_DEBUG=y
> CONFIG_MAC80211_HT_DEBUG=y
> CONFIG_MAC80211_TKIP_DEBUG=y
> CONFIG_MAC80211_IBSS_DEBUG=y
> CONFIG_MAC80211_VERBOSE_PS_DEBUG=y
> CONFIG_MAC80211_VERBOSE_MPL_DEBUG=y
> CONFIG_MAC80211_VERBOSE_MPATH_DEBUG=y
> CONFIG_MAC80211_VERBOSE_MHWMP_DEBUG=y
> CONFIG_MAC80211_VERBOSE_TDLS_DEBUG=y
> CONFIG_MAC80211_DEBUG_COUNTERS=y
> CONFIG_MAC80211_HWSIM=m
> ***
> 
> 2) wifi related
> ************
> - ath5 only supports 1 adhoc vif
> - ath5 can't run in master mode without hostapd
> - ath5 bridging and mesh only possible with 2 wlan cards
> - ath9 no problems at all
> - ath9 bridging and mesh with one wlan card possible
> 
> !!! attention !!!
> 
> when using ath5 wlan cards hostapd service hast o be restared. only after
> restarting the hostapd service you will be able to link second wlan ath5
> card into the bridge br0. i tried many thing but this ist he only way i
> succeeded.
> 
> 
> 
> *** (/etc/hostapd/hostapd,.conf can be also an adhoc vif)
> interface=wlan1
> bridge=br0
> driver=nl80211
> hw_mode=g
> channel=1
> ssid=adradix_test
> macaddr_acl=0
> auth_algs=1
> ignore_broadcast_ssid=0
> wpa=2
> wpa_passphrase=xxx
> wpa_key_mgmt=WPA-PSK
> wpa_pairwise=TKIP
> rsn_pairwise=CCMP
> ***
> 
> *** (network script > of course no need to use static ip's also dhcp
> possible)
> #!/bin/bash
> 
> # ADRADIX MODIFIED AT 2012-06-09 23:51:24
> #
> echo "1" > /proc/sys/net/ipv4/ip_forward
> 
> ifconfig eth0 down
> ifconfig wlan0 down
> ifconfig wlan1 down
> ifconfig mesh0 down
> ifconfig bat0 down
> ifconfig br0 down
> 
> brctl delbr br0
> batctl if del mesh0
> 
> iw dev wlan0 del
> iw dev wlan1 del
> iw dev mesh0 del
> iw dev mon.wlan0 del
> iw dev mon.wlan1 del
> 
> iw phy phy0 interface add mesh0 type adhoc
> ifconfig mesh0 mtu 1528
> iwconfig mesh0 mode ad-hoc essid adradix_mesh ap xx:xx:xx:xx:xx:xx channel
> 10
> batctl if add mesh0
> ifconfig mesh0 0.0.0.0 up
> 
> iw phy phy1 interface add wlan1 type adhoc
> 
> brctl addbr br0
> brctl addif br0 eth0
> brctl addif br0 bat0
> 
> ifconfig bat0 0.0.0.0 up
> ifconfig eth0 0.0.0.0 up
> ifconfig br0 10.xx.xx.xx netmask 255.255.255.0 up
> 
> route add default gw 10.41.20.1
> 
> #echo "1" > /proc/sys/net/ipv4/conf/mesh0/proxy_arp
> #echo "1" > /proc/sys/net/ipv4/conf/bat0/proxy_arp
> #echo "1" > /proc/sys/net/ipv4/conf/br0/proxy_arp
> #echo "1" > /proc/sys/net/ipv4/conf/eth0/proxy_arp
> 
> #
> # IMPORTANT: WITHOUT THAT RESTART BRIDGING DOES NOT WORK
> /etc/init.d/hostapd restart
> brctl addif br0 wlan1
> 
> exit 0;
> ***

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

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

[Walter Robert Ditzler]

hi sven,

thanks, i am too long on the same problem, of course it was the udev!

cheers walter

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

On Monday 11 June 2012 15:49:24 Walter Robert Ditzler wrote:
> hi sven,
> 
> as promised my final report :-)
> 
> at the end only one question has left, but it is hardware wifi 
> related. i have several alix hardware boxes, now all with double ath5 wlan
cards.
> strange is sometimes when i create the vif (iw phy phy1) becomes the 
> wlan 0 and sometimes wlan1. any glue on that?

Sounds a little bit like udev is renaming the device even when you told iw
how the device should be named (see persistent net settings).

http://www.ducea.com/2008/09/01/remove-debian-udev-persistent-net-rules/

Kind regards,
	Sven

Just for the other people:
> ***
> as you mentioned hostapd and ath5 are very buggy! under debian i only 
> could get it to run under following conditions:
> 
> 1) system related
> ***************
> add to apt source list:
> deb http://backports.debian.org/debian-backports squeeze-backports 
> main
> 
> install hostapd from:
> DEBIAN_FRONTEND=noninteractive aptitude -y install -t 
> squeeze-backports batctl hostapd
> 
> (hostapd >= 0.6.10)
> 
> kernel:
> ***
> root@srv-ldeb-basic1:/etc/hostapd# cat /boot/config-3.4.0-adx-alix 
> |grep "80211"
> CONFIG_CFG80211=m
> CONFIG_NL80211_TESTMODE=y
> CONFIG_CFG80211_DEVELOPER_WARNINGS=y
> CONFIG_CFG80211_REG_DEBUG=y
> CONFIG_CFG80211_DEFAULT_PS=y
> CONFIG_CFG80211_DEBUGFS=y
> CONFIG_CFG80211_INTERNAL_REGDB=y
> CONFIG_CFG80211_WEXT=y
> CONFIG_LIB80211=m
> CONFIG_LIB80211_CRYPT_WEP=m
> CONFIG_LIB80211_CRYPT_CCMP=m
> CONFIG_LIB80211_CRYPT_TKIP=m
> CONFIG_LIB80211_DEBUG=y
> CONFIG_MAC80211=m
> CONFIG_MAC80211_HAS_RC=y
> CONFIG_MAC80211_RC_PID=y
> CONFIG_MAC80211_RC_MINSTREL=y
> CONFIG_MAC80211_RC_MINSTREL_HT=y
> # CONFIG_MAC80211_RC_DEFAULT_PID is not set 
> CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
> CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
> CONFIG_MAC80211_MESH=y
> CONFIG_MAC80211_LEDS=y
> CONFIG_MAC80211_DEBUGFS=y
> CONFIG_MAC80211_DEBUG_MENU=y
> CONFIG_MAC80211_NOINLINE=y
> CONFIG_MAC80211_VERBOSE_DEBUG=y
> CONFIG_MAC80211_HT_DEBUG=y
> CONFIG_MAC80211_TKIP_DEBUG=y
> CONFIG_MAC80211_IBSS_DEBUG=y
> CONFIG_MAC80211_VERBOSE_PS_DEBUG=y
> CONFIG_MAC80211_VERBOSE_MPL_DEBUG=y
> CONFIG_MAC80211_VERBOSE_MPATH_DEBUG=y
> CONFIG_MAC80211_VERBOSE_MHWMP_DEBUG=y
> CONFIG_MAC80211_VERBOSE_TDLS_DEBUG=y
> CONFIG_MAC80211_DEBUG_COUNTERS=y
> CONFIG_MAC80211_HWSIM=m
> ***
> 
> 2) wifi related
> ************
> - ath5 only supports 1 adhoc vif
> - ath5 can't run in master mode without hostapd
> - ath5 bridging and mesh only possible with 2 wlan cards
> - ath9 no problems at all
> - ath9 bridging and mesh with one wlan card possible
> 
> !!! attention !!!
> 
> when using ath5 wlan cards hostapd service hast o be restared. only 
> after restarting the hostapd service you will be able to link second 
> wlan ath5 card into the bridge br0. i tried many thing but this ist he 
> only way i succeeded.
> 
> 
> 
> *** (/etc/hostapd/hostapd,.conf can be also an adhoc vif)
> interface=wlan1
> bridge=br0
> driver=nl80211
> hw_mode=g
> channel=1
> ssid=adradix_test
> macaddr_acl=0
> auth_algs=1
> ignore_broadcast_ssid=0
> wpa=2
> wpa_passphrase=xxx
> wpa_key_mgmt=WPA-PSK
> wpa_pairwise=TKIP
> rsn_pairwise=CCMP
> ***
> 
> *** (network script > of course no need to use static ip's also dhcp
> possible)
> #!/bin/bash
> 
> # ADRADIX MODIFIED AT 2012-06-09 23:51:24 # echo "1" > 
> /proc/sys/net/ipv4/ip_forward
> 
> ifconfig eth0 down
> ifconfig wlan0 down
> ifconfig wlan1 down
> ifconfig mesh0 down
> ifconfig bat0 down
> ifconfig br0 down
> 
> brctl delbr br0
> batctl if del mesh0
> 
> iw dev wlan0 del
> iw dev wlan1 del
> iw dev mesh0 del
> iw dev mon.wlan0 del
> iw dev mon.wlan1 del
> 
> iw phy phy0 interface add mesh0 type adhoc ifconfig mesh0 mtu 1528 
> iwconfig mesh0 mode ad-hoc essid adradix_mesh ap xx:xx:xx:xx:xx:xx 
> channel
> 10
> batctl if add mesh0
> ifconfig mesh0 0.0.0.0 up
> 
> iw phy phy1 interface add wlan1 type adhoc
> 
> brctl addbr br0
> brctl addif br0 eth0
> brctl addif br0 bat0
> 
> ifconfig bat0 0.0.0.0 up
> ifconfig eth0 0.0.0.0 up
> ifconfig br0 10.xx.xx.xx netmask 255.255.255.0 up
> 
> route add default gw 10.41.20.1
> 
> #echo "1" > /proc/sys/net/ipv4/conf/mesh0/proxy_arp
> #echo "1" > /proc/sys/net/ipv4/conf/bat0/proxy_arp
> #echo "1" > /proc/sys/net/ipv4/conf/br0/proxy_arp
> #echo "1" > /proc/sys/net/ipv4/conf/eth0/proxy_arp
> 
> #
> # IMPORTANT: WITHOUT THAT RESTART BRIDGING DOES NOT WORK 
> /etc/init.d/hostapd restart brctl addif br0 wlan1
> 
> exit 0;
> ***