I have been watching batman-adv for quite a while. I really love the progress that the devs have made and the concepts are great.
I think the holy grail of mesh routing protocols is to handle 3 characteristics of routes and route choice per packet type, possibly using DSCP/TOS values or something.
Those 3 characteristics are link quality, latency, and available throughput. And the multiple routing tables would be so that services requiring low latency can be routed on lowest latency routes, that may not have a lot of throughput, and bulk traffic can be routed through paths that have more available throughput.
I have seen posts discussing interest in adding such features and I am interested to do some reading on this subject as it pertains to batman-adv. Is there anything out there? I couldn't find anything on the site.
On Friday, June 08, 2012 07:45:31 dan wrote:
I have been watching batman-adv for quite a while. I really love the progress that the devs have made and the concepts are great.
I think the holy grail of mesh routing protocols is to handle 3 characteristics of routes and route choice per packet type, possibly using DSCP/TOS values or something.
Those 3 characteristics are link quality, latency, and available throughput. And the multiple routing tables would be so that services requiring low latency can be routed on lowest latency routes, that may not have a lot of throughput, and bulk traffic can be routed through paths that have more available throughput.
I have seen posts discussing interest in adding such features and I am interested to do some reading on this subject as it pertains to batman-adv. Is there anything out there? I couldn't find anything on the site.
AFAIK nobody plans to implement multiple routing tables as you are suggesting here. Unless I missed something ?
Regards, Marek
b.a.t.m.a.n@lists.open-mesh.org
-
dan -
Marek Lindner