From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: TCP listen overflows
Date: Wed, 14 Oct 2015 17:19:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20151014T191218-4@post.gmane.org> (raw)
In-Reply-To: CAN0CFw1B6EFEVmx8RKzLsUqmFeanne6_mb1dOBKhDyXePyjhCA@mail.gmail.com
Grant <emailgrant <at> gmail.com> writes:
> My site when down for about 10 minutes recently and the only
> interesting thing I see in the munin graphs is a massive spike in "TCP
> socket buffer errors", specifically "Listen overflows" at exactly the
> same time. Is that a clue or just a result of the downtime? Nothing
> in the logs.
Hard to tell. What I have done in the past is install a hub/switch
outside your firewall/DMZ with several systems to perform 'mock tests'
via standard penetration tests, packet flooding, DoS, etc etc depending
on your suspicions, and pound on your net
Pentoo linux is also an excellent tool.
hth,
James
next prev parent reply other threads:[~2015-10-14 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 16:11 [gentoo-user] TCP listen overflows Grant
2015-10-14 17:19 ` James [this message]
2015-10-19 23:39 ` [gentoo-user] " Adam Carter
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=loom.20151014T191218-4@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox