<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - nftables - dynamic update for verdict map from the packet path"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1736#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - nftables - dynamic update for verdict map from the packet path"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1736">bug 1736</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>(In reply to dinhtrason from <a href="show_bug.cgi?id=1736#c2">comment #2</a>)
<span class="quote">> > I have seen rulesets which rely in meta mark to achieve this, thus, you use
> > the 'update' statement to add mappings using any key : meta mark. Then, use
> > the meta mark for the verdict map lookup to know what chain to visit in the
> > ruleset.
>
> Thanks for the suggestion.
>
> There is a restriction on using meta mark for this purpose because the
> packet mark has been used for an existing function (namely for masquerading)
> in my project.</span >
Are you fully using the 32 bits in the mark _only_ for masquerading?
If you use conntrack, then can you use connlabel?
<span class="quote">> It is also hard to have a unique meta mark for each target chain because its
> value will be generated by a hash of the target chain's ids (e.g. endpoint's
> destIP and destport) and collision is not avoidable with hashing function
> even the target chain's ids are different.</span >
I don't have access to your ruleset, I would need a sketch ruleset of you to
understand better what you are trying to do and make better suggestions.
Thanks.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>