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.

> As soon as you set a more specific route, the traffic will not go into
> the TUN anymore.

Ah, so instead of pushing all traffic through userspace, as I envisioned,
you use the TUN hack for unknown destinations, but establish normal kernel
routes or known destinations.  I see, that's why you need a way to monitor
which routes are being actively used.

Charlie, could you please tell us which of these two techniques is the one
that you envision, and tell us what's the bit that we're still missing?

-- Juliusz