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;
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:
- 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)
- 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
- alix2 boards
- 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
- 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
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:
- 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)
- 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
- alix2 boards
- 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
- 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
Hello Walter,
On Wed, Jun 06, 2012 at 12:16:07AM +0200, Walter Robert Ditzler wrote:
so my question is:
- 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,
- can i connect tot he batman mesh essid to get access the base lan?
You want to use ap0 at this point.
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:
- lan to lan bridge (10.41.200.11 <> 10.41.200.12)
what i am too stupid to do:
- 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).
- that ex. a attached laptop has a address 10.41.200.71 > bridged analogue
tot he base lan
so my question is:
- 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.
- 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
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:
- lan to lan bridge (10.41.200.11 <> 10.41.200.12)
what i am too stupid to do:
- 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).
- that ex. a attached laptop has a address 10.41.200.71 > bridged
analogue tot he base lan
so my question is:
- 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.
- 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
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
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
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
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
b.a.t.m.a.n@lists.open-mesh.org
-
Antonio Quartulli -
Sven Eckelmann -
Walter Robert Ditzler -
Wayne Abroue