public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Vincent Li <vincent.mc.li@gmail.com>
To: development@lists.ipfire.org
Subject: Enable eBPF XDP/TC kernel feature for IPFire
Date: Tue, 09 Apr 2024 10:36:41 -0700	[thread overview]
Message-ID: <CAK3+h2wnTKji1sdWJRTP3Lj7ww-aC-g1cpK+n-4m_Sk4=VB5WA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 688 bytes --]

Hi,

I have been working on enabling eBPF XDP/TC kernel feature for IPFire,
please refer to
https://upload.wikimedia.org/wikipedia/commons/3/37/Netfilter-packet-flow.svg
for where XDP fit in Linux network datapath, XDP will not interfere
with existing IPFire firewall rules. XDP is especially good at DDoS
packet filtering at high speed, see
https://netdevconf.info/0x15/slides/30/Netdev%200x15%20Accelerating%20synproxy%20with%20XDP.pdf

I think we only need to enable XDP/TC network filtering capability
without eBPF tracing capability which some users are concerned about
potential host security information leaks.

Please let me know what you think, thanks!

Vincent

             reply	other threads:[~2024-04-09 17:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 17:36 Vincent Li [this message]
2024-04-10  9:04 ` Adolf Belka
2024-04-10 14:11   ` Vincent Li
2024-04-10 15:17     ` Peter Müller
2024-04-10 18:01       ` Vincent Li
2024-04-17 16:07         ` Michael Tremer
2024-04-17 22:36           ` Vincent Li
2024-04-17 22:41             ` Vincent Li
2024-04-18  8:57             ` Michael Tremer
2024-04-18 15:21               ` Vincent Li
2024-04-18 21:13                 ` Michael Tremer
2024-04-19  0:17                   ` Vincent Li
2024-04-24 15:28                     ` Michael Tremer
     [not found] <CAK3+h2x_Qx3DtbKGPEexfjfEeoEJVnNhOxZGJMkSMYJZW=qhMg@mail.gmail.com>
2024-04-25 10:08 ` Michael Tremer

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='CAK3+h2wnTKji1sdWJRTP3Lj7ww-aC-g1cpK+n-4m_Sk4=VB5WA@mail.gmail.com' \
    --to=vincent.mc.li@gmail.com \
    --cc=development@lists.ipfire.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