All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing fundamentals
Date: Fri, 28 Mar 2003 19:32:26 +0000	[thread overview]
Message-ID: <marc-lartc-104888003902009@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104882855509686@msgid-missing>

Kjell,

Let me try a slightly different tack.....one of the fundamental
differences between ipchains and iptables is identified and explored in
varying depths here:

  http://www.netfilter.org/documentation/HOWTO//packet-filtering-HOWTO-10.html
  http://www.linuxvirtualserver.org/Joseph.Mack/HOWTO/LVS-HOWTO.netfilter_hooks.html

[ Apparently, I wrote a similar statement about ipchains vs. iptables in
  July of last year...the beauty of a bad memory is that I can learn
  things anew by re-reading things I once knew! ]

  http://lists.insecure.org/lists/firewall-wizards/2002/Jul/0228.html

In ipchains, each incoming packet hit input, forward and output chains,
which only filtered packets (OK, OK, and masqueraded).

In iptables, every incoming packet traverses the PREROUTING chains in the
conntrack (implicit), mangle and nat tables.  In the PREROUTING chains,
you have access to --in-interface (-i) $RECEIVE_IF.  In the PREROUTING
chain, an output interface makes no sense, because we have no idea about
where the packet is going!

Now that the PREROUTING chain has been passed, we'll route!  After
routing, (and assuming the packet is bound for a non-local destination),
the packet will enter the FORWARD chain.  Now, we know both --in-interface
$RECEIVE_IF and --out-interface (-o) $TRANSMIT_IF, so both options can be
used.

POSTROUTING is just about the last thing before the packet is handed off
to the much misunderstood traffic control system.  And in this
chain, you'll see nalogous behaviour...the --in-interface option is not
available.

Does that answer your question?

-Martin

 : > > For a packet that is not for local host,
 : > > but comes in on one interface and goes
 : > > out on another;
 : (1)
 : > > Will that packet traverse PREROTING, FORWARD and POSTROUTING
 : > > on _both_ underface, or
 : (2)
 : > > will that packet traverse PREROTING, FORWARD and POSTROUTING
 : > > only once, where PREROTING is when a packet "is in" the incoming
 : > > physical interface, and is in FORWARD and POSTROUTING when
 : > > the packet "is in" the outgoing interfave?
 : > >
 : > Maybe this can help :
 : > http://www.docum.org/stef.coene/qos/kptd/
 :
 : No. It would help if you told me what is right.
 : The figure I got from before, and really don't
 : rule out number one.
 :
 :
 : _______________________________________________
 : LARTC mailing list / LARTC@mailman.ds9a.nl
 : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
 :

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-03-28 19:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28  5:14 [LARTC] Routing fundamentals Kjell Chris Flor
2003-03-28 10:59 ` Stef Coene
2003-03-28 16:28 ` Kjell Chris Flor
2003-03-28 16:46 ` Erik S. Johansen
2003-03-28 19:32 ` Martin A. Brown [this message]
2003-03-28 20:08 ` Martin A. Brown

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=marc-lartc-104888003902009@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --cc=lartc@vger.kernel.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.