Re: Kernel hooks for AODVv2 [was: AODVv2 implementation]

Yes...

it's a similar problem with SMF (or other multicast forwarders). The
existing multicast-routing API of Linux is something between "arcane"
and "horrible"... and it's only partially useful for Manet
Multicast-Routing. Which means everyone tries to implement SMF with a
raw-socket, which integrates horrible (or not at all) with more
complicated routing environments (e.g. Manet-Routers with multiple
interfaces and multi-topology routing).

Henning Rogge

On Sat, Feb 3, 2024 at 1:17 AM Charlie Perkins
<[email protected]> wrote:
>
> Hello Juliusz,
>
> Follow-up below...
>
> On 12/4/2023 11:00 AM, Juliusz Chroboczek wrote:
>
> So has somebody written down what is the small set of callbacks from the
> data plane to the control plane that is required to implement AODVv2?
> Once that is written down, then we can have a discussion on whether it is
> indeed the case that AODVv2 is easy to implement.
>
>
> Section 6.4 attempts to provide such a list.  I agree that it would be worthwhile to focus on the best ways to implement these required interactions.
>
> Regards,
> Charlie P.
> _______________________________________________
> manet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/manet

_______________________________________________
manet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/manet