All of lore.kernel.org
 help / color / mirror / Atom feed
From: S/C Conway <seconway@mts.net>
To: netfilter@lists.netfilter.org
Subject: journey through IPTables looking for documentation
Date: Fri, 25 Apr 2003 06:44:54 -0500	[thread overview]
Message-ID: <3EA91FB6.BB3D44FC@mts.net> (raw)

G'Day,
What is the path data takes to complete its journey through IPTables?

Many of the documents I have read provide in detail the rule
construction of a firewall.  I have a working firewall. Rule
construction is not my goal. I am trying to understand IPTables in
microcosm. My question is to help develop a better understanding of data
movement within IPTables. 

I have constructed through research a diagram that shows the chain path
through IPTables superimposed over a physical network. I am at a
crossroad because my research conflicts with what I see through protocol
analysis. I am missing some key piece of knowledge.

I am looking for someone who has knowledge of IPTables and is willing to
wear a tank to go "deep". I would like to start by reviewing the drawing
and providing some suggestions. I am willing to share my research.

Sean D. Conway


                 reply	other threads:[~2003-04-25 11:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EA91FB6.BB3D44FC@mts.net \
    --to=seconway@mts.net \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.