Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Jun 2007 08:37:25 -0400 (EDT)
From:      Daniel Eischen <deischen@freebsd.org>
To:        "Bruce M. Simpson" <bms@incunabulum.net>
Cc:        Ian FREISLICH <ianf@clue.co.za>, current@freebsd.org
Subject:   Re: Multicast problems
Message-ID:  <Pine.GSO.4.64.0706180833080.23884@sea.ntplx.net>
In-Reply-To: <46765CB9.9020105@incunabulum.net>
References:  <E1I0E3b-0000kk-Ky@clue.co.za> <46765CB9.9020105@incunabulum.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Jun 2007, Bruce M. Simpson wrote:
>
> 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.

What happens when you join a group without an interface (INADDR_ANY)?
Assume there is no route for the multicast group.  Does the new code
select the interface that the default route is on?

This is the behavior we expect to see and what occurs on other OSs.

-- 
DE



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0706180833080.23884>