Public bug reported: This is a known limitation in the reference implementation of address scopes [1] in the L3 agent that a router cannot be connected to subnets with overlapping IPs even when the subnets are in different address scopes and, in theory, there should be no ambiguity. This was documented in the devref [2]. I'm filing this bug to capture ideas for possibly eliminating this limitation in the future.
[1] https://review.openstack.org/#/c/270001/ [2] http://docs.openstack.org/developer/neutron/devref/address_scopes.html#address-scopes ** Affects: neutron Importance: Wishlist Status: Confirmed ** Tags: address-scopes l3-ipam-dhcp ** Tags added: address-scopes l3-ipam-dhcp ** Changed in: neutron Importance: Undecided => Wishlist ** Changed in: neutron Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1543656 Title: Cannot connect a router to overlapping subnets with address scopes Status in neutron: Confirmed Bug description: This is a known limitation in the reference implementation of address scopes [1] in the L3 agent that a router cannot be connected to subnets with overlapping IPs even when the subnets are in different address scopes and, in theory, there should be no ambiguity. This was documented in the devref [2]. I'm filing this bug to capture ideas for possibly eliminating this limitation in the future. [1] https://review.openstack.org/#/c/270001/ [2] http://docs.openstack.org/developer/neutron/devref/address_scopes.html#address-scopes To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1543656/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp