Date: Tue, 03 Jul 2007 15:59:09 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: "Bruce M. Simpson" <bms@FreeBSD.org> Cc: current@freebsd.org Subject: Re: Multicast problems [PATCH] Message-ID: <E1I5iuL-0006kH-6s@clue.co.za> In-Reply-To: Message from "Bruce M. Simpson" <bms@FreeBSD.org> of "Mon, 02 Jul 2007 12:34:46 %2B0100." <4688E2D6.8050608@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Bruce M. Simpson" wrote: > Ian FREISLICH wrote: > >> Has there been any outcome here, ie. have folks who were seeing problems > >> with multicast in the system tested this patch and found it to fix their > >> problems? > >> > > > > The quagga issue I have with the OSPF multicast address landing up > > on the wrong interface remains. > > > > Is Quagga still incorrectly using 0.0.0.0/8 to select a multicast source > interface by index? Bruce, sorry to require so much handholding. The quagga people almost haven't heard of FreeBSD and I'm not very familiar with multicast. I've already got it working with a private hack, but I'm not sure that I've done it right. Quagga no longer uses the mreq hack to pass the ifindex due to the presence of the imr_ifindex member to the struct ip_mreqn. Am I correct in my reading of the in_mcast.c that IP_ADD_MEMBERSHIP will ignore a value in imr_ifindex and use the address in imr_address And that it is no longer possible to add a multicast membership using the ifindex? Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1I5iuL-0006kH-6s>