From: Pablo Neira Ayuso <pablo@netfilter.org>
To: ratheesh kannoth <ratheesh.ksz@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
Netfilter mailing list <netfilter@vger.kernel.org>
Subject: Re: nft for bridge.
Date: Mon, 6 Oct 2025 12:03:27 +0200 [thread overview]
Message-ID: <aOOT7y0sfm74XGdg@calendula> (raw)
In-Reply-To: <CAGZFCEEdS7wjCs7S5_pESdMqsMqVezcMS_qmr=mVoKs_PQfNNg@mail.gmail.com>
On Sun, Oct 05, 2025 at 05:56:06PM +0530, ratheesh kannoth wrote:
> On Sun, Oct 5, 2025 at 5:15 PM Florian Westphal <fw@strlen.de> wrote:
> > You will need to figure that out yourself. Most of us a volunteers.
> Ok.
>
> >
> > > MY nft version : nftables v1.1.5 (Commodore Bullmoose #6)
> > > My kernel : kernel 6.6
> > >
> > > ADD cookie=18446462603462596360 (00:00:00:00:00:00,
> > > 192.168.11.200:30443) to (00:00:00:00:00:00, 192.168.9.100:35091) IPv4
> > > TCP
> > > ADD cookie=18446462603462596360 (00:00:00:00:00:00,
> > > 192.168.11.200:30443) to (00:00:00:00:00:00, 192.168.9.100:35091) IPv4
> > > TCP
> >
> > I don't even know where these messages come from.
> Sorry. THis is a debug print added in my function xxxx() to print
> flow tuple information.
> .ndo_setup_tc()
This is hardware offload trace.
What are you trying to do there?
> |
> |
> case TC_SETUP_FT:
> return flow_block_cb_setup_simple(type_data,
> &my_cb_list,
> my_setup_ft_block_ingress_cb,
> priv, priv, true);
> |
> |
> |
> my_setup_ft_block_ingress_cb() {
> struct flow_cls_offload *cls = type_data;
> switch (cls->command) {
> case FLOW_CLS_REPLACE:
> return xxxx(nic, cls);
> }
> |
> |
> |
> xxxx() {
> // parsing flow here
> if (flow_rule_match_key(rule, FLOW_DISSECTOR_KEY_ETH_ADDRS)) {
> struct flow_match_eth_addrs match;
> /// debug prints are here to print MAC address
> flow_rule_match_eth_addrs(rule, &match);
> }
> if (flow_rule_match_key(rule, FLOW_DISSECTOR_KEY_IPV4_ADDRS)) {
> struct flow_match_ipv4_addrs match;
> // debug prints are here to print IP address.
> flow_rule_match_ipv4_addrs(rule, &match);
> }
>
> }
prev parent reply other threads:[~2025-10-06 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 12:05 nft for bridge ratheesh kannoth
2025-08-18 14:20 ` Pablo Neira Ayuso
2025-10-05 7:03 ` ratheesh kannoth
2025-10-05 11:45 ` Florian Westphal
2025-10-05 12:26 ` ratheesh kannoth
2025-10-06 10:03 ` Pablo Neira Ayuso [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=aOOT7y0sfm74XGdg@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter@vger.kernel.org \
--cc=ratheesh.ksz@gmail.com \
/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