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: Sun, 31 Jul 2016 21:00:56 +0200 From: Florian Westphal <fw@...len.de> To: fxp2001640163@...il.com Cc: pablo@...filter.org, kaber@...sh.net, kadlec@...ckhole.kfki.hu, netfilter-devel@...r.kernel.org, coreteam@...filter.org, netdev@...r.kernel.org, Xiaoping Fan <xfan@...eaurora.org> Subject: Re: [PATCH 2/3] netfilter: nat: snat created in route process just apply to routed traffic fxp2001640163@...il.com <fxp2001640163@...il.com> wrote: > From: Xiaoping Fan <xfan@...eaurora.org> > > In some situations, packet goes through Linux twice, one for bridging, > another for routing. If snat is created in bridging process, that means Hmm, but SNAT happens in POSTROUTING. Where can we enter routing path after bridge went though postrouting...? Normally if bridge packet has local dst mac kb traversal is: bridge prerouting -> bridge input -> ipv4 prerouting (hook invocation suppressed via bridge netfilter sabotage hook) Depending on route table we then end up in ipv4 input (again suppressed) or in forward and postrouting. What is the issue, exactly?
Powered by blists - more mailing lists