Ok,
that's my mistake about put IP tables built-in kernel instead of module.
So I try again putting "IP tables suppport" like module like you can see
below, but I still can't load iptables but now I can load ip_tables. Is
this the same one??
[*] Network packet filtering (replaces ipchains) --> IP: Netfilter
Configuration -->
<*> IP tables support (required for filtering/masq/NAT)
<M> limit match support
<M> IP range match support
I also tryed to use these optbions below like modules but I'm not
allowed to change this to module, so I also tryed to deactivate these
options but in the same way I can't load iptables module.
Is this options below part of iptables too? or it's just for router? I'm
really confused about iptables support in this kernel 'cause it's so
differente of the 2.6.0 version.
Device Drivers ->
Networking support ->
Networking Options ->
[*] IP: advanced router
[*] IP: policy routing
[*] IP: use netfilter MARK value as routing key
[*] IP: fast network address translation
[*] IP: equal cost multipath
[*] IP: use TOS value as routing key
[*] IP: verbose route monitoring
Tks in advice,
claudinei matos
On Tue, 2004-02-03 at 16:46, Marshal Newrock wrote:
> On Tue, 3 Feb 2004, Claudinei Matos wrote:
>
> > So genkernel had marked that's options and I tried to compile the kernel
> > without any other changes, but the module iptables had not compiled
> > Device Drivers ->
> > Networking support ->
> > Networking Options ->
> > [*] Network packet filtering (replaces ipchains) -->
> > IP: Netfilter Configuration -->
> > <*> IP tables support (required for filtering/masq/NAT)
> > <M> limit match support
> > <M> IP range match support
>
> [snip]
>
> > So, is the module name of iptable changed? When I see this message of
> > lsmod, I tryed to use the last version of firehol to create my firewall
> > rules, but when I start firehol the program exit with error on trying to
> > load iptable module.
> >
> > What can I doing wrong? Have anybody any advice to take me?
>
> The <*> indicates that IP tables is compiled in, rather than compiled as a
> module. Since there's no module, 'modprobe iptables' will fail, but if
> you do 'iptables -L' you'll see iptables present and working.
>
> You would either need to change IP Tables support to be a module, or
> change the firehol script to recognize that iptables might be compiled in,
> instead of a module. IMHO, failing if something is compiled in rather
> than a module is poor planning or poor programming (if there's a
> difference).
--
[EMAIL PROTECTED] mailing list
