Hi,
I was going through the Internet Draft for B.A.T.M.A.N, and wanted to confirm if the bits 10 to 15 in the OGM packet are supposed to be all zeroes always?
Thanks
On Thursday, 25 June 2020 15:22:46 CEST Rahul Bothra wrote:
I was going through the Internet Draft for B.A.T.M.A.N, and wanted to confirm if the bits 10 to 15 in the OGM packet are supposed to be all zeroes always?
Please don't implement the legacy draft which was never finished. This is really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really outdated.
But the batmand layer 3 compat version 5 handled these as reserved flags. So it would have been a good idea at that time not to leave them in a random state and just set them to 0. This would have allowed announcements of additional features in the future.
See https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/ include/uapi/linux/batadv_packet.h for the B.A.T.M.A.N. IV and B.A.T.M.A.N. V layer 2 packet definitions.
Kind regards, Sven
Thanks, is there a published documentation / memo for B.A.T.M.A.N. V currently present in the kernel tree? If not, I'd be happy to join in writing one as I work on the NS-3 model.
Thanks Rahul Bothra
On Thu, Jun 25, 2020 at 7:36 PM Sven Eckelmann sven@narfation.org wrote:
On Thursday, 25 June 2020 15:22:46 CEST Rahul Bothra wrote:
I was going through the Internet Draft for B.A.T.M.A.N, and wanted to confirm if the bits 10 to 15 in the OGM packet are supposed to be all zeroes always?
Please don't implement the legacy draft which was never finished. This is really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really outdated.
But the batmand layer 3 compat version 5 handled these as reserved flags. So it would have been a good idea at that time not to leave them in a random state and just set them to 0. This would have allowed announcements of additional features in the future.
See https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/ include/uapi/linux/batadv_packet.h for the B.A.T.M.A.N. IV and B.A.T.M.A.N. V layer 2 packet definitions.
Kind regards, Sven
On Thursday, 25 June 2020 17:16:16 CEST Rahul Bothra wrote:
Thanks, is there a published documentation / memo for B.A.T.M.A.N. V currently present in the kernel tree?
https://www.open-mesh.org/projects/batman-adv/wiki/BATMAN_V
Kind regards, Marek Lindner
On Thursday, 25 June 2020 17:16:16 CEST Rahul Bothra wrote:
Thanks, is there a published documentation / memo for B.A.T.M.A.N. V currently present in the kernel tree? If not, I'd be happy to join in writing one as I work on the NS-3 model.
There are various documents in the wiki [1]. But the code is the most precise documentation at the moment. Other persons on this mailing list can also answer further questions and help you in situations when the wiki documentation doesn't match the actual implementation. At least I've found already various problems on the ELP page but the developers involved in the implementation didn't update the page(s) (yet).
Kind regards, Sven
[1] https://www.open-mesh.org/projects/batman-adv/wiki/Protocol_information
b.a.t.m.a.n@lists.open-mesh.org
-
Marek Lindner -
Rahul Bothra -
Sven Eckelmann