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. Best regards, Jozsef - E-mail : kadlec@xxxxxxxxxxxxxxxxx, kadlec@xxxxxxxxxxxx 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 -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
