From: Patrick McHardy <kaber@trash.net>
To: Changli Gao <xiaosuo@gmail.com>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
netfilter-devel@vger.kernel.org
Subject: Re: Add seperated timeout for the connections that only receive packets in one direction
Date: Fri, 27 Nov 2009 11:02:18 +0100 [thread overview]
Message-ID: <4B0FA3AA.4070702@trash.net> (raw)
In-Reply-To: <412e6f7f0911270159i2e55355end54b64372570b90d@mail.gmail.com>
Changli Gao wrote:
> On Fri, Nov 27, 2009 at 5:42 PM, Jozsef Kadlecsik
> <kadlec@blackhole.kfki.hu> wrote:
>> On Fri, 27 Nov 2009, Changli Gao wrote:
>>
>>> Yes, as nf_conntrack_tcp_timeout_loose_unreply implied, it is for
>>> picked up connections.
>> Connection pickup can be disabled by proper rules or by setting
>> nf_ct_tcp_loose to zero. So in which environment this third method is
>> required? I'm curious what triggered you to write your patch.
>>
>
> In some condition, you can't disable it. It's why we export
> nf_ct_tcp_loose. As a bridge, if its booting breaks connections, users
> won't happy, so we must allow loose mode.
That won't help much. If you're able to spoof packets, you might
as well spoof packets for both direction so SEEN_REPLY is set.
next prev parent reply other threads:[~2009-11-27 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 9:09 Add seperated timeout for the connections that only receive packets in one direction Changli Gao
2009-11-27 9:25 ` Jozsef Kadlecsik
2009-11-27 9:32 ` Changli Gao
2009-11-27 9:42 ` Jozsef Kadlecsik
2009-11-27 9:59 ` Changli Gao
2009-11-27 10:02 ` Patrick McHardy [this message]
2009-11-27 11:47 ` Patrick McHardy
2009-11-30 4:39 ` Changli Gao
2009-11-30 11:10 ` Patrick McHardy
2009-12-01 1:26 ` Changli Gao
2009-12-01 9:14 ` Jozsef Kadlecsik
2009-12-01 9:29 ` Changli Gao
2009-12-01 9:45 ` Jozsef Kadlecsik
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=4B0FA3AA.4070702@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=xiaosuo@gmail.com \
/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.