From: team lnx <teamlnxi8@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: xdp-newbies@vger.kernel.org
Subject: Re: xdp forward issue
Date: Mon, 19 Dec 2022 20:22:57 -0800 [thread overview]
Message-ID: <CAOLRUnApBOYXXhOvV_2qzELQD+bTWERqEDOR9sgOYrTiU=J_MQ@mail.gmail.com> (raw)
In-Reply-To: <37d5bcac-4b63-c9f1-280a-caf7d303c309@gmail.com>
Thank you, it helped !!
On Tue, Dec 6, 2022 at 7:05 PM David Ahern <dsahern@gmail.com> wrote:
>
> On 12/6/22 5:26 PM, team lnx wrote:
> >
> > Sure, I did search for it and read some article but found that
> > BPF_FIB_LKUP_RET_NOT_FWDED means packets
> > are not forwarded and only unicast are forwarded. Verified prog id and
> > map id using bpftool to confirm if it has any issue
>
> ok, so this one:
>
> if (res.type != RTN_UNICAST)
> return BPF_FIB_LKUP_RET_NOT_FWDED;
>
> and the discussion about local return. If this is really supposed to be
> forwarding and not local delivery, the next step is verifying the
> routing tables and fib lookup parameters:
> perf record -e fib:* -a
> <run test>
> ctrl-c
> perf script
>
> the tracepoints will show you input variables, table ids and result.
>
> >
> > interface details:
> > prog/xdp id: 4
> > map_ids: 1
> > btf_id: 7
> >
> > ./bpftool map show id 1
> > 1: devmap name xdp_tx_ports flags 0x80
> >
> > Any hints or suggestions on debugging this issue would be helpful !
> >
> > Thanks
>
prev parent reply other threads:[~2022-12-20 4:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 16:43 xdp forward issue team lnx
2022-12-06 20:10 ` David Ahern
2022-12-06 20:36 ` team lnx
2022-12-06 21:42 ` David Ahern
2022-12-07 0:26 ` team lnx
2022-12-07 3:05 ` David Ahern
2022-12-20 4:22 ` team lnx [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='CAOLRUnApBOYXXhOvV_2qzELQD+bTWERqEDOR9sgOYrTiU=J_MQ@mail.gmail.com' \
--to=teamlnxi8@gmail.com \
--cc=dsahern@gmail.com \
--cc=xdp-newbies@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).