From: Volodymyr Litovka <doka@funlab.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: doka@funlab.cc, netfilter@vger.kernel.org
Subject: Re: nftables / DHCP / NAT
Date: Tue, 31 Oct 2023 22:26:46 +0100 [thread overview]
Message-ID: <0d0602ef-362a-4150-b8ae-ca46ff63dea3@funlab.cc> (raw)
In-Reply-To: <ZUEJrwuwr0tw+TNL@calendula>
Hi Pablo,
On 10/31/23 15:05, Pablo Neira Ayuso wrote:
> I see no duplicates, see below.
thank a lot for the help. You were right and, finally, it was my
mistake. The difference is that when I use 'ip daddr set x.x.x.x' it
rewrites packet and receiving host is the final destination, while 'fwd'
is frame forwarding with original ip header so this packet, being
received, was forwarded to the original destination and that's why I
seen two copies - one from ingress, another one - from egress.
Thanks again!
--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison
prev parent reply other threads:[~2023-10-31 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <df94652d-d611-4713-963a-911d6b7ef986@funlab.cc>
2023-10-30 8:41 ` nftables / DHCP / NAT Pablo Neira Ayuso
2023-10-30 11:58 ` Volodymyr Litovka
[not found] ` <54fda956-92bd-4c14-b0e5-29445b53f04a@funlab.cc>
2023-10-30 16:40 ` Pablo Neira Ayuso
2023-10-30 22:20 ` Volodymyr Litovka
2023-10-31 14:05 ` Pablo Neira Ayuso
2023-10-31 21:26 ` Volodymyr Litovka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0d0602ef-362a-4150-b8ae-ca46ff63dea3@funlab.cc \
--to=doka@funlab.cc \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox