qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Samuel Thibault <samuel.thibault@labri.fr>,
	ped@listes.subiron.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PER] Re:  socket, mcast looping back frames -> IPv6 broken
Date: Mon, 11 Mar 2013 09:36:14 +0100	[thread overview]
Message-ID: <20130311083614.GA28434@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20130310200152.GY6036@type.youpi.perso.aquilenet.fr>

On Sun, Mar 10, 2013 at 09:01:52PM +0100, Samuel Thibault wrote:
> Stefan Hajnoczi, le Wed 06 Mar 2013 13:29:37 +0100, a écrit :
> > > What do people think about it?
> > 
> > We should fix the layer that introduces the problem.  Therefore I think
> > the fix needs to be net/socket.c.
> > 
> > Unfortunately net/socket.c does not have the concept of a link-layer
> > address, so we cannot easily filter out multicast packets coming from
> > our NIC's address.
> > 
> > Are you aware of a way to filter out just the packets sent by *this*
> > process?
> 
> So in the end I couldn't find any way (even Linuxish) to distinguish
> packets coming from self or from other qemus running on the same host,
> event with recvmsg etc.
> 
> So, it seems if we want to fix the issue we'll have to filter by source
> MAC address.  Since the guest can actually change its own MACs, we'd
> have to learn them on the fly.  We can also implement some aging on the
> entries in case the user migrates a MAC from a VM to another.

Yes, the guest may use multiple MACs at the same time (e.g. nested
virtualization).

> Otherwise we may just document that one has to disable Duplicate Address
> Detection to get IPv6 working :/

Seems like this might be the only way for now.

Stefan

  reply	other threads:[~2013-03-11  8:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 16:35 [Qemu-devel] socket,mcast looping back frames -> IPv6 broken Samuel Thibault
2013-03-06 12:29 ` Stefan Hajnoczi
2013-03-06 13:15   ` [Qemu-devel] [PER] Re: socket, mcast " Samuel Thibault
2013-03-07  9:38     ` Stefan Hajnoczi
2013-03-07 17:14       ` Samuel Thibault
2013-03-08  8:43         ` Stefan Hajnoczi
2013-03-08  9:08           ` Samuel Thibault
2013-03-08 12:47             ` Samuel Thibault
2013-04-01  6:35               ` Mike Lovell
2013-04-01  9:32                 ` Samuel Thibault
2013-04-08 11:12                   ` Stefan Hajnoczi
2013-03-10 20:01   ` Samuel Thibault
2013-03-11  8:36     ` Stefan Hajnoczi [this message]
2013-04-01  0:12       ` [Qemu-devel] [PATCH] Document mcast+ipv6 (Was: Re: socket, mcast looping back frames -> IPv6 broken) Samuel Thibault
2013-04-08 11:13         ` Stefan Hajnoczi
2013-04-08 12:11           ` Samuel Thibault

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130311083614.GA28434@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=ped@listes.subiron.org \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@labri.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).