Date: Mon, 18 Jun 2007 11:21:45 +0100 From: "Bruce M. Simpson" <bms@incunabulum.net> To: Ian FREISLICH <ianf@clue.co.za> Cc: current@freebsd.org Subject: Re: Multicast problems Message-ID: <46765CB9.9020105@incunabulum.net> In-Reply-To: <E1I0E3b-0000kk-Ky@clue.co.za> References: <E1I0E3b-0000kk-Ky@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian FREISLICH wrote: > Hi > > I have a problem with quagga running on a CURRENT (15 June). It > appears that it's registering the multicast address on the wrong > interface. In fact, no matter which network I tell quagga to use > as the OSPF network, it always registers the multicast addresses > on the same incorrect vlan. It works with a May 24 kernel. > What is the format of the IP_ADD_MEMBERSHIP call used by the version of Quagga you are running to join the OSPF group? Does it use 'struct ip_mreqn' ? Does it use IP_ADD_SOURCE_MEMBERSHIP or IP_BLOCK_SOURCE ioctls? Other folks reported issues with the new code. As you're probably aware, ipv4 multicast group memberships must be bound to an interface. When they are not, the interface selected as the source for the IGMP join uses a routing table lookup on the group. The newer code changed to perform this lookup by interface index as well as by address, as interfaces used for ipv4 multicast traffic are generally assumed to have a protocol-level address. BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46765CB9.9020105>