netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Ed W <lists@wildgooses.com>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
	netfilter-devel@vger.kernel.org
Subject: Re: Feature request: ip_set for non-modular kernel
Date: Thu, 05 May 2011 14:49:37 +0100	[thread overview]
Message-ID: <4DC2AAF1.6000301@googlemail.com> (raw)
In-Reply-To: <4DC29AFF.5060901@wildgooses.com>


> Hi, Love the ip_set features - any chance that you might provide the
> code (or possibly just instructions?) to build into the kernel in a
> non-modular fashion? (for 2.6.38 and earlier)
>   
I was able to successfully achieve just that with version 4.5 and kernel 
2.6.35 (kernel compiled from source, of course). If you have ipset 4.5 
there is a nifty script called patch_kernel in the kernel/ directory 
which does the donkey work for you - i.e. copying the necessary files to 
the kernel source directory and adjust the appropriate kernel Kbuild and 
Makefile(s).

What is left to be done by you then is to run "make oldconfig" (or amend 
the ipset kernel options manually, if you wish) and adjust the ipset 
kernel options so that all ipset files are included in the kernel, not 
as modules (in other words, set all ipset-related kernel options to "y" 
as oppose to "m").

In version 6 and above, the job is a tad more difficult as I am not sure 
you can build the ipset objects as part of the kernel - I have 
successfully built them as modules (as part of the kernel compilation), 
but have not tried to include them as part of the kernel itself - I am 
waiting for Jozsef to fix the bug I found in v6.3 and I will then 
upgrade all my systems to that version (I am still on 4.5 at present). 
Good luck!


      reply	other threads:[~2011-05-05 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 12:41 Feature request: ip_set for non-modular kernel Ed W
2011-05-05 13:49 ` Mr Dash Four [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=4DC2AAF1.6000301@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=lists@wildgooses.com \
    --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).