From: Leonardo Balliache <leoball@opalsoft.net>
To: lartc@vger.kernel.org
Subject: [LARTC] linux NETWORKING diagram ?
Date: Thu, 25 Jul 2002 02:54:10 +0000 [thread overview]
Message-ID: <marc-lartc-102756596704209@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102736700917698@msgid-missing>
Hi.
You wrote:
> OK. I've made the diagram in Dia (attached). U can easly export it in
any format > (any linux distro have Dia, i think)...
Could you post your diagram in ascii?
> I made some changes may be they are wrong, pls correct me... I thought
that all > "mangle" and "nat" stuff should be "IPTABLES", and all
"ipchains" suff should go > away !! ?
As I understand there is some ipchains original code running on iptables;
but not iptables code to emulate ipchains behavior, just ipchains filter
code. Have a look to LARTC digest, Vol 1 #641, #642, #651, #652 and #655.
> - What is "mark-rewrite" ?!
It would be better "mark-write".
It's mark packet writing in mangle table (fwmark). This mark survive just
inside host or router that makes the mark (the packet is not really marked
when it leaves the router).
> - there is something which have to be added somewhere around
"forwarding", can't > figure out what/where ?! Pls do it, or tell me i wil
do it?
> - in my opinion (6a.3) output-routing should go at the place of (7) !!!
> 'm I right ?
I haven't your diagram. BTW, diagram misses some hooks (must be added):
conntrack PREROUTING just before mangle PREROUTING.
conntrack INPUT after filter INPUT but before LOCAL PROCESS.
mangle INPUT after conntrack INPUT also before LOCAL PROCESS.
mangle FORWARD before filter FORWARD.
conntrack OUTPUT before mangle OUTPUT but after OUTPUT ROUTING.
mangle POSTROUTING before nat POSTROUTING.
conntrack POSTROUTING after nat POSTROUTING but before QOS EGRESS.
when discussion matures I will post this changes to Stef.
Best regards,
Leonardo Balliache
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-25 2:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 19:41 [LARTC] linux NETWORKING diagram ? raptor
2002-07-22 20:03 ` Stef Coene
2002-07-23 7:15 ` Gabriel Paues
2002-07-23 18:27 ` raptor
2002-07-23 19:06 ` Stef Coene
2002-07-23 19:29 ` raptor
2002-07-23 20:35 ` Stef Coene
2002-07-25 2:54 ` Leonardo Balliache [this message]
2002-07-25 19:07 ` raptor
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-102756596704209@msgid-missing \
--to=leoball@opalsoft.net \
--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.