From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: therbert@google.com, netdev@vger.kernel.org
Subject: Re: [RFC PATCH] tcp: Replace possible syn attack msg by counters
Date: Thu, 11 Aug 2011 08:33:07 +0200 [thread overview]
Message-ID: <1313044387.3066.8.camel@edumazet-laptop> (raw)
In-Reply-To: <20110810.231318.959972077845910551.davem@davemloft.net>
Le mercredi 10 août 2011 à 23:13 -0700, David Miller a écrit :
> From: Tom Herbert <therbert@google.com>
> Date: Wed, 10 Aug 2011 22:38:02 -0700 (PDT)
>
> > Rather than printing the message to the log, use a mib counter to keep
> > track of the count of occurences of syn cookies being used or syn
> > being dropped when request queue is full.
> >
> > Rationale is these messages can fill up /var/log/messages on server
> > which is simply under heavy load... I'm not sure how much more useful
> > they would be in identifying a server DOS attack (compared to
> > counters).
> >
> > Signed-off-by: Tom Herbert <therbert@google.com>
>
> Print the message once, and also do the counters.
>
> Say something like "Possible SYN flooding, see SNMP counters." or
> similar.
>
> Because if people are grepping for that message in their logs, they
> will now have a false sense of confidence seeing it not being there
> any more.
An alternative would be to guard the message by net_msg_warn
(/proc/sys/net/core/warnings)
LIMIT_NETDEBUG(KERN_INFO "TCP: Possible SYN flooding on port %d. %s.\n"
...)
next prev parent reply other threads:[~2011-08-11 6:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 5:38 [RFC PATCH] tcp: Replace possible syn attack msg by counters Tom Herbert
2011-08-11 6:13 ` David Miller
2011-08-11 6:33 ` Eric Dumazet [this message]
2011-08-12 6:08 ` [PATCH] tcp: Use LIMIT_NETDEBUG in syn_flood_warning() Eric Dumazet
2011-08-15 3:20 ` Tom Herbert
2011-08-15 6:39 ` David Miller
2011-08-30 13:21 ` [PATCH v2] tcp: Change possible SYN flooding messages Eric Dumazet
2011-09-15 19:06 ` David Miller
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=1313044387.3066.8.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--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