1FOLLOW THESE STEPS:
2
30) There may be some outstanding bugfixes or tweaks which are not yet
4   in the official kernel.  Those are now (as of iptables-1.2.7) kept
5   in a seperate package, called patch-o-matic.  It is available from
6   ftp://ftp.netfilter.org/pub/patch-o-matic/
7
81) Next, make the package.
9	% make KERNEL_DIR=<<where-you-built-your-kernel>>
10
112) Finally, you need to to install the shared libraries, and the binary:
12	# make install KERNEL_DIR=<<where-you-built-your-kernel>>
13
14If you are a developer, you can install the headers, development libraries
15and associated development man pages, with:
16	# make install-devel
17
18That's it!
19================================================================
20PROBLEMS YOU MAY ENCOUNTER:
21
221) This package requires a 2.4.4 kernel, or above.
23
242) If you get the kernel directory wrong, you may see a message like:
25	Please try `make KERNEL_DIR=path-to-correct-kernel'
26
273) If you want to specify alternate directories for installation
28(instead of /usr/local/ bin lib man), do this:
29
30	% make BINDIR=/usr/bin LIBDIR=/usr/lib MANDIR=/usr/man
31	# make BINDIR=/usr/bin LIBDIR=/usr/lib MANDIR=/usr/man install
32
334) If you want to build a statically linked version of the iptables binary,
34   without the need for loading the plugins at runtime (e.g. for an embedded
35   device or router-on-a-disk), please use
36
37	% make NO_SHARED_LIBS=1
38
395) If you want to build a single BusyBox style multipurpose binary instead of
40   the individual iptables, iptables-save and iptables-restore binaries, then
41   please use
42
43	% make DO_MULTI=1
44
45NOTE: make sure you build with at least the correct LIBDIR=
46specification, otherwise iptables(8) won't know where to find the
47dynamic objects.
48