All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Martijn Lievaart <m@rtij.nl>,
	Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [Proposal] ip_conntrack_tuple extension for advanced matching
Date: Tue, 26 Sep 2006 16:45:22 +0200	[thread overview]
Message-ID: <45193D02.1010509@gmx.net> (raw)
In-Reply-To: <45193250.4080000@trash.net>

Patrick McHardy wrote:
> Carl-Daniel Hailfinger wrote:
>> Martijn Lievaart wrote:
>>
>>> <citaat van="Patrick McHardy">
>>>
>>>> Pablo Neira Ayuso wrote:
>>>>
>>>>> Carl-Daniel Hailfinger wrote:
>>>>>
>>>>>
>>>>>> Would a patch for adding such a feature be accepted into mainline?
>>>>> IHMO, your numering schema is not convenient. I would not accept such
>>>>> patch since I can't see any other utility apart from supporting your
>>>>> setting.
>>>> Me neither, the network setup is obviously broken. Its also a bit harder
>>>> than just extending the conntrack keys, you need also need to take care
>>>> of NAT unique tuple generation, expectations and ICMP error tracking.
>>>> That still leaves a few corner cases, but nothing terribly important.
>>> This would be possible with multiple network stacks (aka virtual routers),
>>> something I've been thinking about but is way beyond my capabilities.
>>
>> IIRC that has already been implemented by Extreme Networks in their
>> Linux-based routers. The only problem is that I can't find any source
>> code from them. Will inquire further.
> 
> OpenVZ might help. I think it virtualizes the conntrack table etc., so
> you could use one virtual instance for each interface and NETMAP them
> to seperate networks.

Thanks! I'll look at that code.


Regards,
Carl-Daniel

  reply	other threads:[~2006-09-26 14:45 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 [this message]
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=45193D02.1010509@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --cc=kaber@trash.net \
    --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.