<html>
<head>
<base href="https://bugzilla.netfilter.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - tproxy with nftables collides with nat entries"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1773#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - tproxy with nftables collides with nat entries"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1773">bug 1773</a>
from <span class="vcard"><a class="email" href="mailto:pablo@netfilter.org" title="Pablo Neira Ayuso <pablo@netfilter.org>"> <span class="fn">Pablo Neira Ayuso</span></a>
</span></b>
<pre>not applicable, for the record see:
<a href="https://lore.kernel.org/netfilter-devel/ZuQpbnjAoutXEFUj@orbyte.nwl.cc/T/">https://lore.kernel.org/netfilter-devel/ZuQpbnjAoutXEFUj@orbyte.nwl.cc/T/</a>
a patch to document this behaviour has been proposed instead.
I remembered that tproxy is not terminal in nftables to fix the hack in
xt_TPROXY to mangle the packet mark. nftables is more flexible in this regard
because user could want to make more actions on the packet after validating
that the socket is transparent.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>