From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Eric Leblond <eric@inl.fr>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Martijn Lievaart <m@rtij.nl>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: ip_conntrack_tuple and marks
Date: Tue, 26 Sep 2006 00:23:56 +0200 [thread overview]
Message-ID: <451856FC.9050408@gmx.net> (raw)
In-Reply-To: <1159222083.18152.12.camel@localhost.localdomain>
Eric Leblond wrote:
>
> In the setup you describe and in almost all cases. The differences is in
> the interfaces.
>
> Could it be a a way to differentiate the connection tracking entries ?
I first hoped so. Then I thought about expectation setup and how messy
it would get to guess the incoming interface for a packet in the opposite
direction. And it would also break some cases of load balancing where
packets may leave and/or enter through multiple interfaces. That's where
I gave up on the idea to base this on incoming interface.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
prev parent reply other threads:[~2006-09-25 22:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 20:33 ip_conntrack_tuple and marks Carl-Daniel Hailfinger
2006-09-24 3:14 ` Pablo Neira Ayuso
2006-09-24 17:57 ` Carl-Daniel Hailfinger
2006-09-24 22:03 ` Martijn Lievaart
2006-09-25 14:04 ` Carl-Daniel Hailfinger
2006-09-25 18:42 ` Martijn Lievaart
2006-09-25 20:52 ` [Proposal] ip_conntrack_tuple extension for advanced matching Carl-Daniel Hailfinger
2006-09-25 23:48 ` Pablo Neira Ayuso
2006-09-26 10:00 ` Patrick McHardy
2006-09-26 13:45 ` Martijn Lievaart
[not found] ` <60318.2001:888:19e1::53.1159278334.squirrel@dexter>
2006-09-26 13:54 ` Carl-Daniel Hailfinger
2006-09-26 13:59 ` Patrick McHardy
2006-09-26 14:45 ` Carl-Daniel Hailfinger
2006-09-25 21:56 ` ip_conntrack_tuple and marks Eric Leblond
2006-09-25 22:02 ` Carl-Daniel Hailfinger
2006-09-25 22:08 ` Eric Leblond
2006-09-25 22:23 ` Carl-Daniel Hailfinger [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=451856FC.9050408@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=eric@inl.fr \
--cc=m@rtij.nl \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@netfilter.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.