netdev - Re: RTM_NEWLINK not received by application when connecting multiple devices simultaneously

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120420081400.67a98836@nehalam.linuxnetplumber.net>
Date:	Fri, 20 Apr 2012 08:14:00 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Kristian Evensen <kristian.evensen@...il.com>
Cc:	Ben Greear <greearb@...delatech.com>, netdev@...r.kernel.org
Subject: Re: RTM_NEWLINK not received by application when connecting
 multiple devices simultaneously

On Fri, 20 Apr 2012 16:07:42 +0200
Kristian Evensen <kristian.evensen@...il.com> wrote:

> Thank you very much for all the help.
> 
> >> I spent some more time debugging this now. It turns out that which
> >> interface is seen by my application is not random, it is always the
> >> first one that is connected. This indicates that the bug is that the
> >> netlink message contains information about more than one interface.
> >> However, I am not able to prove this.
> >
> > There is no filtering. A dump request always returns all interfaces.
> 
> I think maybe I didnt explain myself clearly enough, I am sorry. This
> does not happen when I dump interface info, but at the event of
> connecting two interfaces at the same time.
> 
> I have now converted the application to using libmnl, but I still see
> the same error. There is one message that is not received by my
> netlink socket, or at least, the application does not process it. Just
> in case it was bundled together with the message about the first
> interface, I tried adding a loop where I received the packets (similar
> to the one in the -dump example). However, this did not help.
> 
> -Kristian

Check if ip command catches the events (ip monitor).
What is the type of device? and what do you  mean by connecting?
(ie installing, doing admin up, operstate transition, carrier)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html