On Sun, 31 Dec 2000, guy keren wrote:
On Sun, 31 Dec 2000, Jonathan Ben-Avraham wrote:
The ipchains HOWTO contains an example firewall configuration with
separate chains defined for each triple of source network, destination
network and direction. That is, there are chains "net-dmz",
On Mon, 1 Jan 2001, Adi Stav wrote:
Hmm. How is that different from from creating custom chains in
ipchains and sending packets from one chain to another?
with chains - when one chain matched a rule, then its action is taken
place, and no more rule matching is performed on that packet from
On Sun, Dec 31, 2000 at 10:01:07AM +0200, guy keren wrote:
btw, in the new kernel (2.4), where netfilter is used, there is a new
notion of tables. unlike usage of multiple chains, usage of multiple
tables does add extra functionality, in that it allows you to have one set
of rules perform a
On Sun, 31 Dec 2000, Alex Shnitman wrote:
Hi, guy!
On Sun, Dec 31, 2000 at 10:01:07AM +0200, you wrote the following:
btw, in the new kernel (2.4), where netfilter is used, there is a new
notion of tables. unlike usage of multiple chains, usage of multiple
tables does add extra
On Sun, 31 Dec 2000, Alex Shnitman wrote:
btw, in the new kernel (2.4), where netfilter is used, there is a new
notion of tables. unlike usage of multiple chains, usage of multiple
tables does add extra functionality, in that it allows you to have one set
of rules perform a complete
On Mon, 1 Jan 2001, Adi Stav wrote:
btw, in the new kernel (2.4), where netfilter is used, there is a new
notion of tables. unlike usage of multiple chains, usage of multiple
tables does add extra functionality, in that itallows you to have one set
of rules perform a complete
Hi, guy!
On Sun, Dec 31, 2000 at 10:01:07AM +0200, you wrote the following:
btw, in the new kernel (2.4), where netfilter is used, there is a new
notion of tables. unlike usage of multiple chains, usage of multiple
tables does add extra functionality, in that it allows you to have one set
Hi,
The ipchains HOWTO contains an example firewall configuration with
separate chains defined for each triple of source network, destination
network and direction. That is, there are chains "net-dmz", "dmz-net",
"net-int", "int-net", "int-dmz" and "dmz-int". Is there any really good
reason not
On Sun, 31 Dec 2000, Jonathan Ben-Avraham wrote:
The ipchains HOWTO contains an example firewall configuration with
separate chains defined for each triple of source network, destination
network and direction. That is, there are chains "net-dmz", "dmz-net",
"net-int", "int-net", "int-dmz"
