From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LNDui-0006iy-Vz for qemu-devel@nongnu.org; Wed, 14 Jan 2009 17:08:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LNDui-0006iR-2N for qemu-devel@nongnu.org; Wed, 14 Jan 2009 17:08:40 -0500 Received: from [199.232.76.173] (port=49630 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNDuh-0006iO-Ra for qemu-devel@nongnu.org; Wed, 14 Jan 2009 17:08:39 -0500 Received: from mx2.redhat.com ([66.187.237.31]:43152) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LNDuh-0005CH-4G for qemu-devel@nongnu.org; Wed, 14 Jan 2009 17:08:39 -0500 Message-ID: <496E61F0.8060605@redhat.com> Date: Thu, 15 Jan 2009 00:06:40 +0200 From: Dor Laor MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 1/5] virtio-net: Allow setting the MAC address via set_config References: <1231881829.9095.191.camel@bling> <496DB8D1.2070101@redhat.com> <1231947298.7109.262.camel@lappy> <20090114164155.GA6431@shareable.org> In-Reply-To: <20090114164155.GA6431@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: dlaor@redhat.com, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Mark McLoughlin , kvm Jamie Lokier wrote: > Alex Williamson wrote: > >>> What if the guest will chose the host's mac? >>> Thinking about it, I don't think we should test that. >>> A concerned host mgmt app can add ebtables roles for such a case. >>> >>> Maybe we can optionally allow/deny it? >>> >> What's the topology you're thinking of that the virtio-net MAC is also >> the host MAC? I typically use a bridge with a tap device, so the >> virtio-net MAC is isolated from the host. Thanks, >> > > For example you might forward IPX packets to the guest and IP/ARP to > the host, using an ebtables rule to distinguish them. From the > outside, it would look equivalent to a single host processing both IPX > and IP. > > -- Jamie > > That's a nice common scenario ;) What I meant is that if we allow the guest to change his mac address, it can deliberately change it to other hosts/guests mac and thus create networking problems. Although guest can always mangle packets, maybe it worth enforcing these macs for the guest. Thanks, Dor