https://bugzilla.novell.com/show_bug.cgi?id=821879 https://bugzilla.novell.com/show_bug.cgi?id=821879#c24 Jiri Bohac <jbohac@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |jbohac@suse.com InfoProvider|jbohac@suse.com | --- Comment #24 from Jiri Bohac <jbohac@suse.com> 2013-05-31 18:30:55 CEST --- (In reply to comment #23)
https://bugs.launchpad.net/nova/+bug/1011134
so we really have 3 bugs:
1. VM interfaces on compute-hosts of SUSE Cloud 1.0 / OpenStack have hairpin_mode on, making them receive back their own traffic
I think you're correct. My understanding of VEPA is that the hairpin mode is there to allow the bridge to act as an uplink to another VEPA-mode bridge connected to the specific port. Setting the hairpin mode on a VSI is wrong. The above mentioned Ubuntu bug, has a link to an openstack "fix" for this: https://review.openstack.org/#/c/14017/ Instead of not setting the hairpin mode on the VSIs, they set up a packet filter to work around the problem. Am I missing something?
2. with the Host's bridge treating multicast like broadcast, VM's Linux IPv6 duplicate address detection receives its own sent packet and assumes some other host is using the same addr
Multicasts are treated like broadcasts by L2 switches - I don't see what's wrong with that. They just should not be looped back to the port they came from, which is what the hairpin misconfiguration causes. David Miller has rejected a patch trying to work around such a network misconfiguration: http://www.spinics.net/lists/netdev/msg127696.html I agree. I think it's a good thing that DAD detects duplicate addresses caused by a duplicate MAC address - something quite likely to happen with virtual machines.
3. 12.3's systemd assumes this means a failure in the network script and on udev upgrade the network is killed
Yes, this looks incorrect. For example, one may have more than one IPv6 addresses configured. One of them failing DAD should not be a reason to deconfigure the network -- the other addresses can still be used, IPv4 can be used. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.