netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: netlink tester program
Date: Mon, 2 Jun 2003 14:04:52 -0700	[thread overview]
Message-ID: <20030602140452.039248de.rddunlap@osdl.org> (raw)
In-Reply-To: <20030530.234211.102567405.davem@redhat.com>

On Fri, 30 May 2003 23:42:11 -0700 (PDT) "David S. Miller" <davem@redhat.com> wrote:

|    From: "Randy.Dunlap" <rddunlap@osdl.org>
|    Date: Fri, 30 May 2003 20:22:12 -0700 (PDT)
|    
|    Oh well, it's at this URL, bugs and all.
|    
|    http://www.xenotime.net/linux/ipv6/rtnl_test.c
|    
| I know you don't want to use libnetlink from iproute2, but I want to
| stress that it takes care of all of the minutae of netlink socket
| usage that you have to duplicate in your little test program and this
| duplication leads to bugs.
| 
| Firstly, you needs to be fixed to call recvmsg() multiple times,
| you'll get one entry for each recvmsg call in the table you are
| querying.

Yes, I noticed that I was getting only 1 msg there.

| You really need something like rtnl_talk() or rtnl_dump_filter()
| from libnetlink to do this properly.

Does anyone have documentation (or semantics) for rtnl_talk()?
or just some blurb about it?
Andi's libnetlink man page missed it somehow.

Thanks,
--
~Randy

  parent reply	other threads:[~2003-06-02 21:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 16:00 netlink tester program Randy.Dunlap
2003-05-31  0:11 ` David S. Miller
2003-05-31  3:22   ` Randy.Dunlap
2003-05-31  6:42     ` David S. Miller
2003-05-31 12:09       ` Andi Kleen
2003-06-02 17:07         ` Randy.Dunlap
2003-06-02 21:04       ` Randy.Dunlap [this message]
2003-06-02 21:56         ` David S. Miller
2003-06-03  1:56           ` David Brownell
2003-06-03  2:02             ` David S. Miller
2003-06-03  3:34               ` David Brownell
2003-06-03  3:38                 ` David S. Miller
2003-06-03  3:49                   ` Randy.Dunlap
2003-06-03  3:51                     ` David S. Miller
2003-06-03  7:57                   ` Hisham Kotry
2003-06-09  1:35                     ` Jamal Hadi
2003-06-09 14:37                       ` Mr. James W. Laferriere
2003-06-09 17:16                       ` David S. Miller
2003-06-03  2:33           ` John S. Denker
2003-06-03  2:38             ` David S. Miller
2003-06-03  3:20               ` John S. Denker
2003-06-03  3:22                 ` David S. Miller
2003-06-03  3:41                   ` John S. Denker
2003-06-03  3:46                     ` David S. Miller
2003-06-03  3:54                       ` Randy.Dunlap
2003-06-03  3:54                         ` David S. Miller
2003-06-03  3:37             ` David Brownell
2003-06-03  3:32           ` Randy.Dunlap
2003-06-03  3:35             ` David S. Miller

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=20030602140452.039248de.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=davem@redhat.com \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).