Re: [PATCH] nft_flow_offload: Fix the peer route get from wrong daddr

On Fri, Dec 28, 2018 at 02:14:58PM +0800, we...@ucloud.cn wrote: > From: wenxu > > For nat example: > client 1.1.1.7 ---> 2.2.2.7 which dnat to 10.0.0.7 server > > When syn_rcv pkt from server it get the peer(client->server) route > through daddr = ct->tuplehash[!dir].tuple.dst.u3.ip, the value

[PATCH] nft_flow_offload: Fix the peer route get from wrong daddr

From: wenxu For nat example: client 1.1.1.7 ---> 2.2.2.7 which dnat to 10.0.0.7 server When syn_rcv pkt from server it get the peer(client->server) route through daddr = ct->tuplehash[!dir].tuple.dst.u3.ip, the value 2.2.2.7 is not correct in this situation. it should be 10.0.0.7 ct->tuplehash[d