[Tfug] iptables no longer built into kernel? make oldconfig on lsd?
t takahashi
gambarimasu at gmail.com
Mon May 22 13:19:35 MST 2006
i got the latest debian linux-source, did zcat /proc/config.gz >
.config, and ran make oldconfig.
the iptables questions are numerous and strange. some of them have a
default of N but say that if you are unsure you should say Y.
shouldn't the "unsure" comment and default options match?
even worse, the ip tables support (same as iptables and ip_tables?)
can't be built into the kernel. doesn't nearly everybody run a
firewall?
take a look:
IP tables support (required for filtering/masq/NAT)
(IP_NF_IPTABLES) [N/m/?] (NEW) ?
iptables is a general, extensible packet identification framework.
The packet filtering and full NAT (masquerading, port forwarding,
etc) subsystems now use this: say `Y' or `M' here if you want to use
either of those.
To compile it as a module, choose M here. If unsure, say N.
IP tables support (required for filtering/masq/NAT)
(IP_NF_IPTABLES) [N/m/?] (NEW) y
iptables is a general, extensible packet identification framework.
The packet filtering and full NAT (masquerading, port forwarding,
etc) subsystems now use this: say `Y' or `M' here if you want to use
either of those.
To compile it as a module, choose M here. If unsure, say N.
IP tables support (required for filtering/masq/NAT)
(IP_NF_IPTABLES) [N/m/?] (NEW)
clearly something is wrong, even if it's just my understanding of
what's going on.
thanks.
--
Webmaster: do you believe that people will (a) switch browsers to view
your "best viewed with" page or (b) go to your competitor?
More information about the tfug
mailing list