[GBP-52] DestinationMapper has L3 flow that matches on L2 Created: 21/May/15 Updated: 15/Jun/15 Due: 05/Jun/15 Resolved: 15/Jun/15 |
|
| Status: | Resolved |
| Project: | groupbasedpolicy |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Thomas Bachman | Assignee: | Konstantin Blagov |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3317 |
| Priority: | High |
| Description |
|
DestinationMapper has an L3 flow that is matching on what should be L2 traffic. Pinging within a subnet on the same node was causing it to match on the L3 flow, which was decrementing the TTL. It should match on the L2 flow instead. |
| Comments |
| Comment by Keith Burns [ 01/Jun/15 ] |
|
See my comments GBP-33. That should fix this. |
| Comment by Konstantin Blagov [ 02/Jun/15 ] |
| Comment by Thomas Bachman [ 08/Jun/15 ] |
|
I believe this pastebin describes the problem, and potential solution: |
| Comment by Keith Burns [ 15/Jun/15 ] |
|
Misunderstanding. Traffic intra-subnet is not L2. If its an IP packet, it should match on the L3 flows. |