Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Morgan Nelson <mnelson@argontech.net>
To: lartc@vger.kernel.org
Subject: [LARTC] netlink api
Date: Tue, 10 Aug 2004 20:48:05 +0000	[thread overview]
Message-ID: <41193485.9020705@argontech.net> (raw)

Hey all,

    I'm looking for more detailed info on the netlink api.  I've read
Andi Kleen's man pages (which describe themselves as lacking and
incomplete), rfc3549 -- Linux Netlink as an IP Services Protocol (which
was a nice general overview, but lacking in implementation detail), both
the iproute2/ip/tc source and the kernel source (which have no usable
documentation/comments), etc.

    Andi's man pages and rfc3549 were a great help in getting into the
basics of the netlink api, but I can't seem to find anything more
specific about the RTA TLV's, order of RTA's, which RTA's are optional,
which are required, etc.

    I'm thinking about writing a C++ library for netlink sockets, but I
don't necessarily want to spend the next 6 months wading through kernel
source to figure out that I had a single param wrong somewhere.  I'd
also be happy to compile a howto/tutorial/spec for others to use, if I
could just get the info.  Would anybody be interested in this?

    I'm more than happy to RTFM, but I need to know which fine manual to
read.  Please, any pointer would be greatly appreciated.

Morgan

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-08-10 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 20:48 Morgan Nelson [this message]
2004-08-11  0:09 ` [LARTC] netlink api Martin A. Brown
2004-08-11 15:13 ` Morgan Nelson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41193485.9020705@argontech.net \
    --to=mnelson@argontech.net \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox