compiling iptables support for other machine
Hi, folks,
I might be wrong looking for help in this forum but as it is related to the topic I hope someone can give me a usefull advice or an idea where I can find related information to solve the following problem:
=====
I am trying to compile a new kernel on my machine (MA) for anathor machine (MB) that I am using as firewall, where I need extended iptables support.
MB is very slow and does not have enough diskspace, so I can not install compilers or headers there.
Tehre is enough space for a new kernel though.
What I was trying ot do is to compile the kernel on MA and to install it after I nfs-mount the linux-directory from MA to MB. Unfortunately a developers environment on MB is missing and I got following error after i do
make install
make: *** No rule to make target /usr/src/kernel-source-2.4.20/include/asm/param.h', needed by /usr/src/kernel-source-2.4.20/include/linux/sched.h'. Stop.
Unfortunately on MA everything is compiling fine - where is the problem what do I need for the asm/param.h
Is it enough to compile on MA and to copy the relevant stuff eg. vmlinuz
+ modules to MB
thanks a lot
--
+ Emanoil Kotsev - - - - -+
+ E-Mail: [email protected] +
On Sat, May 03, 2003 at 01:29:01PM +0200, Emanoil Kotsev spoke thusly:
Quoted 5 lines
Unfortunately on MA everything is compiling fine - where is the problem what do I need for the
asm/param.hIs it enough to compile on MA and to copy the relevant stuff eg. vmlinuz
+ modules to MB
After you compile the kernel, merely copy over the following files :
- /usr/src/linux-2.4.20/arch/i386/boot/bzImage
- /usr/src/linux-2.4.20/System.map
- /lib/modules/2.4.20/*
to the relevant paths at MB. Most probably /boot/ and /lib/. If you've made changes to the iptables stuff, copy over the binary + relevant shared libraries (.so files); those might be in different places. Try the following paths for starters :
/lib/iptables//usr/local/lib/iptables/
If you still can't find it, try doing 'strace /path/to/new/iptables/binary -L -n', and look for the open() calls to see which library path its looking at. Reboot && voila :)