Examples of using Ipchains in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
Iptables is a replacement for ipfwadm and ipchains.
It nicely replaces'ipchains' used in Linux kernel 2.2.
This motto narrowly edged out'Whip me, beat me, make me use ipchains.
Firstly, you can simply use ipchains and ipfwadm as before.
See Using ipchains and ipfwadm for how to painlessly avoid using iptables if you're using one of those tools.
The restart directive only works if the ipchains kernel module is not loaded.
Quick Translation From 2.0 and 2.2 Kernels Sorry to those of you still shell-shocked from the 2.0(ipfwadm)to 2.2(ipchains) transition.
At first glance, ipchains and iptables appear to be quite similar.
The connection tracking and NAT subsystems are more general andmore powerful than the rudimentary versions within ipchains and ipfwadm.
O Setting the masquerading timeouts with ipchains-M-S, or ipfwadm-M-s does nothing.
I wrote ipchains(see above for due credit to the people who did the actual work), and learnt enough to get packet filtering right this time.
So I could have simply written netfilter, ported ipchains over the top, and been done with it.
Those of you familiar with ipchains may simply want to look at Differences Between iptables and ipchains; they are very similar.
Red Hat Linux's firewall configuration tools use"ipchains," and those configurations are not vulnerable to this bug.
I wrote ipchains(see above for due credit to the people who did the actual work), and learnt enough to get packet filtering right this time.
Prior to iptables,the predominant software packages for creating Linux firewalls were ipchains in Linux kernel 2.2.x and ipfwadm in Linux kernel 2.0.x, which in turn was based on BSD's ipfw.
After I finished ipchains, which was initially going to be a minor modification of the kernel part of ipfwadm, and turned into a larger rewrite, and wrote the HOWTO, I became aware of just how much confusion there is in the wider Linux community about issues like packet filtering, masquerading, port forwarding and the like.
Those of you familiar with ipchains may simply want to look at; they are very similar.
One of the advantages of iptables filter over ipchains is that it is small and fast, and it hooks into netfilter at the NF_IP_LOCAL_IN, NF_IP_FORWARD and NF_IP_LOCAL_OUT points.
One powerful feature which iptables inherits from ipchains is the ability for the user to create new chains, in addition to the three built-in ones INPUT, FORWARD and OUTPUT.