Hi
I am trying to bring up open mesh with batman advanced. My network configuration is as follows:
_____DSL cable_____Linksys Router____Cisco PIX______Switch______ open mesh 1 ---------- open mesh 2 -------- client laptop
192.168.50.1 | _______ my PC
|_______
|_______
|_______
My IPs get automatically assigned by the PIX (In the subnet 192.168.50.0)
OPEN MESH 1 - configuration ===========================
1. I stop the routing daemons running on them. It has eth0, ath0, ath1 and ath2 interfaces where ath0 is in adhoc mode and ath1 and ath2 are in master mode
I create a bridge between all these interfaces (br0 - eth0, ath0, ath1, ath2) and i run udhcpc with br0 as an argument so that my bridge gets an IP from the network
All other interfaces are given an IP of 0.0.0.0
My bridge gets an IP (192.168.50.5)
I have batman_core module and i update the /proc/net/batman-adv/interfaces with br0 interface echo br0 > /proc/net/batman-adv/interfaces
OPENMESH 2 - configuration ==========================
1. I stop the routing daemons. It has ath0, ath1, ath2 interfaces. I again bridge these interfaces (br0 - ath0, ath1, ath2
I try getting an IP for this node usign the same method of running udhcpc but i am unable to So I dont have an IP - but i dont worry about it now.
I have batman_core module and i update the /proc/net/batman-adv/interfaces with br0 interface echo br0 > /proc/net/batman-adv/interfaces
OBSERVATION =========== Now when i check connectivity using battool i can ping between openmesh 2 and openmesh 1 using battool bp My originators file indicate the mac of the other mesh node
E.g. on openmesh2
root@open-mesh:/proc/net/batman-adv# cat originators Originator (#/255) Nexthop [outgoingIF]: Potential nexthops .. . [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC: br0/00:18:0a:01:44:d0] openmesh1 MAC (255) openmesh1 MAC [ br0]: openmesh1 MAC (255)
Associate a client ==================
I now try to associate a client to open mesh 2. Its IP request gets forwarded to the wired network and it receives an IP (192.168.50.6)
However i can't batping to it from either openmesh 2 or openmesh 1
Is something missing in my configuration?
Hi,
OPENMESH 2 - configuration
I stop the routing daemons. It has ath0, ath1, ath2 interfaces. I again bridge these interfaces (br0 - ath0, ath1, ath2
I try getting an IP for this node usign the same method of running
udhcpc but i am unable to So I dont have an IP - but i dont worry about it now.
You wont get an IP address on distant hosts (more than 1 hop) unless you have batman running. The adhoc network will not relay your message.
B.A.T.M.A.N. advanced is a kind of bridging tool on its own. You should load the module and add the batman interfaces (in your case ath0). After configuring batman you will have a new interface called "bat0" which you can add to your bridge setup (br0 - ath1, ath2, bat0). Run udhcp on top of br0 now.
Associate a client
I now try to associate a client to open mesh 2. Its IP request gets forwarded to the wired network and it receives an IP (192.168.50.6)
However i can't batping to it from either openmesh 2 or openmesh 1 Is something missing in my configuration?
You can't run the battools (e.g. batping) from a client that does not run batman advanced. The battools connect to the running batman to inject their ping requests. Batman will recognize these special packets and treat them accordingly.
Regards, Marek
On Sat, Jan 24, 2009 at 2:42 AM, Marek Lindner lindner_marek@yahoo.de wrote:
Hi,
OPENMESH 2 - configuration
I stop the routing daemons. It has ath0, ath1, ath2 interfaces. I again bridge these interfaces (br0 - ath0, ath1, ath2
I try getting an IP for this node usign the same method of running
udhcpc but i am unable to So I dont have an IP - but i dont worry about it now.
You wont get an IP address on distant hosts (more than 1 hop) unless you have batman running. The adhoc network will not relay your message.
B.A.T.M.A.N. advanced is a kind of bridging tool on its own. You should load the module and add the batman interfaces (in your case ath0). After configuring batman you will have a new interface called "bat0" which you can add to your bridge setup (br0 - ath1, ath2, bat0). Run udhcp on top of br0 now.
Thanks for your reply.
I do have the batman module running on openmesh2 as well and I have included in the br0 (ath1, ath2, bat0). I also have set ath0 in /proc/net/batman-advanced/interfaces.
I also run udhcpc specifying -i br0. However I am unable to get an IP for openmesh2.
So i was basically wondering if batman kernel module is running on both openmesh routers and one of routers is connected to eth0 (openmesh1) while the other is wirelessly connected to openmesh1 (i.e. my openmesh2) - should it receive an IP from my wired backbone?
Associate a client
I now try to associate a client to open mesh 2. Its IP request gets forwarded to the wired network and it receives an IP (192.168.50.6)
However i can't batping to it from either openmesh 2 or openmesh 1 Is something missing in my configuration?
You can't run the battools (e.g. batping) from a client that does not run batman advanced. The battools connect to the running batman to inject their ping requests. Batman will recognize these special packets and treat them accordingly.
Ok. That makes sense that batping cannot ping clients (as they dont run batman) Again my client when associated to openmesh1 (which is wired) gets an IP however when connected to openmesh2 (wirelessly connected to openmesh1) does not get an IP
I hope other than setting the interface "ath0" in /proc/net/batman-advanced/interfaces - i dont need any other configuration changes.
Since I can batping between the two routers i guess the layer 2 connectivity is established between these guys - am just wondering if they should be able to forward requests like dhcp over multiple hop (1 hop and above)....
Regards, Marek
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
On Tuesday 27 January 2009 01:34:16 Gargi Purohit wrote:
I hope other than setting the interface "ath0" in /proc/net/batman-advanced/interfaces - i dont need any other configuration changes.
Since I can batping between the two routers i guess the layer 2 connectivity is established between these guys - am just wondering if they should be able to forward requests like dhcp over multiple hop (1 hop and above)....
Yes, a working batping indicates that the connection between both modules is given. The DHCP request should be forwarded without problems. Your setup is misconfigured somewhere.
Could you please show the output of "brctl show br0" and "cat /proc/net/batman-adv/interfaces" on both nodes. You can check where the dhcp request dies by using tcpdump or batdump.
Regards, Marek
On Mon, Jan 26, 2009 at 1:41 PM, Marek Lindner lindner_marek@yahoo.de wrote:
On Tuesday 27 January 2009 01:34:16 Gargi Purohit wrote:
I hope other than setting the interface "ath0" in /proc/net/batman-advanced/interfaces - i dont need any other configuration changes.
Since I can batping between the two routers i guess the layer 2 connectivity is established between these guys - am just wondering if they should be able to forward requests like dhcp over multiple hop (1 hop and above)....
Yes, a working batping indicates that the connection between both modules is given. The DHCP request should be forwarded without problems. Your setup is misconfigured somewhere.
Could you please show the output of "brctl show br0" and "cat /proc/net/batman-adv/interfaces" on both nodes. You can check where the dhcp request dies by using tcpdump or batdump.
On node 1 (Which is wired) ---------------------------------------
root@open-mesh:~# brctl show br0 bridge name bridge id STP enabled interfaces br0 8000.00180a0145b0 no bat0 ath1 ath2 eth0 root@open-mesh:~# cat /proc/net/batman-adv/interfaces ath0
root@open-mesh:~# cat /proc/net/batman-adv/originators Originator (#/255) Nexthop [outgoingIF]: Potential nexthops ... [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC: ath0/00:18:0a:01:45:b0] 00:18:0a:01:44:d0 (255) 00:18:0a:01:44:d0 [ ath0]: 00:18:0a:01:44:d0 (255)
On node 2 (Which is connected wirelessly to node 1 - eth0 is down) -------------------------------------------------------------------------------------------------- root@open-mesh:/proc/net# brctl show br0 bridge name bridge id STP enabled interfaces br0 8000.00ff678aa75f no ath1 bat0 ath2 root@open-mesh:/proc/net# cat /proc/net/batman-adv/interfaces ath0
root@open-mesh:/proc/net# cat /proc/net/batman-adv/originators Originator (#/255) Nexthop [outgoingIF]: Potential nexthops .. . [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC: ath0/00:18:0a:01:44:d0] 00:18:0a:01:45:b0 (255) 00:18:0a:01:45:b0 [ ath0]: 00:18:0a:01:45:b0 (255)
root@open-mesh:/proc/net#
Regards, Marek
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
Hello Gargi,
your setup looks correct from what you've pasted. Some questions to find the reason:
1. Have you set "up" all the interfaces by doing "ifconfig <dev> up"?
2. If you set IPs on br0 of open-mesh1 and br0 of open-mesh2 manually, can they ping each other?
3. If yes (and configured within the subnet of PIX): Can you ping PIX from open-mesh2?
4. If you do udhcpc on open-mesh2, do you receive the packet on br0 on open-mesh1? Please check with tcpdump, this should work. If yes, do you also receive it on the PIX? (Maybe the answer is getting lost somewhere).
BTW, i've set up similar scenarios yet, this is supposed to work. ;)
best regards, Simon
On Mon, Jan 26, 2009 at 02:28:44PM -0600, Gargi Purohit wrote:
On Mon, Jan 26, 2009 at 1:41 PM, Marek Lindner lindner_marek@yahoo.de wrote:
On Tuesday 27 January 2009 01:34:16 Gargi Purohit wrote:
I hope other than setting the interface "ath0" in /proc/net/batman-advanced/interfaces - i dont need any other configuration changes.
Since I can batping between the two routers i guess the layer 2 connectivity is established between these guys - am just wondering if they should be able to forward requests like dhcp over multiple hop (1 hop and above)....
Yes, a working batping indicates that the connection between both modules is given. The DHCP request should be forwarded without problems. Your setup is misconfigured somewhere.
Could you please show the output of "brctl show br0" and "cat /proc/net/batman-adv/interfaces" on both nodes. You can check where the dhcp request dies by using tcpdump or batdump.
On node 1 (Which is wired)
root@open-mesh:~# brctl show br0 bridge name bridge id STP enabled interfaces br0 8000.00180a0145b0 no bat0 ath1 ath2 eth0 root@open-mesh:~# cat /proc/net/batman-adv/interfaces ath0
root@open-mesh:~# cat /proc/net/batman-adv/originators Originator (#/255) Nexthop [outgoingIF]: Potential nexthops ... [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC: ath0/00:18:0a:01:45:b0] 00:18:0a:01:44:d0 (255) 00:18:0a:01:44:d0 [ ath0]: 00:18:0a:01:44:d0 (255)
On node 2 (Which is connected wirelessly to node 1 - eth0 is down)
root@open-mesh:/proc/net# brctl show br0 bridge name bridge id STP enabled interfaces br0 8000.00ff678aa75f no ath1 bat0 ath2 root@open-mesh:/proc/net# cat /proc/net/batman-adv/interfaces ath0
root@open-mesh:/proc/net# cat /proc/net/batman-adv/originators Originator (#/255) Nexthop [outgoingIF]: Potential nexthops .. . [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC: ath0/00:18:0a:01:44:d0] 00:18:0a:01:45:b0 (255) 00:18:0a:01:45:b0 [ ath0]: 00:18:0a:01:45:b0 (255)
root@open-mesh:/proc/net#
Regards, Marek
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
On Mon, Jan 26, 2009 at 3:24 PM, Simon Wunderlich simon.wunderlich@s2003.tu-chemnitz.de wrote:
Hello Gargi,
your setup looks correct from what you've pasted. Some questions to find the reason:
Thanks a lot for your hints. Really appreciate!!
- Have you set "up" all the interfaces by doing "ifconfig <dev> up"?
I screwed up here ... bat0 was not up...i brought it up on both openmesh1 and openmesh2 and i got an IP for openmesh2
I hope likewise a client of openmesh2 would too get an IP...I would check that soon....just wanted to thank you first :D
- If you set IPs on br0 of open-mesh1 and br0 of open-mesh2 manually,
can they ping each other?
- If yes (and configured within the subnet of PIX):
Can you ping PIX from open-mesh2?
- If you do udhcpc on open-mesh2, do you receive the packet on br0 on
open-mesh1? Please check with tcpdump, this should work. If yes, do you also receive it on the PIX? (Maybe the answer is getting lost somewhere).
BTW, i've set up similar scenarios yet, this is supposed to work. ;)
best regards, Simon
On Mon, Jan 26, 2009 at 02:28:44PM -0600, Gargi Purohit wrote:
On Mon, Jan 26, 2009 at 1:41 PM, Marek Lindner lindner_marek@yahoo.de wrote:
On Tuesday 27 January 2009 01:34:16 Gargi Purohit wrote:
I hope other than setting the interface "ath0" in /proc/net/batman-advanced/interfaces - i dont need any other configuration changes.
Since I can batping between the two routers i guess the layer 2 connectivity is established between these guys - am just wondering if they should be able to forward requests like dhcp over multiple hop (1 hop and above)....
Yes, a working batping indicates that the connection between both modules is given. The DHCP request should be forwarded without problems. Your setup is misconfigured somewhere.
Could you please show the output of "brctl show br0" and "cat /proc/net/batman-adv/interfaces" on both nodes. You can check where the dhcp request dies by using tcpdump or batdump.
On node 1 (Which is wired)
root@open-mesh:~# brctl show br0 bridge name bridge id STP enabled interfaces br0 8000.00180a0145b0 no bat0 ath1 ath2 eth0 root@open-mesh:~# cat /proc/net/batman-adv/interfaces ath0
root@open-mesh:~# cat /proc/net/batman-adv/originators Originator (#/255) Nexthop [outgoingIF]: Potential nexthops ... [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC: ath0/00:18:0a:01:45:b0] 00:18:0a:01:44:d0 (255) 00:18:0a:01:44:d0 [ ath0]: 00:18:0a:01:44:d0 (255)
On node 2 (Which is connected wirelessly to node 1 - eth0 is down)
root@open-mesh:/proc/net# brctl show br0 bridge name bridge id STP enabled interfaces br0 8000.00ff678aa75f no ath1 bat0 ath2 root@open-mesh:/proc/net# cat /proc/net/batman-adv/interfaces ath0
root@open-mesh:/proc/net# cat /proc/net/batman-adv/originators Originator (#/255) Nexthop [outgoingIF]: Potential nexthops .. . [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC: ath0/00:18:0a:01:44:d0] 00:18:0a:01:45:b0 (255) 00:18:0a:01:45:b0 [ ath0]: 00:18:0a:01:45:b0 (255)
root@open-mesh:/proc/net#
Regards, Marek
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJfin8rzg/fFk7axYRArD6AJsFopD8+ZhlwhJWN6jNnGAo83qHPgCdFgHp t/I6o0/TASreYNzzrjw65fY= =rn7h -----END PGP SIGNATURE-----
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
b.a.t.m.a.n@lists.open-mesh.org
-
Gargi Purohit -
Marek Lindner -
Simon Wunderlich