From: Husnu Demir <hdemir@metu.edu.tr>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: "netfilter-devel@vger.kernel.org >> Netfilter Developer Mailing
List" <netfilter-devel@vger.kernel.org>
Subject: Re: ipset problem.
Date: Mon, 25 Jan 2010 13:57:05 +0200 [thread overview]
Message-ID: <4B5D8711.7000802@metu.edu.tr> (raw)
In-Reply-To: <alpine.DEB.2.00.1001251246070.21944@blackhole.kfki.hu>
[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Good point, I did not understand what I read. Perhaps I am following the IPSET so
long time that I think that I have to compile all kernel. As I read "need the
source tree of ..", I should reload the kernel.
0. You need the source tree of your kernel (version >= 2.6.16 or 2.4.36.x)
and it have to be configured, modules compiled.
Thanks.
hdemir.
Jozsef Kadlecsik wrote:
> On Mon, 25 Jan 2010, Husnu Demir wrote:
>
>>> On Mon, 25 Jan 2010, Husnu Demir wrote:
>>>
>>>> I do download xtables-addons-1.22.tar.bz2 and installed it. It has the
>>>> same problem.
>>> xtables-addons-1.22 was released two days ago, before ipset-4.2.
>>>
>>>> I could not try ipset-4.2.tar.bz2.
>>> Why can't you install ipset itself? What's the problem?
>> As far as I remember I should pacth the kernel and reload the server
>> which I did not want. But for the xtables no need to reload the kernel.
>
> You have to patch the kernel only if you run 2.4.x, as it is written in
> the README of the ipset source tree...
>
> Best regards,
> Jozsef
> -
> E-mail : kadlec@blackhole.kfki.hu, kadlec@mail.kfki.hu
> PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
> Address : KFKI Research Institute for Particle and Nuclear Physics
> H-1525 Budapest 114, POB. 49, Hungary
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAktdhxEACgkQHgR50XBBy+mCggCfe47Js52jNJLxxx7S6hblOdqc
Kf8AoM4y/GlopHCFtmOtfPDVEdXWoag4
=fui9
-----END PGP SIGNATURE-----
[-- Attachment #2: hdemir.vcf --]
[-- Type: text/x-vcard, Size: 164 bytes --]
begin:vcard
fn:Husnu Demir
n:Demir;Husnu
email;internet:hdemir@metu.edu.tr
tel;work:+903122103330
tel;fax:+903122103303
x-mozilla-html:FALSE
version:2.1
end:vcard
next prev parent reply other threads:[~2010-01-25 11:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 11:54 ipset problem Husnu Demir
2010-01-22 13:22 ` Jozsef Kadlecsik
2010-01-22 18:05 ` Tom Eastep
2010-01-23 21:00 ` Jozsef Kadlecsik
2010-01-23 21:44 ` Jozsef Kadlecsik
[not found] ` <alpine.DEB.2.00.1001242243560.20757@blackhole.kfki.hu>
2010-01-25 7:17 ` Husnu Demir
2010-01-25 10:24 ` Jozsef Kadlecsik
2010-01-25 11:33 ` Jan Engelhardt
2010-01-25 11:47 ` Husnu Demir
2010-01-25 11:34 ` Husnu Demir
2010-01-25 11:39 ` Jan Engelhardt
2010-01-25 11:49 ` Jozsef Kadlecsik
2010-01-25 11:57 ` Husnu Demir [this message]
2010-01-25 12:01 ` Husnu Demir
-- strict thread matches above, loose matches on Subject: below --
2012-09-13 14:19 Ipset Problem Lutfi ODUNCUOGLU
2012-09-13 14:53 ` Jozsef Kadlecsik
2012-09-13 20:12 ` hdemir
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=4B5D8711.7000802@metu.edu.tr \
--to=hdemir@metu.edu.tr \
--cc=kadlec@blackhole.kfki.hu \
--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).