netdev - Re: [PATCH 3/3] bonding: Improve IGMP join processing

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: <bdfc5d6e0703061244q2bc9403cs7c6321136fd8e4e0@mail.gmail.com>
Date:	Tue, 6 Mar 2007 15:44:27 -0500
From:	"Andy Gospodarek" <andy@...yhouse.net>
To:	"Jay Vosburgh" <fubar@...ibm.com>
Cc:	"Brian Haley" <brian.haley@...com>, netdev@...r.kernel.org,
	bonding-devel@...ts.sourceforge.net
Subject: Re: [PATCH 3/3] bonding: Improve IGMP join processing

On 3/6/07, Jay Vosburgh <fubar@...ibm.com> wrote:
> Brian Haley <brian.haley@...com> wrote:
>
> >Andy Gospodarek wrote:
> >> If we are easily able to differentiate between the multicast addresses
> >> in the mc_list as to which are for ipv4 and which are for ipv6 then it
> >> would be easy to call-out to something in the ipv6 mcast code when
> >> needed instead of always calling out to ipv4 code.
> >
> >I've been unable to figure out exactly what you're referring to in the
> >code (bond_main.c), it seems to failover all multicast addresses,
> >regardless of what address family they are.  I might have missed something
> >in 4K lines of code though?
>
>         I believe Andy is talking about bond_resend_igmp_join_requests
> being only effective for IGMP v4 and not IGMP v6.  The reason being that
> there is (a) no discrimination between v4 and v6 multicast addresses,
> and (b) for the v6 case, there's no "rejoin" type function as was
> created for IPv4 with the patch.
>

/me nods
-
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