(usagi-users 03068) State of source routing in usagi?

[Ignacy Gawedzki <ig@xxxxxx>]

Hi,

I would like to ask the maintainers of USAGI what is the state of support of
source-routing in IPv6.  If this feature is not supported, I would like to
know whether it is so because of its complexity or simply because of its
bad ranking on the priority list of things to do.  In the case it is supported
I am also interested in the preferred way to send source-routed packets.

I am currently working on the Qolyester project (http://qolsr.lri.fr/code)
which is an IPv4/IPv6 implementation of the OLSR protocol for ad hoc networks
that is designed to be augmented with QoS routing features.  The current idea
is to source-route the packets of applications that need QoS constraints to be
satisfied: the application communicates with the Qolyester daemon which
calculates a route or replies that a route could not be found.  Then either
the daemon hands the route to the application which sets the necessary options
on its socket, or the daemon sets up what is required to source-route the
application's packet (I suppose a way to go would be to set some matching code
into netfilter and then maybe source-route the matched packets).

Thanks for any information you could provide me.

Ignacy

-- 
NO CARRIER