From: Avi Kivity <avi@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: dlaor@redhat.com, qemu-devel@nongnu.org,
Mark McLoughlin <markmc@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: [PATCH 1/5] virtio-net: Allow setting the MAC address via set_config
Date: Thu, 15 Jan 2009 15:41:48 +0200 [thread overview]
Message-ID: <496F3D1C.4020605@redhat.com> (raw)
In-Reply-To: <20090115131249.GD32368@shareable.org>
Jamie Lokier wrote:
> Dor Laor wrote:
>
>> 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.
>>
>
> Although it can create network problems, sometimes it is also wanted.
>
> I think if you want to restrict the guests's ability to break the
> network by changing its MAC, it would be appropriate to have an option
> to completely lock down the MAC so the guest can't change its MAC at all.
>
I don't think locking down the MAC is very useful; the guest can still
fake its IP address.
If the admin wants to lock down the guest, they should use netfilter
(and live with the performance hit).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-01-15 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 21:23 [PATCH 1/5] virtio-net: Allow setting the MAC address via set_config Alex Williamson
2009-01-14 10:05 ` Dor Laor
2009-01-14 15:34 ` Alex Williamson
2009-01-14 16:41 ` [Qemu-devel] " Jamie Lokier
2009-01-14 22:06 ` Dor Laor
2009-01-14 22:14 ` Paul Brook
2009-01-15 13:11 ` Jamie Lokier
2009-01-15 13:12 ` Jamie Lokier
2009-01-15 13:41 ` Avi Kivity [this message]
2009-01-18 9:37 ` Dor Laor
2009-01-18 9:42 ` Avi Kivity
2009-01-14 22:08 ` Dor Laor
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=496F3D1C.4020605@redhat.com \
--to=avi@redhat.com \
--cc=dlaor@redhat.com \
--cc=jamie@shareable.org \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--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