All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 30 Nov 2009 12:10:04 +0100	[thread overview]
Message-ID: <4B13A80C.6070607@trash.net> (raw)
In-Reply-To: <412e6f7f0911292039v74b89b4cieca5e2a043bad43d@mail.gmail.com>

Changli Gao wrote:
> On Fri, Nov 27, 2009 at 7:47 PM, Patrick McHardy <kaber@trash.net> wrote:
>> They don't need to forward anything, conntrack handles the packet before
>> routing.
>>
> 
> Think about this topologic:
> 
> Attacker -> router1 -> router2 -> ... -> Linux Router -> Apache.
> 
> the packets in the other direction won't be sent to the Linux Router,
> as the other routers will routed them to the other place.

Yes, in that case it could help.

> Case 2:
> 
> Attacker ---+
>                 +-- Linux Router --> WAN
> Victim-------+
> 
> If we do sth. like RPF before entering conntrack, the packets in the
> other direction won't be in.

RPF doesn't help since its also done after conntrack.


  reply	other threads:[~2009-11-30 11:10 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
2009-11-27 11:47           ` Patrick McHardy
2009-11-30  4:39             ` Changli Gao
2009-11-30 11:10               ` Patrick McHardy [this message]
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=4B13A80C.6070607@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.