[Tfug] ip_tables kernel code no longer possible to build into the kernel?

[t takahashi]

what i need is normal, basic, usual iptables capabilities.  like
blocking ports and port ranges and limiting and logging,

so is this module (or rather all these tiny little iptables-related modules):

1.  something that looks EXACTLY like it's what i need but is not?
i.e. it is for some advanced thing?

or:

2.  just what i need?

i pulled your trick on XTABLES and it still looks like what i need.
so why would it not default to yes?

i kind of found out via make menuconfig just before you posted that it
might have something to do with a higher level setting being a module.
 it looks like that might be the reason.

as for using a module, i can, but there were dozens and i didn't want
to have to keep track of them just to do basic things.  why would i
have to reenable iptables, then set modules for every tiny little part
of it, like port ranges and limiting and the like?  i'd think it would
be mostly on by default.


-- 
Webmaster: do you believe that people will (a) switch browsers to view
your "best viewed with" page or (b) go to your competitor?