From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: KOVACS Krisztian <hidden@balabit.hu>
Cc: Kovesdi Gyorgy <kgy@deverto.com>,
netfilter-devel@lists.netfilter.org,
Balazs Scheidler <bazsi@balabit.hu>
Subject: Re: conntrack for multiple interfaces
Date: Tue, 17 Jan 2006 13:48:37 +0100 [thread overview]
Message-ID: <43CCE7A5.80000@gmx.net> (raw)
In-Reply-To: <200601171319.51023@nienna>
KOVACS Krisztian schrieb:
> Hi,
>
> On Tuesday 17 January 2006 12.48, Carl-Daniel Hailfinger wrote:
>
>>>Conntrack is interface independent, however it does not handle when
>>>tuples collide, it assumes they are part of the same connection. (ie.
>>>it does not work, unless your IP space is actually divided between
>>>interfaces and connections never collide)
>
>
> Yes, but current mode of operation does work in most cases.
>
>
>>That's unfortunate. IIRC someone posted a patch to netfilter-devel half
>>a year ago (sorry, no exact date) to address that issue. Was there some
>>reason not to include it back then?
>>The only problem with that patch I can think of right now would be load
>>balancing over multiple links.
>
>
> Apart from breaking a couple of scenarios, what would be the advantage of
> differentiating connections per interface?
The scenario of the OP (multiple interfaces with the same IP range) would
work without tuple collisions. And double NAT would be possible as well
with only one machine.
Regards,
Carl-Daniel
prev parent reply other threads:[~2006-01-17 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 12:55 conntrack for multiple interfaces Kovesdi Gyorgy
2006-01-17 8:27 ` KOVACS Krisztian
2006-01-17 8:55 ` Balazs Scheidler
2006-01-17 11:48 ` Carl-Daniel Hailfinger
2006-01-17 12:19 ` KOVACS Krisztian
2006-01-17 12:48 ` 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=43CCE7A5.80000@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=bazsi@balabit.hu \
--cc=hidden@balabit.hu \
--cc=kgy@deverto.com \
--cc=netfilter-devel@lists.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.