Bug 1896151 - Offloaded vxlan decap rule not seen in ovs
Summary: Offloaded vxlan decap rule not seen in ovs
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux Fast Datapath
Classification: Red Hat
Component: openvswitch
Version: FDP 20.H
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Marcelo Ricardo Leitner
QA Contact: qding
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-09 20:15 UTC by Amit Supugade
Modified: 2022-06-02 16:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-02 16:53:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FD-933 0 None None None 2022-02-22 06:07:20 UTC

Description Amit Supugade 2020-11-09 20:15:47 UTC
Description of problem:
vxlan decap rule is not visible in ovs offloaded rules.

Version-Release number of selected component (if applicable):
openvswitch2.13-2.13.0-60.el8fdp.x86_64.rpm

How reproducible:
Always

Steps to Reproduce:
1. Add VFs 
2. Install and Configure OVS- Add VF and vxlan port
3. Enable offload
4. Add vxlan decap tc rule
5. Run traffic
6. Check: 'ovs-appctl dpctl/dump-flows type=tc --name' and 'ovs-appctl dpctl/dump-flows type=offloaded --name'

Actual results:
Offloaded vxlan decap rule not seen in output of 'ovs-appctl dpctl/dump-flows type=tc --name' and 'ovs-appctl dpctl/dump-flows type=offloaded --name'

Expected results:
Offloaded vxlan decap rule seen in ovs.

Additional info:
[root@netqe27 ~]# ovs-vsctl show
57ce3378-2da4-432d-9824-aa318d2443e6
    Bridge ovsbr0
        Port eth1
            Interface eth1
        Port eth0
            Interface eth0
        Port ovsbr0
            Interface ovsbr0
                type: internal
        Port vx1
            Interface vx1
                type: vxlan
                options: {dst_port="4789", key="100", local_ip="1.1.1.1", remote_ip="1.1.1.2"}
    ovs_version: "2.13.2"
[root@netqe27 ~]#
[root@netqe27 ~]# tc filter show dev vxlan_sys_4789 ingress
filter parent ffff: protocol ip pref 1 flower chain 0
filter parent ffff: protocol ip pref 1 flower chain 0 handle 0x1
  eth_type ipv4
  enc_dst_ip 1.1.1.1
  enc_src_ip 1.1.1.2
  enc_key_id 100
  enc_dst_port 4789
  in_hw in_hw_count 1
action order 1: tunnel_key  unset pipe
index 1 ref 1 bind 1

action order 2: mirred (Egress Redirect to device eth0) stolen
  index 1 ref 1 bind 1
 
[root@netqe27 ~]#

Comment 1 Marcelo Ricardo Leitner 2021-02-12 18:01:50 UTC
Hi Amit. I remember we had discussed this over irc a while back, but I don't remember our conclusion. Do you?
In any case, is this still reproduceable?


Note You need to log in before you can comment on or make changes to this bug.