From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ipchains + mark in output chain ?
Date: Mon, 17 Jun 2002 20:35:34 +0000 [thread overview]
Message-ID: <marc-lartc-102434613412400@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102389248503844@msgid-missing>
Hello,
On Mon, 17 Jun 2002, Ciprian Niculescu wrote:
> aa ok, so why the subject is ipchains? :-)
I'm just replying to the proposed iptables diagram.
> >>http://people.unix-fu.org/andreasson/iptables-tutorial/images/tables_traverse.jpg
> >>
> > Another wrong picture for iptables
>
>
> why???
Read my posting again. The routing decision is before
OUTPUT not after OUTPUT. It should be looking something like:
local process -> output routing -> OUTPUT+output_rerouting(s) -> ...
Another problem: to what routing decision refers the diagram
after forward?
The forwarding should be:
prerouting -> input routing -> forward -> post_routing
Another bug, this time in the netfilter sources (iptable_mangle.c):
output_rerouting called from INPUT
> C
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-06-17 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 14:32 [LARTC] ipchains + mark in output chain ? Ludovic Drolez
2002-06-12 14:48 ` Stef Coene
2002-06-17 18:55 ` Leonardo Balliache
2002-06-17 19:11 ` Julian Anastasov
2002-06-17 19:20 ` Ciprian Niculescu
2002-06-17 19:31 ` Julian Anastasov
2002-06-17 19:42 ` Ciprian Niculescu
2002-06-17 20:35 ` Julian Anastasov [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=marc-lartc-102434613412400@msgid-missing \
--to=ja@ssi.bg \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox