From: Stephen Hemminger <shemminger@vyatta•com>
To: Kristian Evensen <kristian.evensen@gmail•com>
Cc: Ben Greear <greearb@candelatech•com>, netdev@vger•kernel.org
Subject: Re: RTM_NEWLINK not received by application when connecting multiple devices simultaneously
Date: Fri, 20 Apr 2012 09:15:59 -0700 [thread overview]
Message-ID: <20120420091559.732541ef@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAKfDRXiPOj64M0oSW9Dc5F0+src3mAjKYna+UM8hwEiHEJXniQ@mail.gmail.com>
On Fri, 20 Apr 2012 18:04:49 +0200
Kristian Evensen <kristian.evensen@gmail•com> wrote:
> I have uploaded a compressed version of my listener code here:
> http://pastebin.com/f1NPYGSh
>
> The othe operations my application do related to netlink, is to
> configure the sockets. Could it be that the configuration messages
> somehow disturb the retrieval of other messages, as they all use the
> same mnl_sock? None of them requests any replies (they are all
> RTM_NEW*/NLM_F_CREATE), but I am not sure about the internal working
> of netlink.
Most applications using netlink listening have two sockets, one
for events the other for requests. The problem is that your own requests
will generate events and it is hard to tell what to expect next
the response (ACK) or the async event when using the same socket.
prev parent reply other threads:[~2012-04-20 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 11:44 RTM_NEWLINK not received by application when connecting multiple devices simultaneously Kristian Evensen
2012-04-19 14:26 ` Ben Greear
2012-04-19 14:54 ` Stephen Hemminger
2012-04-19 15:07 ` Kristian Evensen
2012-04-19 19:54 ` Kristian Evensen
2012-04-19 20:36 ` Stephen Hemminger
2012-04-20 14:07 ` Kristian Evensen
2012-04-20 15:14 ` Stephen Hemminger
2012-04-20 15:54 ` Kristian Evensen
2012-04-20 16:04 ` Kristian Evensen
2012-04-20 16:15 ` Stephen Hemminger [this message]
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=20120420091559.732541ef@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta$(echo .)com \
--cc=greearb@candelatech$(echo .)com \
--cc=kristian.evensen@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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