how to get ipset as module
Dear list,
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 ?
Thanks
Quoted 2 lines · J. Bakshi
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.
Best regards,
Jozsef
-
E-mail : [email protected], [email protected] 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
Quoted 7 lines · Jozsef Kadlecsik
Quoted 3 lines · J. Bakshi
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 ?
Quoted 10 lines
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
Quoted 16 lines · J. Bakshi
Quoted 6 lines · Jozsef Kadlecsik
Quoted 3 lines · J. Bakshi
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 ?
Quoted 8 lines
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.
Quoted 4 lines
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 : [email protected], [email protected] 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
Quoted 21 lines · Jozsef Kadlecsik
Quoted 18 lines · J. Bakshi
Quoted 16 lines · Jozsef Kadlecsik
Quoted 4 lines · J. Bakshi
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.
Quoted 9 lines
Quoted 5 lines
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-64bitThen use the ARCH=x86_64 flag when configuring the kernel source.
Oh ! great. Forgot how flexible linux is.
Thanks