From: "Billy Crook" <billycrook@gmail.com>
To: Jose Ildefonso Camargo Tolosa <ildefonso.camargo@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Question about packet flow picture.
Date: Tue, 26 Aug 2008 09:04:17 -0500 [thread overview]
Message-ID: <a43edf1b0808260704k947044ekf0d9ba51dd4e2577@mail.gmail.com> (raw)
In-Reply-To: <4c4b58e80808260556o1f25214el31cf22bd2284156e@mail.gmail.com>
On Tue, Aug 26, 2008 at 07:56, Jose Ildefonso Camargo Tolosa
<ildefonso.camargo@gmail.com> wrote:
> OUTPUT (raw) ---> Conntrack ---> OUTPUT (mangle) ----> reroute
> check???? ---> OUTPUT (nat)
>
> Shouldn't the "reroute check" go *after* OUTPUT (nat) ?
I'm not sure
> and I have one doubt:
>
> It says that:
>
> ebtables OUTPUT (nat) --> ebtables OUTPUT (filter) --> ebtables
> POSTROUTING (nat) --> Network Output
>
> But, shouldn't it "reroute" the packet after ebtables OUTPUT (nat)?
To where should it reroute? EBtables lies underneath iptables,
between it and the hardware (usually). When ebtables is done with the
packet, it'd done with it.
next prev parent reply other threads:[~2008-08-26 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 23:41 Question about packet flow picture Jose Ildefonso Camargo Tolosa
2008-08-26 3:23 ` Billy Crook
2008-08-26 12:56 ` Jose Ildefonso Camargo Tolosa
2008-08-26 14:04 ` Billy Crook [this message]
2008-08-26 14:48 ` Michal Soltys
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=a43edf1b0808260704k947044ekf0d9ba51dd4e2577@mail.gmail.com \
--to=billycrook@gmail.com \
--cc=ildefonso.camargo@gmail.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox