Fischer, Anna wrote:
Subject: Re: tun/tap and Vlans
Lukas Kolbe wrote:
Right, I guess you'd see this with a real switch as well? Maybe
have
your guest send a packet out once in a while so the bridge can learn
its
MAC address (we do this after migration, for example).
Does this mean that it is not possible for having each tun device in
a
seperate bridge that serves a seperate Vlan? We have experienced a
strange problem that we couldn't yet explain. Given this setup:
Guest Host
kvm1 --- eth0 -+- bridge0 --- vlan1 \
| +-- eth0
kvm2 -+- eth0 -/ /
\- eth1 --- bridge1 --- vlan2 +
When sending packets through kvm2/eth0, they appear on both bridges
and
also vlans, also when sending packets through kvm2/eth1. When the
guest
has only one interface, the packets only appear on one bridge and one
vlan as it's supposed to be.
Can this be worked around?
This is strange. Can you post the command line you used to start kvm2?
This is exactly my scenario as well.
When QEMU sends packets through the tun interface coming from a VM then those will be passed to both tap devices of that VM. Simply because it doesn't know where to send the packet to. It just copies the buffer to the tap interface. The tap interface then eventually discards the packet if the MAC address doesn't match its own.
What you would need is a 1:1 mapping, e.g. one tun interface per tap device.
There ougt to be a 1:1 mapping thought the vlan parameter.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
