Hi folks,
my goal is to visualize batman-adv-kernelland network topology. 'echo "server" > /proc/net/batman-adv/vis' activates vis server on the mesh node directly, right? Do the other nodes find the vis server autmagically? What happens, if I wanna use more than one vis server? And the last and most important question: is it possible to run a vis server outside the mesh running layer 2 batman-adv? The layer 3 vis runs fine but I have no clue how to get the visualization running on batman-adv nodes. How to tell the vis server on the mesh nodes to output their data to a dot-draw server (s3d) ? Lot of questions ;-)
For the German readers: I am documenting all the stuff on http://debian.asconix.com/batman-advanced-openwrt-howto but I think, the way I'm describing in the vis chapter is the way to get vis running in layer3 batman, isn't it?
Greets, Chris
Hello Christoph,
On Thu, May 21, 2009 at 10:19:40PM +0200, Christoph Pilka wrote:
Hi folks,
my goal is to visualize batman-adv-kernelland network topology. 'echo "server" > /proc/net/batman-adv/vis' activates vis server on the mesh node directly, right?
Yes, that's right.
Do the other nodes find the vis server autmagically?
Yup, they do.
What happens, if I wanna use more than one vis server?
The running vis servers synchronize each other. You can set up multiple vis servers inside your mesh (this is different from L3 batman).
And the last and most important question: is it possible to run a vis server outside the mesh running layer 2 batman-adv?
That's not possible. They only run within the batman-adv module, and you can only access the data locally on the node. One thing you can do is building a script with ssh, e.g.
ssh <yournode> 'cat /proc/net/batman-adv/vis'
which would give you the topology even on a remote node. What you can also do is building a vis server similar to the L3 one on the node by using netcat and a small shellscript which prints out /proc/net/batman-adv/vis in a loop.
The layer 3 vis runs fine but I have no clue how to get the visualization running on batman-adv nodes. How to tell the vis server on the mesh nodes to output their data to a dot-draw server (s3d) ? Lot of questions ;-)
if you build a vis server with netcat and a shellscript this will be possible. Please note however that you might need to patch the s3d visualization program (olsrs3d or meshs3d) as it expects IP addresses, not MAC addresses. This is not hard to do ....
For the German readers: I am documenting all the stuff on http://debian.asconix.com/batman-advanced-openwrt-howto but I think, the way I'm describing in the vis chapter is the way to get vis running in layer3 batman, isn't it?
Right, your description references to the layer 3 vis server. Layer 2 is a little bit different ...
Greets, Chris
-- "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
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 Simon,
many thanks for all the infos and hints. The base install seems to work properly. I'll take a look at s3d this weekend cause I'm very interested in getting it running at ethernet frame level. By the way, the JSON output seems to be really nice feature but the code is only available for level3 batman ?
Greets. Chris <°(((><
2009/5/22 Simon Wunderlich simon.wunderlich@s2003.tu-chemnitz.de
Hello Christoph,
On Thu, May 21, 2009 at 10:19:40PM +0200, Christoph Pilka wrote:
Hi folks,
my goal is to visualize batman-adv-kernelland network topology. 'echo "server" > /proc/net/batman-adv/vis' activates vis server on the mesh node directly, right?
Yes, that's right.
Do the other nodes find the vis server autmagically?
Yup, they do.
What happens, if I wanna use more than one vis server?
The running vis servers synchronize each other. You can set up multiple vis servers inside your mesh (this is different from L3 batman).
And the last and most important question: is it possible to run a vis server outside the mesh running layer 2 batman-adv?
That's not possible. They only run within the batman-adv module, and you can only access the data locally on the node. One thing you can do is building a script with ssh, e.g.
ssh <yournode> 'cat /proc/net/batman-adv/vis'
which would give you the topology even on a remote node. What you can also do is building a vis server similar to the L3 one on the node by using netcat and a small shellscript which prints out /proc/net/batman-adv/vis in a loop.
The layer 3 vis runs fine but I have no clue how to get the visualization running on batman-adv nodes. How to tell the vis server on the mesh nodes to output their data to a dot-draw server (s3d) ? Lot of questions ;-)
if you build a vis server with netcat and a shellscript this will be possible. Please note however that you might need to patch the s3d visualization program (olsrs3d or meshs3d) as it expects IP addresses, not MAC addresses. This is not hard to do ....
For the German readers: I am documenting all the stuff on http://debian.asconix.com/batman-advanced-openwrt-howto but I think, the way I'm describing in the vis chapter is the way to get vis running in layer3 batman, isn't it?
Right, your description references to the layer 3 vis server. Layer 2 is a little bit different ...
Greets, Chris
-- "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
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.9 (GNU/Linux)
iEYEARECAAYFAkoWh6oACgkQrzg/fFk7axazzwCdEj0eeCi+lI10Fjo3IXevv78Q PWYAn01bptuXhZX+bo6rXE5Sm1n8N3jt =ouCT -----END PGP SIGNATURE-----
On Friday 22 May 2009 19:51:20 Christoph Pilka wrote:
many thanks for all the infos and hints. The base install seems to work properly. I'll take a look at s3d this weekend cause I'm very interested in getting it running at ethernet frame level. By the way, the JSON output seems to be really nice feature but the code is only available for level3 batman ?
No, it is also available in the current svn version of batman-adv. See https://www.open-mesh.org/changeset/1265 for more informations.
Best regards, Sven
Hi,
For the German readers: I am documenting all the stuff on http://debian.asconix.com/batman-advanced-openwrt-howto but I think, the way I'm describing in the vis chapter is the way to get vis running in layer3 batman, isn't it?
its fantastic that you write such an extensive documentation. As soon as you feel ready I will add a link from our page to yours, so that people can find you.
I think there are 2 hidden misunderstandings in the howto:
* You are splitting up the VLANs and I did not quite get the reason. In the document you state the number of OGMs will be decreased. Whether it decreases or not heavily depends on the network attached to these VLANs. How does the topology look like ? May be I overlooked that section ?
* The vis-advanced daemon is not necessary here because the kernel module has the server built-in. All you need to do is activating a server (echo "server"
/proc/net/batman-adv/vis) which allows you to retrieve the information via
cat /proc/net/batman-adv/vis. The vis-advanced daemon goes together with batman-adv-userspace which is the user space implementation of the layer 2 approach. Its a bit confusing - we have to think about how to clean it up ..
In case you are aware of all these facts just discard my mail. :-)
Regards, Marek
Hi all,
Hi* You are splitting up the VLANs and I did not quite get the reason. In
the document you state the number of OGMs will be decreased. Whether it decreases or not heavily depends on the network attached to these VLANs. How does the topology look like ? May be I overlooked that section ?
Well, I didn't mention it, but the reason for splitting the lan ports into VLANs is an approach for using bat-adv on boxes in a partially wired environment (indoor installations with some ethernet wires). So, yepp, you're right, it depends on the network topology. In my case I am using some of the LAN connections to link the boxes among each other. So I think, it's a good approach to seperate the lan ports and to let bat-adv bridge the frames. Correct me, if it's wrong.
* The vis-advanced daemon is not necessary here because the kernel module
has the server built-in. All you need to do is activating a server (echo "server"
/proc/net/batman-adv/vis) which allows you to retrieve the information
via cat /proc/net/batman-adv/vis. The vis-advanced daemon goes together with batman-adv-userspace which is the user space implementation of the layer 2 approach. Its a bit confusing - we have to think about how to clean it up ..
Yepp, you're right. I've documented the vis stuff beeing not sure if it's working this way on layer 2. Simon answered all of my questions so now it's time for me to write down the bat-adv-kernel way ;-) He gave me some very interesting hints to collect the data from outside the mesh like polling /proc/net/batman-adv/vis. I think it's a good challenge for me for this weekend to set up a nice solution to collect the data on a central box outside the mesh and visualize it. I have some experiences with JSON, so Iwould use it as exchange format. Well, patching s3d to accept MAC- instead of IP-addresses seems to be a nice solution too.
Regards, Chris
b.a.t.m.a.n@lists.open-mesh.org
-
Christoph Pilka -
Marek Lindner -
Simon Wunderlich -
Sven Eckelmann