[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 03474) Schedule for RFC 3542 in Linux? (was: Any particular reason that IPV6_TCLASS/IPV6_RECVTCLASS is not implemented?)
On Thu, 23 Jun 2005, Peder Chr. Norgaard wrote:
> > > But - do you have any opinions on the other issue I raised - the
> > > transition issue? I will probably have to hack a solution within my
> > > project - there I need packages right here and now (such as quagga and
> > > iputils) that are run-time independent on whether the kernel contains
> > your
>
> >
> > If you're compiling on a system that supports both,
> > then you can call setsockopt with IPV6_RECVx. If that
> > returns ENOPROTOOPT (I think that's the errno for an
> > invalid socket option-- should check), then call again
> > with "IPV6_2292x" (or whatever the old value is defined
> > as in the eventual patch).
>
> Of course - that solves my problem. I should have thought about
> that myself. Thank you for your answer.
>
I have now worked with this solution for some time, and it works just
fine. I have adapted it for Debian, where I can build packages that
run under both 2292 and 3542 semantics.
I was considering to forward my results to the Debian organization, to
help preparing that distribution for the transition. First, however, I
would ask if there is any schedule for inclusion of this change in the
actual released linux kernel? Like, if it is not going to happen within
next 12 months or so, there is no reason to do it now.
I know that this is voluntary work, so I won't be surprised by a "no
schedule exists" answer.
best regards
--
Peder Chr. Nørgaard Senior System Developer, M. Sc.
Ericsson Denmark A/S, Telebit Division
Skanderborgvej 232 tel: +45 30 91 84 31
DK-8260 Viby J, Denmark fax: +45 89 38 51 01
e-mail: Peder.Chr.Norgaard@xxxxxxxxxxxx
(old e-mail 2000-2003: Peder.C.Norgaard@xxxxxxxxxxxxxxx)
(old e-mail 1992-2000: pcn@xxxxxxx)