From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) Subject: Re: [patch 0/2][NETNS49][IPV4][IGMP] activate multicast per namespace Date: Fri, 12 Oct 2007 12:50:20 -0600 Message-ID: References: <20071012171013.105324992@mai.toulouse-stg.fr.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <20071012171013.105324992-WECHFHqYCmGD/CxQmPlnQ0FT0OZdM7KVQQ4Iyu8u01E@public.gmane.org> (Daniel Lezcano's message of "Fri, 12 Oct 2007 19:10:13 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Daniel Lezcano Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org List-Id: containers.vger.kernel.org Daniel Lezcano writes: > The following patches activate the multicast sockets for > the namespaces. The results is a traffic going through > differents namespaces. So if there are several applications > listenning to the same multicast group/port, running in > different namespaces, they will receive multicast packets. At a first glance this feels wrong. I don't see any per namespace filtering of multicast traffic. Unless the multicast traffic is routed/bridged between namespaces it should be possible to send multicast traffic in one namespace and listen for that same traffic in another namespace and not get it. Eric