From: "???????? ?????" <skekes@pylones.gr>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] OUTPUT chain marking after or before routing?
Date: Thu, 17 Jul 2003 06:37:42 +0000 [thread overview]
Message-ID: <marc-lartc-105842380827919@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105842045025983@msgid-missing>
Well catalin, try to add theese rules with the in the prerouting chain
but bind theese rules with the interfaces you have.
Without binding netfilter rules with interfaces it will not work, and
you'll get the results you allready got.
Catalin Borcea wrote:
>Hello,
>I tried to mark the packets in the PREROUTING chain but still doesn't work.
>Now the packets are no marked anymore when they go out by the eth2
>interface. When I marked them in the OUTPUT chain they arrived also to the
>eth2 interface but marked. According to the docs the PREROUTING chain is not
>traversed by locally generated packets so, I don't know how this works for
>you. Maybe you have forwarded packets and not locally generated packets.
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-07-17 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 5:37 [LARTC] OUTPUT chain marking after or before routing? Catalin Borcea
2003-07-17 6:04 ` ???????? ?????
2003-07-17 6:31 ` Catalin Borcea
2003-07-17 6:37 ` ???????? ????? [this message]
2003-07-17 7:15 ` Catalin Borcea
2003-07-17 7:32 ` ???????? ?????
2003-07-17 14:08 ` Chijioke Kalu
2003-07-17 15:55 ` Martin A. Brown
2003-07-17 16:50 ` lartc
2003-07-18 5:04 ` Catalin Borcea
2003-07-18 18:41 ` Martin A. Brown
2003-07-18 18:46 ` Martin A. Brown
2003-07-19 7:45 ` lartc
2003-07-20 15:19 ` Leonardo Balliache
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-105842380827919@msgid-missing \
--to=skekes@pylones.gr \
--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.