[NETVIRT-928] tun_gpe_np cannot be used as condition Created: 27/Sep/17 Updated: 27/Feb/18 Resolved: 27/Feb/18 |
|
| Status: | Verified |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Nitrogen |
| Fix Version/s: | Nitrogen-SR2 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Manuel Buil | Assignee: | Jaime Caamaño Ruiz |
| 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: | 9220 |
| Description |
|
According to Yi Yang, tun_gpe_np is lost after decapsulation because there isn’t a way to save it in tunnel metadata in OVS vxlan-gpe implementation. Therefore, we cannot use it to decide if a packet is coming from a tunnel or internally, as it is done right now in table=100: table=100, n_packets=0, n_bytes=0, priority=510,tun_gpe_np=0x3 actions=resubmit(,83) Packet always hits the second flow. |
| Comments |
| Comment by Jaime Caamaño Ruiz [ 16/Oct/17 ] |