From: Christian Deacon <gamemann@gflclan.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>, xdp-newbies@vger.kernel.org
Subject: Re: XDP Software Issue - Payload Matching
Date: Tue, 14 Jul 2020 10:58:55 -0500 [thread overview]
Message-ID: <4581875c-d5af-3da5-bf01-ce3e404c94dc@gflclan.com> (raw)
In-Reply-To: <87tv08j96h.fsf@toke.dk>
Hey Toke,
I apologize for the long delay on this. A lot has been going on recently!
I attempted to match payload data using the packet's payload as the BPF
map key. Unfortunately, I didn't have any success with this. I stored my
findings here from last month:
https://github.com/gamemann/XDP-Dynamic-Payload-Matching#section-methodfour-fail
I'd assume I may be missing something here, though.
I saw another XDP mailing list thread pop up recently regarding matching
TCP payload data. I believe this may be what they're trying to achieve
(being able to match dynamic payload data with XDP).
I was wondering if you had any other ideas on how we can match packet
payload data against a BPF map.
Thank you for your time!
On 5/22/2020 10:12 AM, Toke Høiland-Jørgensen wrote:
> Christian Deacon <gamemann@gflclan.com> writes:
>
>> Hey Toke,
>>
>> I apologize for the delay on this. I've been working on a couple other
>> XDP/BPF projects recently.
>>
>> Thank you for the information you provided!
>>
>> Do you know of any open-source projects/examples that uses the method
>> you're suggesting to compare packet data without using for/while loops?
>> I haven't tried implementing the code yet, but I'm not entirely sure how
>> I am going to do so.
> Well, having a map that uses IP addresses as lookup key is kinda the
> same, I suppose, it's just a very limited part of the payload that's
> being used as the key. But other than that, no, please consider this a
> completely off-the-top-of-my-head idea with no warranties, implied or
> otherwise :)
>
> -Toke
>
next prev parent reply other threads:[~2020-07-14 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 13:57 XDP Software Issue - Payload Matching Christian Deacon
2020-05-11 10:41 ` Toke Høiland-Jørgensen
2020-05-11 18:40 ` Christian Deacon
2020-05-12 14:28 ` Toke Høiland-Jørgensen
2020-05-13 13:25 ` Christian Deacon
2020-05-13 14:42 ` Toke Høiland-Jørgensen
2020-05-22 14:49 ` Christian Deacon
2020-05-22 15:12 ` Toke Høiland-Jørgensen
2020-07-14 15:58 ` Christian Deacon [this message]
2020-07-14 20:48 ` Toke Høiland-Jørgensen
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=4581875c-d5af-3da5-bf01-ce3e404c94dc@gflclan.com \
--to=gamemann@gflclan.com \
--cc=toke@redhat.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 NNTP newsgroup(s).