From: Patrick McHardy <kaber@trash.net>
To: "Damien Thébault" <damien.thebault@gmail.com>
Cc: linux-net@vger.kernel.org, netfilter-devel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: conntrack doesn't always work when a bridge is used
Date: Wed, 19 Dec 2007 20:03:05 +0100 [thread overview]
Message-ID: <47696AE9.6090201@trash.net> (raw)
In-Reply-To: <9a4a382a0712190900v2ba747a0wd4ff243d0e65e9ef@mail.gmail.com>
Damien Thébault wrote:
> Hello,
>
> I sent the quoted mail to linux-net with my problem yesterday, but I
> did a git bisect today and I got the following output :
>
>> 2bf540b73ed5b304e84bb4d4c390d49d1cfa0ef8 is first bad commit
>> commit 2bf540b73ed5b304e84bb4d4c390d49d1cfa0ef8
>> Author: Patrick McHardy <kaber@trash.net>
>> Date: Wed Dec 13 16:54:25 2006 -0800
>>
>> [NETFILTER]: bridge-netfilter: remove deferred hooks
>>
>> Remove the deferred hooks and all related code as scheduled in
>> feature-removal-schedule.
>>
>> Signed-off-by: Patrick McHardy <kaber@trash.net>
>> Signed-off-by: David S. Miller <davem@davemloft.net>
>>
>> :040000 040000 c49ea947455937566b6129991dde5e86f2453aae 6611736ce5c0fcde7627494b66b9ea94e37ea42e M Documentation
>> :040000 040000 d0dd0700fe68f98b52687be3a0c31d73f7b15b81 f8ddf15a0389c5f5b7f2c11d7d0db039a660e1d5 M include
>> :040000 040000 dafccf7ff8657be9adca6b28dbd365cdd6c01ca5 3eeb1cb4b16cc5cb698ab559b47ea6b0991d4d3a M net
>
> With exactly this version, the behaviour is similar with what I see
> with 2.6.23 and 2.6.24-rc5 (see below).
Could you capture the conntrack events of the non-working
case with (run in parallel):
conntrack -E
conntrack -E expect
next prev parent reply other threads:[~2007-12-19 19:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9a4a382a0712180648i7fc958edt6f0d9db83f574c77@mail.gmail.com>
2007-12-19 17:00 ` conntrack doesn't always work when a bridge is used Damien Thébault
2007-12-19 19:03 ` Patrick McHardy [this message]
2007-12-20 8:30 ` Damien Thébault
2007-12-20 10:06 ` Patrick McHardy
2007-12-20 11:06 ` Damien Thébault
2007-12-20 11:07 ` Patrick McHardy
2007-12-20 11:20 ` Damien Thébault
2007-12-20 11:25 ` Patrick McHardy
2007-12-20 13:21 ` Damien Thébault
2007-12-20 16:08 ` Damien Thébault
2007-12-22 7:56 ` Patrick McHardy
2007-12-26 9:54 ` Damien Thébault
2007-12-30 17:53 ` Patrick McHardy
[not found] ` <9a4a382a0801020118n4166e505l5eb84a9f07f620be@mail.gmail.com>
2008-01-11 8:10 ` Damien Thébault
2008-01-11 12:24 ` Patrick McHardy
2008-01-11 12:53 ` Damien Thébault
2008-01-11 12:57 ` Patrick McHardy
2008-01-11 13:25 ` Patrick McHardy
2008-01-11 15:16 ` Damien Thébault
2008-01-11 17:33 ` Patrick McHardy
2007-12-28 14:39 ` Damien Thébault
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=47696AE9.6090201@trash.net \
--to=kaber@trash.net \
--cc=damien.thebault@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-net@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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.