iptables install

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm trying to build iptables-1.4.2 for a 2.6 kernel running on an
embedded ARM device (up to now I've used 1.2.11 on a 2.4 kernel).  To
build and install, I run:

#./configure --host=arm --enable-static KERNEL_DIR=$KERNEL_SOURCE
prefix=$BUILD_DIR CC=arm-9tdmi-linux-gnu-gcc LD=arm-9tdmi-linux-gnu-ld
AR=arm-9tdmi-linux-gnu-ar

#make KERNEL_DIR=$KERNEL_SOURCE prefix= CC=arm-9tdmi-linux-gnu-gcc
LD=arm-9tdmi-linux-gnu-ld AR=arm-9tdmi-linux-gnu-ar

#make KERNEL_DIR=$KERNEL_SOURCE prefix=$BUILD_DIR
CC=arm-9tdmi-linux-gnu-gcc LD=arm-9tdmi-linux-gnu-ld
AR=arm-9tdmi-linux-gnu-ar install

In $BUILD_DIR/sbin , I then see "iptables-static".  Is that the binary I
should run? Or put another way, should I rename "iptables-static" to
"iptables" to use the same scripts and apps that expect a binary called
"iptables"?  Why doesn't "make install" name it iptables?  Or am I doing
something wrong on the install side?

When I do rename it to "iptables", and I run iptables on the device, the
output looks like it's still trying to load modules from somewhere, even
though I used the --enable-static option when running configure.  The
output:

--------Output start

modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
modprobe: could not parse modules.dep
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
REJECT     udp  --  anywhere             anywhere            udp
dpt:domain reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

------------ Output end

What modules could it be attempting to load?  Or should I disregard it and assume it's working? (It
looks like it works after a few simple tests)

Regards,
Richard Barry


--
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

[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux