Hi, a bunch of questions about B.a.t.m.a.n. performance and your future plans.
After studying the source code, I understand that HNA information is included in every originator message. Isn't such excessive amount of routing information bad for typically limited-capacity wireless links? What are the results of real-world tests - there isn't much info in open-mesh.net about that. What is the largest network in which B.a.t.m.a.n. have been tested? Is there some actual evidence that B.a.t.m.a.n. outperforms OLSR?
And if you concerned about its performance, too - have you considered using Fish-eye to improve the algorithm? It could be either periodical TTL modifications or not including all HNA information in each originator message (i.e. include them in only, say, every 10-th). The second approach could work if there some kind of route-request message. Another approach I can think of would be to introduce some kind of delay in forwarding as the originator packet get farther away from its originator. Or introduce random probability of not forwarding it.
Have you thought of adding some re-active components (like in Hazy Sighted Link State protocol)?
What about handling of asymmetrical links? Currently BATMAN appears to have an implicit assumption of symmetry. Is there any plans to incorporate asymmetrical link support? 'Neighbor Link Quality' field perhaps? Or do you feel that this is something unnecessary for real world setups?
And, finally, what exactly is batman-experimental? A prototype for B.a.t.m.a.n.-IV implementation?
Thanks, A.E.