tun_gpe_np cannot be used as condition

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)
table=100, n_packets=0, n_bytes=0, priority=510,encap_eth_type=0x894f actions=resubmit(,17)

Packet always hits the second flow.

Environment

Operating System: All
Platform: All

Activity

Show:

Jaime Caamaño Ruiz October 16, 2017 at 8:37 AM

Done

Details

Assignee

Reporter

External issue ID

Components

Fix versions

Affects versions

Priority

Created September 27, 2017 at 10:05 AM
Updated February 27, 2018 at 9:39 AM
Resolved February 27, 2018 at 9:32 AM