Reviewed: https://review.openstack.org/287074 Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=6cb84079f9e791b7f2da6e65bc670c008e6f55fd Submitter: Jenkins Branch: master
commit 6cb84079f9e791b7f2da6e65bc670c008e6f55fd Author: YAMAMOTO Takashi <[email protected]> Date: Wed Mar 2 19:02:36 2016 +0900 Prevent binding IPv6 addresses to Neutron interfaces Closes-Bug: #1534652 Neutron change: Id879075f2d5ee42f8ff153e813e7519a4424447b Change-Id: I7ae0d1ad540e81c99681aa00d609f2ad1baa4511 ** Changed in: networking-midonet Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1534652 Title: Host machine exposed to tenant networks via IPv6 Status in networking-midonet: Fix Released Status in neutron: Fix Released Status in OpenStack Security Advisory: Incomplete Bug description: When creating a new interface Neutron creates interface and brings link up without disabling default IPv6 binding. By default Linux brings IPv6 link local addresses to all interfaces, this is different behavior than IPv4 where an administrator must explicitly configure an address on the interface. The is significantly exposed in LinuxBridgeManager ensure_vlan() and ensure_vxlan() where a new VLAN or VXLAN interface is created and set link up before being enslaved in the bridge. In the case of compute node joining and existing network, there is a time window in which VLAN or VXLAN interface is created and has connectivity to the tenant network before it has been enslaved in bridge. Under normal circumstances this time window is less than the time needed to preform IPv6 duplicate address detection, but under high load this assumption may not hold. I recommend explicitly disabling IPv6 via sysctl on each interface which will be attached to a bridge prior bringing the interface link up. This is already done for the bridge interfaces themselves, but should be done for all Neutron configured interfaces in the default namespace. This issue was referenced in https://bugs.launchpad.net/neutron/+bug/1459856 Related issue addressed being addressed in Nova: https://review.openstack.org/#/c/198054/ To manage notifications about this bug go to: https://bugs.launchpad.net/networking-midonet/+bug/1534652/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
