[ovs-dev] [PATCH] fix match issue for decap when the remote_ip=flow in userspace implementation
mengke.liu at intel.com
Fri Aug 14 01:19:08 UTC 2015
OK , Thanks.
From: Jesse Gross [mailto:jesse at nicira.com]
Sent: Friday, August 14, 2015 9:17 AM
To: Liu, Mengke
Cc: dev at openvswitch.org
Subject: Re: [ovs-dev] [PATCH] fix match issue for decap when the remote_ip=flow in userspace implementation
On Thu, Aug 13, 2015 at 6:19 PM, Mengke <mengke.liu at intel.com> wrote:
> From: mengke <mengke.liu at intel.com>
> In the test the bridge is configured with type "netdev" and the VXLAN port is configured with "options: remote_ip=flow options: key=flow", the VXLAN packets can't be matched for the rule (ovs-ofctl add-flow br-int "priority=200,in_port=2,tun_src=18.104.22.168, ip, actions= drop").
> After looking into the code, I found the reason is that when tunnel port is added, the match.wc.masks.nw_src argument is set "OVS_BE32_MAX" in "tnl_port_map_insert" function whether the "options: remote_ip" is set "flow" or constant IP_ADDR. This indicates the remote_ip is compared anyway, but the correct way is that the remote_ip should not be matched in "tnl_port_map_lookup" function when the "options: remote_ip" is set "flow".
> The patch with unit test is as following:
This has already been fixed. I guess you need to update your git repository?
More information about the dev