From: PJ Waskiewicz [EMAIL PROTECTED]
Date: Tue, 06 Nov 2007 07:25:47 -0800
The socket option for packet sockets to return the original ifindex instead
of the bonded ifindex will not match multicast traffic. Since this socket
option is the most useful for layer 2 traffic and multicast
From: PJ Waskiewicz [EMAIL PROTECTED]
Date: Tue, 06 Nov 2007 07:25:47 -0800
The socket option for packet sockets to return the original ifindex instead
of the bonded ifindex will not match multicast traffic. Since this socket
option is the most useful for layer 2 traffic and multicast
The socket option for packet sockets to return the original ifindex
instead of the bonded ifindex will not match multicast
traffic. Since
this socket option is the most useful for layer 2 traffic and
multicast traffic, make the option multicast-aware.
Signed-off-by: Peter P
From: Waskiewicz Jr, Peter P [EMAIL PROTECTED]
Date: Wed, 7 Nov 2007 03:00:42 -0800
In any event, the only thing this could affect is if the option is
set on the socket, which shouldn't be very often at all.
Any idea how many programs set this option and which
ones? You obviously noticed, so
-Original Message-
From: David Miller [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 07, 2007 3:52 AM
To: Waskiewicz Jr, Peter P
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] [AF_PACKET]: Allow multicast traffic to
be caught by ORIGDEV when bonded
From: Waskiewicz Jr
The socket option for packet sockets to return the original ifindex instead
of the bonded ifindex will not match multicast traffic. Since this socket
option is the most useful for layer 2 traffic and multicast traffic, make
the option multicast-aware.
Signed-off-by: Peter P Waskiewicz Jr [EMAIL
