[LISPMAP-164] Negative mapping in SB masking overlapping more specific positive added later to NB Created: 23/Aug/17 Updated: 20/Mar/18 Resolved: 12/Sep/17 |
|
| Status: | Resolved |
| Project: | lispflowmapping |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | Oxygen |
| Type: | Bug | Priority: | Highest |
| Reporter: | Lori Jakab | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 9037 |
| Priority: | Normal |
| Description |
|
Suppose we have 192.167.0.0/16 and 192.169.0.0/16 in NB. A lookup for 192.168.0.1 then generates a negative entry for 192.168.0.0/16 in SB. A new positive for 192.168.1.0/24 is added to NB. Now, a request for 192.168.0.1 should return 192.168.0.0/24. However, NB still returns null, and SB has the 192.168.0.0/16 large prefix as a negative, which will be returned. If an xTR installs the large prefix, it will not send requests for 192.168.1.0/24, thus completely masking/blackholing that prefix. |
| Comments |
| Comment by Lori Jakab [ 05/Sep/17 ] |
|
Fix proposed: https://git.opendaylight.org/gerrit/#/c/62690/ |