From: Brent Clark <bclark@eccotours.co.za>
To: netfilter@lists.netfilter.org
Subject: Re: use of -m limit for Syn Flood protection
Date: Sat, 14 Oct 2006 18:45:41 +0200 [thread overview]
Message-ID: <45311435.20604@eccotours.co.za> (raw)
In-Reply-To: <561dc3260610140717i45c75303weaa16bf327bd1f6d@mail.gmail.com>
Jiann-Ming Su wrote:
> If you're trying to limit the SYNs to 4/sec, then the --limit should
> be "--limit 4/s" along with the --limit-burst 4. Though, 4 SYNs per
> second is hardly a syn flood. Also, you may want to specify the
> destination port of the syn flood to give more grainular control.
Hi Jiann
Thank you for your reply.
May I ask what you would consider a more realistic limit /value.
I currently have ports 25, 80 and 443 open. I would like to strive to get a respectable value that would cater for these ports.
Kind Regards
Brent Clark
next prev parent reply other threads:[~2006-10-14 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 13:16 use of -m limit for Syn Flood protection Brent Clark
2006-10-14 14:17 ` Jiann-Ming Su
2006-10-14 16:45 ` Brent Clark [this message]
2006-10-14 20:03 ` Jiann-Ming Su
2006-10-15 12:24 ` Pascal Hambourg
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=45311435.20604@eccotours.co.za \
--to=bclark@eccotours.co.za \
--cc=netfilter@lists.netfilter.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