From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Kernel patch - ERROR KCFG= FAIL
Date: Tue, 19 Feb 2019 16:07:27 +0100 [thread overview]
Message-ID: <636c6297bd98358f1a21751f35371662d0f38d94.camel@ipfire.org> (raw)
In-Reply-To: <2528C607-55C3-4AC3-A712-B18A3020A79E@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2637 bytes --]
Hi Michael,
great that you looked over it.
On Di, 2019-02-19 at 11:25 +0000, Michael Tremer wrote:
> Hi,
>
> The error message is probably quite a bit before the end of the log.
Haven´t found something which can lead me in the right direction. Have
uploaded the build log -->
https://people.ipfire.org/~ummeegge/logs/kernel_log_KCFG-ERROR-nDPI-netfilter
may you can find something there...
>
> What is this patch for?
I think it implements some tracking possiblities via
conntrack/netfilter, the kernel config needed to be also modified. In
here -->
https://github.com/vel21ripn/nDPI/blob/netfilter-2.2/ndpi-netfilter/INSTALL#L22
you can find some further infos.
If all went well, it should be possible to regulate traffic via IPTables
module on application-layer basis e.g. :
iptables -A INPUT -m ndpi --youtube -j DROP # Block youtube
iptables -A INPUT -m ndpi --facebook -j DROP # Block facebook
iptables -A INPUT -m ndpi --skype -j DROP # Block skype
wanted to give it some tests, i thought it might be a nice addition to the already
available layer 7 patch.
>
> -Michael
>
> > On 19 Feb 2019, at 11:22, ummeegge <ummeegge(a)ipfire.org> wrote:
> >
> > Hi all,
> > am trying currently to patch the kernel for nDPI-netfilter and am
> > getting an error which i can´t solve. The patch is from here -->
> >
https://github.com/vel21ripn/nDPI/blob/netfilter-2.2/ndpi-netfilter/kernel-patch/v4.14.0.diff
> > and it does apply but the kernel quits after sometime with
> >
> > CC [M] drivers/net/wireless/ti/wlcore/sdio.o
> > LD [M] drivers/net/wireless/ti/wlcore/wlcore_sdio.o
> > LD [M] drivers/net/wireless/ti/wlcore/wlcore.o
> > AR drivers/net/wireless/ti/built-in.o
> > AR drivers/net/wireless/built-in.o
> > AR drivers/net/built-in.o
> > AR drivers/built-in.o
> > make[1]: Leaving directory '/usr/src/linux-4.14.97'
> > make: *** [linux:149: /usr/src/log/linux-4.14.97-ipfire] Error
> >
> > ERROR: Building linux
> > KCFG=
> >
> > [ FAIL ]
> > Check /var/dev-ipfire_20190118_1813/ipfire-
> > 2.x/log/_build.ipfire.log for errors if applicable
> >
> >
> > so may there is a simple solution for the "KCFG= ERROR". Since i do
> > not
> > really have much experience in kernel development i decided to ask
> > the
> > list for potential help...
> >
> > Might be great if someone do have a hint for me ?
> >
> > Best,
> >
> > Erik
> >
>
>
next prev parent reply other threads:[~2019-02-19 15:07 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 [this message]
2019-02-19 16:20 ` Michael Tremer
2019-02-19 17:21 ` ummeegge
2019-02-25 13:32 ` ummeegge
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=636c6297bd98358f1a21751f35371662d0f38d94.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