lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 29 Dec 2018 13:42:17 +0100 From: Pablo Neira Ayuso <pablo@...filter.org> To: wenxu@...oud.cn Cc: netdev@...r.kernel.org, netfilter-devel@...r.kernel.org Subject: Re: [PATCH] nft_flow_offload: Fix the peer route get from wrong daddr On Fri, Dec 28, 2018 at 02:14:58PM +0800, wenxu@...oud.cn wrote: > From: wenxu <wenxu@...oud.cn> > > 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[dir].tuple.src.u3.ip Please, Cc netfilter-devel@...r.kernel.org for your netfilter patches. Thanks.
Powered by blists - more mailing lists