From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arnd Bergmann <arnd@arndb.de>
Subject: Re: vhost-net todo list
Date: Thu, 17 Sep 2009 13:30:00 +0200
Message-ID: <200909171330.01414.arnd@arndb.de>
References: <20090916100438.GA30036@redhat.com> <200909161727.26153.arnd@arndb.de> <20090916164509.GB6034@redhat.com>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: anthony@codemonkey.ws, virtualization@lists.linux-foundation.org,
	kvm@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from moutng.kundenserver.de ([212.227.126.177]:64816 "EHLO
	moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755115AbZIQLag (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 17 Sep 2009 07:30:36 -0400
In-Reply-To: <20090916164509.GB6034@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Wednesday 16 September 2009, Michael S. Tsirkin wrote:
> > Also, I might not want to allow the user to open a
> > random random raw socket, but only one on a specific downstream
> > port of a macvlan interface, so I can filter out the data from
> > that respective MAC address in an external switch.
> 
> I agree. Maybe we can fix that for raw sockets, want me to
> add it to the list? :)

So far, I could not find any theoretical solution how to fix this,
but if you think it can be done, it would be good to have it on the
list somewhere.

	Arnd <><