Cannot connect a router to overlapping subnets with address scopes
Bug #1543656 reported by
Carl Baldwin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Expired
|
Wishlist
|
Unassigned | ||
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:/
[2] http://
| tags: | added: address-scopes l3-ipam-dhcp |
| Changed in neutron: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| assignee: | nobody → Carl Baldwin (carl-baldwin) |
| assignee: | Carl Baldwin (carl-baldwin) → nobody |
Revision history for this message
| Armando Migliaccio (armando-migliaccio) wrote | #1 |
| Changed in neutron: | |
| status: | Confirmed → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in neutron: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
This bug is > 180 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.
If the bug is still valid, then update the bug status.