netdev - Re: AW: Problem receiving multicast/promiscuous-mode with kernel.2.6.24

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] [day] [month] [year] [list]

Message-ID: <OF1D96C632.7939DCD3-ON882573EC.0068DFE8-882573EC.006A04EB@us.ibm.com>
Date:	Mon, 11 Feb 2008 11:18:05 -0800
From:	David Stevens <dlstevens@...ibm.com>
To:	"Reither Robert" <Robert.Reither@...digital.at>
Cc:	netdev@...r.kernel.org
Subject: Re: AW: Problem receiving multicast/promiscuous-mode with kernel.2.6.24

Another relevant piece of information is what the socket is
bound to; "netstat -au" will tell you if you're bound to an address
that will match the incoming multicast packets.

If you suspect that the VLAN device is the problem, then it'd be
a good idea to try it on ordinary ethernet.

Re: imr_ifindex; using a "0" ifindex  and INADDR_ANY interface is valid,
but it usually doesn't make sense. What it means is "I don't care what
interface I join the group on". But you'll only receive multicasts
delivered to the group on the interface the kernel picks for you, which
often won't be the one you really want.

                                                +-DLS

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