(usagi-users 03406) Re: setsockopt for IPv6 on Fedora Core 2?

[David Stevens <dlstevens@xxxxxxxxxx>]

Patrick,
        Those are utility functions to make it easier to construct
options, but aren't needed (they would be part of glibc, not in the 
kernel).
Your application just needs to pass well-formed data to sendmsg(),
whether you construct it using inet6_opt_* functions or not.
        I'm currently working on RFC 3542 (Advanced Sockets API)
compliance, and others may be too, so I think it's safe to say this area
is "work in progress" right now.
        To receive hop options, you can use the "IPV6_HOPOPTS"
boolean (set it to 1). In the new RFC, this becomes IPV6_RECVHOPTS,
so your code will be different as the work progresses.
        To send, you can use the IPV6_HOPOPTS cmsg_type in
ancillary data (in new and old API).
        There are examples, using the new interface, in RFC3542,
but some of that, of course, is not implemented yet. Still, it does have
example code using sendmsg(), if you haven't done that before.

                                                +-DLS