From: Jose Luis Domingo Lopez <lartc@24x7linux.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Requset regarding packet marking.
Date: Fri, 06 Sep 2002 20:31:29 +0000 [thread overview]
Message-ID: <marc-lartc-103134436624944@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103124517825350@msgid-missing>
On Thursday, 05 September 2002, at 16:57:53 -0000,
anish_46628 wrote:
> 3. Traffic going out from PC2 and generated by PC2 itself should
> have different differnt mark so that the traffic can be filtered
> based on the mark.
>
With linux kernel 2.4.x, packets go through different sets of rules when
"traversing" the box. A packet in transit will enter PREROUTING, pass on
to FORWARD and finally to POSTROUTING just before being queued to be
sent out on the physical interface. On the other hand, locally generated
packets go first to OUTPUT and afterwards to POSTROUTING. Compare this
to kernels 2.2.x when an in-transit packet would be seen at input, forward
and output.
There is an _excelent_ reference on iptables you should check to get the
details of what you can do and how:
http://people.unix-fu.org/andreasson/iptables-tutorial/iptables-tutorial.html
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Woody (Linux 2.4.19-pre6aa1)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-09-06 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 16:57 [LARTC] Requset regarding packet marking anish_46628
2002-09-06 20:31 ` Jose Luis Domingo Lopez [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-103134436624944@msgid-missing \
--to=lartc@24x7linux.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.