From: Glen Huang <heyhgl@gmail.com>
To: Balazs Scheidler <bazsi77@gmail.com>
Cc: "\"Eckl, Máté\"" <ecklm94@gmail.com>, netfilter@vger.kernel.org
Subject: Re: Why tproxy to 127.0.0.1:port doesn't make packets go through the input chain with iifname lo?
Date: Mon, 22 May 2023 22:52:11 +0800 [thread overview]
Message-ID: <D8DF58A3-003F-4C57-9FF3-937E2246B7A0@gmail.com> (raw)
In-Reply-To: <CAKcfE+bewEQq2BPNAwaHM99NDwmDMRtu9qPcAdkC=5J5k+7tvg@mail.gmail.com>
> Without "mark set" your normal routing tables would be used for the routing decision.
I thought you meant the whole ip rule was unnecessary. Your new detailed explanation made everything crystal clear, thank you!
> Using the mark should work.
Thanks for the tip, mark works flawlessly.
> It should not do that. That's probably an explicit rule that does it.
It seems nft doesn’t always print mark in the trace log, I mistakenly thought it got cleared. Like previously mentioned, matching the mark value works flawlessly.
Thanks again for your help Bazsi, and thanks for writing the tproxy target, it helped me tremendously.
Regards,
Glen
prev parent reply other threads:[~2023-05-22 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 7:24 Why tproxy to 127.0.0.1:port doesn't make packets go through the input chain with iifname lo? Glen Huang
2023-05-20 14:19 ` Eckl, Máté
[not found] ` <CAKcfE+bo1hJXF4M1rm2KfWGZ7meYKtfWfGBd6+Rktd2XiUMfdg@mail.gmail.com>
2023-05-20 23:07 ` Glen Huang
[not found] ` <CAKcfE+bewEQq2BPNAwaHM99NDwmDMRtu9qPcAdkC=5J5k+7tvg@mail.gmail.com>
2023-05-22 14:52 ` Glen Huang [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=D8DF58A3-003F-4C57-9FF3-937E2246B7A0@gmail.com \
--to=heyhgl@gmail.com \
--cc=bazsi77@gmail.com \
--cc=ecklm94@gmail.com \
--cc=netfilter@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).