Re: ipchains or iptables? (was: X version)
There is no provision that I am aware of in 2.2 kernels for iptables.
You do have to set up packet filtering, etc., when you build your
kernel. 2.4 kernels do allow for ipchains, but you must selet that
option when you build them. Selecting one (ipchains or iptables)
blocks use of the other, so the presence of iptables directories,
etc. in your woody distribution should have no effect. It does
nothing in mine but take up space (I'm running woody with 2.4.18 and
using ipchains). Woody also provides some ipchains scripting that is
not present in potato. I'd look for that (I'd point you to it, except
that I think I wiped it out, having my own startup script).
* Steve Haslam (email@example.com) wrote:
> On Fri, May 31, 2002 at 03:52:15PM -0700, Paul E Condon wrote:
> > OK, so I'm really using kernel 2.2.19, but...
> > I have been under the impression that the method of packet filtering/forwarding
> > changed from something called 'ipchains' in 2.2 to something called 'iptables'
> > in 2.4. I see that 'iptables' stuff has been added in various places to my
> > file system, and 'ipchains' stuff seems to have been clobbered. I would like
> > not to become too involved in network admin, but to fix my system I need to
> > rebuild some stuff. How can I determine if I should follow recipes for
> > 'ipchains' or 'iptables' ? ( Or am I truly misinformed? )
> version 2.4 kernels may support ipchains backwards-compatibility. you could
> try running "ipchains -L" and see if it works. (you can't use both iptables
> and ipchains simultaneously, even with back-compat. enabled).
> Hmm, I belive that ipchains should still be installable-- it's still in
> unstable, and ipmasq will still use it if requested.
> iptables is better though, gives you access to stateful filtering and is
> more extensible. (I was able to fix some MTU breakage between here and work
> with it).
Cam Ellison Ph.D. R.Psych.
From Roberts Creek on B.C.'s incomparable Sunshine Coast
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com