From: "J. Bakshi" <joydeep@infoservices.in>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@vger.kernel.org
Subject: Re: how to get ipset as module
Date: Tue, 06 Oct 2009 17:11:46 +0530 [thread overview]
Message-ID: <4ACB2CFA.3000704@infoservices.in> (raw)
In-Reply-To: <alpine.DEB.2.00.0910061314460.14389@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> On Tue, 6 Oct 2009, J. Bakshi wrote:
>
>
>> Jozsef Kadlecsik wrote:
>>
>>> On Mon, 5 Oct 2009, J. Bakshi wrote:
>>>
>>>
>>>> I can't compile the kernel to activate ipset as it is a remote box. Is
>>>> there any alternative to to get ipset as a module in a remote suse box ?
>>>>
>>>>
>>> Assuming that the architectures of the remote/local boxes are
>>> identical, that's not hard at all:
>>>
>>> - get the source code of the kernel version running on the remote box,
>>> - configure the kernel source,
>>> - compile ipset with referring to the configured kernel source tree,
>>> - copy the compiled ip_set*.ko modules to the proper module directory
>>> on the remote box.
>>>
>> Thanks for your response.
>> Yes, this can be done too but the arch of the remote box is not same as
>> my local one. local box is 32-bit inter and the remote is
>> amd-dual-core-64bit
>>
>
> Then use the ARCH=x86_64 flag when configuring the kernel source.
>
>
Oh ! great. Forgot how flexible linux is.
Thanks
prev parent reply other threads:[~2009-10-06 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 4:42 how to get ipset as module J. Bakshi
2009-10-06 10:09 ` Jozsef Kadlecsik
2009-10-06 10:51 ` J. Bakshi
2009-10-06 11:16 ` Jozsef Kadlecsik
2009-10-06 11:41 ` J. Bakshi [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=4ACB2CFA.3000704@infoservices.in \
--to=joydeep@infoservices.in \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.