On Jan14 19:24, Paolo Bonzini wrote:
> See http://lists.gnu.org/archive/html/qemu-devel/2013-03/msg04279.html
> and http://lists.gnu.org/archive/html/qemu-devel/2012-10/msg02149.html
> for previous discussions on this topic.
Thanks for pointing me this out, it's now clear.
--
William
signature.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 14/01/2014 18:40, William Dauchy ha scritto:
>>> I think this was nacked already in the past. You would need to
>>> implement some kind of ACL system like the one that is in place
>>> for bridges. Without it, for example, you could hijack
>>> exi
On 01/14/2014 10:15 AM, William Dauchy wrote:
> this will permit to specify an interface prefix to the tap instead of the
> default one ("tap")
> this functionnality is useful when you need an easy way to find the
s/functionnality/functionality/
> interfaces attached to a given virtual machine
>
Hello Paolo,
Thanks for your quick reply.
On Jan14 18:31, Paolo Bonzini wrote:
> I think this was nacked already in the past. You would need to
> implement some kind of ACL system like the one that is in place for
> bridges. Without it, for example, you could hijack existing iptables rules.
I
this will permit to specify an interface prefix to the tap instead of the
default one ("tap")
this functionnality is useful when you need an easy way to find the
interfaces attached to a given virtual machine
example:
-net bridge,prefix=tapvmA. -net bridge,prefix=tapvmA.
will create `tapvmA.0` a
Il 14/01/2014 18:15, William Dauchy ha scritto:
> this will permit to specify an interface prefix to the tap instead of the
> default one ("tap")
> this functionnality is useful when you need an easy way to find the
> interfaces attached to a given virtual machine
>
> example:
> -net bridge,prefi
