public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Kernel patch - ERROR KCFG= FAIL
Date: Mon, 25 Feb 2019 14:32:27 +0100	[thread overview]
Message-ID: <aa85252f34fc86dca3aa8b92d3ac51a78cf80401.camel@ipfire.org> (raw)
In-Reply-To: <679D975C-8023-4625-9ECA-7AEFF44A6302@ipfire.org>

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

Hi,
just a fast feedback from here.

On Di, 2019-02-19 at 16:20 +0000, Michael Tremer wrote:
> 
> So, please toy around with (probably the ntop version of) nDPI. I
> would be interested to see where it goes, but I assume it won’t be
> very far. Does it work with nftables?
got some answers from the developer and it was pointed out to use the
4.15er kernel patch which did worked while building but loading the
module was not possible:

[127389.287576] xt_ndpi: disagrees about version of symbol module_layout

which is a little sad since it seems like the only one actual
development in this topic. Also the OpenDPI people have had their last
activities 6 years ago -->
https://github.com/ewildgoose/ndpi-netfilter
.

A current working solution is here -->
https://github.com/betolj/ndpi-netfilter
findable which seems to be a kind of the original one. There is also no
kernel/kernel_config patch needed but the code (but also the nDPI which
is from ntop) seems to be pretty outdated (needed to patch main.c to
bring it to life).

Some tests has been made and it do not work with 100 but with 90% but
the last (fundamental) activities are there also 2 years ago and it
looks like nobody maintains it currently.

A little documentation for a deeper look into, if wanted, can be found
in here -->
https://forum.ipfire.org/viewtopic.php?f=50&t=22320#p122679

Best and thanks again for your help.

Erik



      parent reply	other threads:[~2019-02-25 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 11:22 ummeegge
2019-02-19 11:25 ` Michael Tremer
2019-02-19 15:07   ` ummeegge
2019-02-19 16:20     ` Michael Tremer
2019-02-19 17:21       ` ummeegge
2019-02-25 13:32       ` ummeegge [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=aa85252f34fc86dca3aa8b92d3ac51a78cf80401.camel@ipfire.org \
    --to=ummeegge@ipfire.org \
    --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