[NETVIRT-613] New Netvirt classifier egress service should bind on egress ports not ingress ports Created: 10/Apr/17 Updated: 19/Oct/17 Resolved: 06/Jun/17 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Carbon |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Brady Johnson | Assignee: | Brady Johnson |
| 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: | 8193 |
| Priority: | High |
| Description |
|
Currently the new Netvirt classifier egress classifier service is binding on ingress ports, but according to discussions with the Genius folks, egress services should bind on egress ports. Since the Netvirt classifier cant know the possible egress port before-hand, for now it should just bind on all switch ports. This shouldnt cause any problems since it always checks for packets with NSH. Those packets that dont have NSH will be returned to the egress dispatcher. |
| Comments |
| Comment by Brady Johnson [ 10/Apr/17 ] |
|
|
| Comment by Brady Johnson [ 06/Jun/17 ] |
|
Fixed in stable/carbon: |