From: Balazs Scheidler <bazsi@balabit.hu>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: netfilter-devel@lists.samba.org
Subject: Re: [RFC] matching tproxied packets
Date: Tue, 4 Jun 2002 18:28:37 +0200 [thread overview]
Message-ID: <20020604162837.GA2365@balabit.hu> (raw)
In-Reply-To: <200206041714.47683.hno@marasystems.com>
On Tue, Jun 04, 2002 at 05:14:47PM +0200, Henrik Nordstrom wrote:
> Balazs Scheidler wrote:
>
> > * use a new state (called TPROXY), which would be applied to all TPROXYed
> > packets (might interact badly with nat/conntrack).
>
> It will in no doubt interact badly with connection tracking (and therefore
> NAT).
ok.
>
> > * have the tproxy framework mark all packets with an fwmark, and let the
> > packets in based on the value of fwmark
>
> Will interact badly with fwmark based routing.
of course the mark value would be controlled by the user, and not assigned
automatically.
> > * have a separate match (called tproxy), which matches tproxied sessions
> > based on some value stored in the associated conntrack entry
>
> Defenitely my preference, but I might be biased as I make heavy use of
> connection tracking and fwmark based routing in combination.
This was my conclusion as well. So I'll go for this solution.
--
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
next prev parent reply other threads:[~2002-06-04 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 14:50 [RFC] matching tproxied packets Balazs Scheidler
2002-06-04 15:14 ` Henrik Nordstrom
2002-06-04 16:28 ` Balazs Scheidler [this message]
2002-06-04 16:37 ` Henrik Nordstrom
2002-06-05 6:53 ` Jozsef Kadlecsik
2002-06-05 10:21 ` Balazs Scheidler
2002-06-05 11:02 ` Jozsef Kadlecsik
2002-06-05 11:08 ` Balazs Scheidler
2002-06-05 13:45 ` Henrik Nordstrom
2002-06-06 5:40 ` Harald Welte
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=20020604162837.GA2365@balabit.hu \
--to=bazsi@balabit.hu \
--cc=hno@marasystems.com \
--cc=netfilter-devel@lists.samba.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.