From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: christoph.paasch@uclouvain.be, David Miller <davem@davemloft.net>,
Martin Topholm <mph@hoth.dk>, netdev <netdev@vger.kernel.org>,
Tom Herbert <therbert@google.com>
Subject: Re: [RFC PATCH] tcp: Fast/early SYN handling to mitigate SYN floods
Date: Thu, 24 May 2012 19:27:26 +0200 [thread overview]
Message-ID: <1337880446.2655.2.camel@edumazet-glaptop> (raw)
In-Reply-To: <1337880065.2388.15.camel@localhost>
On Thu, 2012-05-24 at 19:21 +0200, Jesper Dangaard Brouer wrote:
> Sorry, don't remember.
http://kerneltrap.org/mailarchive/linux-netdev/2010/4/19/6274993
> Sounds really promising, especially coming from the network-ninja :-)
;)
> Yes, this is more an emergency mode.
>
> I was thinking of only handling the SYN cookie case in parallel.
> That should be easier locking wise, right.
>
> I'm also considering writing a netfilter/iptables syn-cookie module, as
> this would allow people to use it in combination with IPset, to e.g
> create a whitelist feature of known-good-hosts (which have completed the
> TCP handshake). But it would be nicer if the base kernel was just fast
> enough to handle these SYN floods.
>
Indeed, I believe I can make this happen eventually in a short term.
prev parent reply other threads:[~2012-05-24 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 13:01 [RFC PATCH] tcp: Fast/early SYN handling to mitigate SYN floods Jesper Dangaard Brouer
2012-05-24 13:20 ` Hans Schillstrom
2012-05-24 17:32 ` Jesper Dangaard Brouer
2012-05-24 13:26 ` Christoph Paasch
2012-05-24 14:51 ` Eric Dumazet
2012-05-24 17:21 ` Jesper Dangaard Brouer
2012-05-24 17:27 ` Eric Dumazet [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=1337880446.2655.2.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=brouer@redhat.com \
--cc=christoph.paasch@uclouvain.be \
--cc=davem@davemloft.net \
--cc=mph@hoth.dk \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).