Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Michael Gale <mgale@utilitran.com>
To: netfilter@lists.netfilter.org
Subject: Re: Hello .. Packet path :)
Date: Wed, 3 Dec 2003 08:49:55 -0700	[thread overview]
Message-ID: <20031203084955.7491f260.mgale@utilitran.com> (raw)
In-Reply-To: <20031203164647.GB28783@cannon.eng.us.uu.net>


Thank you to all who replied :)

Michael.


On Wed, 3 Dec 2003 11:46:47 -0500
Ramin Dousti <ramin@cannon.eng.us.uu.net> wrote:

> Daniel Chemko had an email on this subject not too long ago:
>  
> Raw/PREROUTING
> Mangle/PREROUTING
> Nat/PREROUTING
> Mangle/INPUT
> Filter/INPUT
> Mangle/FORWARD
> Filter/FORWARD
> Raw/OUTPUT
> Mangle/OUTPUT
> Filter/OUTPUT
> Nat/OUTPUT
> Mangle/POSTROUTING
> Nat/POSTROUTING
>  
> 
> On Wed, Dec 03, 2003 at 08:30:34AM -0700, Michael Gale wrote:
> 
> > Hello,
> > 
> > 	I am trying to make a packet go through the least amount of chains / tables as possible for performance.
> > 
> > I have read through the online documentation about netfilter and this "Linux Firewalls Second Edition" book (which was ok). 
> > 
> > But I still have some questions about the order in which the tables are checked. Here is what I think happens when a pack comes in and should be forwarded to a internal machine
> > 
> > Firewall External interface:
> > Packet comes in:
> > NAT table PREROUTING 
> > NAT talbe OUTPUT
> > NAT table POSTROUTING
> > filter table INPUT
> > filter table OUTPUT or forward
> > 
> > Then you would have the same thing when the packet leaves the internal interface.
> > 
> > Of course this is if you break it down by interface first.
> > 
> > Please let me know if this is correct ?
> > 
> > -- 
> > Michael Gale
> > Network Administrator
> > Utilitran Corporation
> 


-- 
Michael Gale
Network Administrator
Utilitran Corporation


      reply	other threads:[~2003-12-03 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 15:30 Hello .. Packet path :) Michael Gale
2003-12-03 16:46 ` Ramin Dousti
2003-12-03 15:49   ` Michael Gale [this message]

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=20031203084955.7491f260.mgale@utilitran.com \
    --to=mgale@utilitran.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox