netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Brian Braunstein <linuxkernel@bristyle.com>,
	Shaun Jackman <sjackman@gmail.com>,
	netdev@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: Multicast and receive filtering in TUN/TAP
Date: Fri, 11 Jul 2008 17:01:38 +1000	[thread overview]
Message-ID: <200807111701.39070.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4876C357.3030708@qualcomm.com>

On Friday 11 July 2008 12:20:07 Max Krasnyansky wrote:
> >> I haven't looked at the virtio stuff much, I was assuming that the host
> >> side of it is still the TUN driver. Is it not ?
> >
> > Yes, the host side is still tun/tap. The problem is that qemu doesnt know
> > which multicast addresses are used inside the guest.
>
> Ah, now I see what you meant by virtio_net does not do multicast. I guess
> it should trivial to add. Rusty will clarify it I guess.

Yes, it could certainly be added; that's what feature bits are for :)

Cheers,
Rusty.

  reply	other threads:[~2008-07-11  7:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 22:58 Multicast and receive filtering in TUN/TAP Max Krasnyansky
2008-07-10  8:29 ` Christian Borntraeger
2008-07-10 16:57   ` Max Krasnyansky
2008-07-10 20:23     ` Christian Borntraeger
2008-07-11  2:20       ` Max Krasnyansky
2008-07-11  7:01         ` Rusty Russell [this message]
2008-07-11  8:01           ` Max Krasnyansky
2008-07-10 21:38 ` Shaun Jackman
2008-07-11  2:32   ` Brian Braunstein
2008-07-11  3:05     ` Max Krasnyansky
2008-07-11  3:01   ` Max Krasnyansky

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=200807111701.39070.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=borntraeger@de.ibm.com \
    --cc=linuxkernel@bristyle.com \
    --cc=maxk@qualcomm.com \
    --cc=netdev@vger.kernel.org \
    --cc=sjackman@gmail.com \
    --cc=virtualization@lists.linux-foundation.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).