qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, chris@linuxinfotag.de
Subject: Re: [Qemu-devel] Solution for qemu mcast / ipv6?
Date: Tue, 10 Mar 2009 23:16:14 +0000	[thread overview]
Message-ID: <200903102316.14749.paul@codesourcery.com> (raw)
In-Reply-To: <20090310203017.GC8323@silmor.de>

> > The bug is in the the mcast socket code. You need to fix that to stop
> > looping back all the packets.
>
> Do you mean the mcast socket code in qemu or the way IP_MULTICAST_LOOP
> works in the linux kernel?

I don't know. Hacking the generic vlan code is definitely the wrong solution 
though.

Paul

  reply	other threads:[~2009-03-10 23:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 15:50 [Qemu-devel] Solution for qemu mcast / ipv6? Christian Perle
2009-03-10 16:11 ` Paul Brook
2009-03-10 20:30   ` Christian Perle
2009-03-10 23:16     ` Paul Brook [this message]
2009-03-10 23:55       ` Jamie Lokier

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=200903102316.14749.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=chris@linuxinfotag.de \
    --cc=qemu-devel@nongnu.org \
    /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).