netdev - Re: multicast, interfaces, kernel 3.0+...

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: <20120922.003133.2272531217856660981.davem@davemloft.net>
Date:	Sat, 22 Sep 2012 00:31:33 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	mjt@....msk.ru
Cc:	netdev@...r.kernel.org
Subject: Re: multicast, interfaces, kernel 3.0+...

From: Michael Tokarev <mjt@....msk.ru>
Date: Sat, 22 Sep 2012 08:21:52 +0400

> The IP_ADD_MEMBERSHIP interface is apparently misdefined, because it
> accepts an IP address of an interface, instead of an ifindex, or
> ifname, or something like this, since there's no, obviously, 1:1
> correspondence between ifaces and addresses, an iface can have no
> addresses assotiated with it, or two ifaces can share one IP address
> like in my case.  But the "questionable" part is the "usualness" of
> this setup I have here, with two ifaces having the same IP address.

Can you at least look at the API specification for IP_ADD_MEMBERSHIP
before making such claims?

The IP_ADD_MEMBERSHIP interface allows for the specification of a
specific interface, the structure you pass into IP_ADD_MEMBERSHIP has
an ->imr_ifindex field and this is the first key the call uses
to pick a device.

If you do not specify an explicit ifindex, and leave it at zero which
I bet your application is doing, it picks the first address which has
the specified address.

As you have discovered, just specifying the address can cause unwanted
effects when multiple devices have the same IP address.  Because the
order of network devices in the system is never, and has never, been
guaranteed.

So the selection in this situation is essentially random because
you haven't given the kernel enough information to choose things
the way that you want it to.

--
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