All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: ip_conntrack_tuple and marks
Date: Sun, 24 Sep 2006 19:57:30 +0200	[thread overview]
Message-ID: <4516C70A.3050502@gmx.net> (raw)
In-Reply-To: <4515F7F8.9030000@netfilter.org>

Pablo Neira Ayuso wrote:
> Carl-Daniel Hailfinger wrote:
>>
>> is it possible to add a nfmark field to ip_conntrack_tuple
>> so that only packets with a certain mark set are matched to
>> a connection? I'm trying to filter/nat multiple independent
>> connections with same ip/proto/port tuples on both sides
>> and the only distinguishing property of the different
>> connections is their nfmark. Using NOTRACK doesn't help
>> because it can only exclude packets from tracking, not
>> match packets to different expectations.
> 
> Could the connmark match/target be what you need?

Unfortunately, connmark does exactly the opposite of what
I'm trying to achieve.

connmark: get/set fwmark based on flow
my problem: handle different flows with identical
  srcip/dstip/sport/dport/proto tuples where the only
  difference is the packet fwmark

Example (what I hope to get working)
SYN packet from 10.0.0.1:1024->10.0.0.2:80 fwmark 1 creates
one connection.
SYN packet from 10.0.0.1:1024->10.0.0.2:80 fwmark 2 creates
another connection independent of the first. Current netfilter
code considers both packets to belong to the same connection.


Regards,
Carl-Daniel

  reply	other threads:[~2006-09-24 17:57 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 [this message]
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

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=4516C70A.3050502@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --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.