Serge,
$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.001a64b33b10 no eth0
vnet0
vnet1
virbr0 8000.000000000000 yes
In case it's not obvious, br0 is the bridge I manually created today.
virbr0 is (i think) the bridge created by libvirt which I had used
previously. virbr0 was never bound to eth0 - it was used for the
'virtual network' scenario.
Attached it the output of iptables -L as of right now, but I *think*
this output may not reflect the same configuration when libvirt is
managing the virtual network. In the case I think libvirt manipulates
the network configuration, including iptables, to support the virtual
LAN. We're in the middle of a test build on the guest which I'd prefer
not to interrupt, but if you'd like me to run another test with the
networking switched back to virtual LAN, I can do that later today. I
can also recapture iptables -L at that point.
brian
** Attachment added: "iptables -L"
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/616064/+attachment/1521218/+files/iptables_L.txt
--
Broken networking in kvm guests
https://bugs.launchpad.net/bugs/616064
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
