netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Crosser <crosser@average.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ebtables: load-on-demand extensions
Date: Fri, 19 Jun 2020 15:45:57 +0200	[thread overview]
Message-ID: <874fd8a8-dfd2-f6c3-ae01-61884ca9bcff@average.org> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2006161830320.16707@n3.vanv.qr>


[-- Attachment #1.1: Type: text/plain, Size: 1490 bytes --]

On 6/16/20 6:33 PM, Jan Engelhardt wrote:

>>> Why not make a patch to publicly expose the skb's data via nft_meta?
>>> No more custom modules, no more userspace modifications [..]
>>
>> For our particular use case, we are running the skb through the kernel
>> function `skb_validate_network_len()` with custom mtu size [..]
> 
> I find no such function in the current or past kernels. Perhaps you could post
> the code of the module(s) you already have, and we can assess if it, or the
> upstream ideals, can be massaged to make the code stick.

I really really don't see our module being useful for anyone else! Even
for us, it's just a stopgap measure, hopefully to be dropped after a few
months. That said, I believe that the company will have no objections
against publishing it. I've uploaded initial (untested) code on github
here https://github.com/crosser/ebt-pmtud, in case anyone is interested.

On the other hand, in my opinion there will always be a use case for
custom kernel modules acting as extensions to netfilter. Alternative, in
most cases, would be a standalone kernel module, not using netfilter
infrastructure. But netfilter infrastructure is so useful and
convenient, it would be a shame to lose it!

Anyway, I would like to suggest a patch to `ebtables-nft` that
introduces `-m` option like in `iptables`. Turns out that it's only a
few lines, including manpage update! I will send the patch in a separate
email.

Regards,

Eugene


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-06-19 13:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 14:48 ebtables: load-on-demand extensions Eugene Crosser
2020-06-16 15:21 ` Jan Engelhardt
2020-06-16 15:54   ` Eugene Crosser
2020-06-16 16:33     ` Jan Engelhardt
2020-06-19 13:45       ` Eugene Crosser [this message]
2020-06-19 15:15         ` Pablo Neira Ayuso
2020-06-19 16:21           ` Eugene Crosser
2020-06-20 10:34           ` Expose skb_gso_validate_network_len() [Was: ebtables: load-on-demand extensions] Eugene Crosser
2020-06-20 11:04             ` Florian Westphal
2020-06-20 21:16               ` Eugene Crosser
2020-06-21  3:24                 ` Florian Westphal
2020-06-21 10:03                   ` Jan Engelhardt
2020-06-21 18:48                     ` Eugene Crosser
2020-06-21 23:52                     ` Florian Westphal
2020-06-22  4:50                       ` Jan Engelhardt
2020-06-22  7:41                         ` Eugene Crosser

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=874fd8a8-dfd2-f6c3-ae01-61884ca9bcff@average.org \
    --to=crosser@average.org \
    --cc=jengelh@inai.de \
    --cc=netfilter-devel@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).