Re: AODVv2 implementation

> For detecting a route request for a non-existing route my idea always
> was to use a TUN device and point a route to the whole MANET (or even
> the default route) into it.

That's going to work, but it pushes every packet through two kernel-user
transitions, which makes it unsuitable for production use.

I don't see many solutions.  Either an implementation moves completely
outside of the kernel, a little like DPDK, but that means that AODVv2
traffic bypasses all of the kernel's infrastructure (including
firewalling).  Or else somebody works out a small set of callbacks that
are enough to implement AODVv2 as a user process without pushing all
packets to userspace, and then spend the next five years of their life
getting them into mainline Linux and at least some BSD.

Hence my asking whether anyone has a complete list of callbacks required
by the current draft of AODVv2.  Charlie pointed me at Section 6.2, but
that list is obviously incomplete: there are obviously callbacks in 6.3,
and most certainly in other sections of the draft.

-- Juliusz