On 9/8/12 11:37 AM, "Sven Eckelmann" sven@narfation.org wrote:
On Wednesday 05 September 2012 13:32:29 you wrote:
Classification: UNCLASSIFIED Caveats: NONE
OK, based on the answers below, I have a few more questions.
- Is there any way for a user program to communicate with batman if
certain packets need special handling? I don't mind if I have to mark each packet individually, or if I have to do something else interesting, but if I can mark a packet as special, then I can hack code into batman to set the TTL field the way I need it.
How would you signal other layers you don't interact with directly? There is no special socket API that allows you do modify the batman-adv stuff. But you can for example do things like the gateway handling which checks different layer 3/4 things and modifies the behaviour slightly.
So it is (depending on the problem) doable, but there is no general solution Available.
That was what I was afraid of. I'll have to do something else then.
- Does batman rely on multicast in any way for its own operation?
That is, for something that keeps the network running well. If not, I can force all multicast packets to have a TTL of 1. This still requires some way of marking my own IP packets as multicast packets in a manner that batman can recognize, but I'm willing to do that, if it will help.
Multicast on ethernet... yes. Because it does broadcasts to send OGMs. But on IP level - no, batman-adv doesn't work on top of layer 3.
And marking the packets. This could be done using special multicast addresses.
That might work for me! I have few enough nodes that I can assign numerous special multicast addresses to each node, for each purpose I have in mind. I'll have to work on it. Thank you for the suggestion!
Thanks, Cem Karan