From: David Cannings <lists@edeca.net>
To: netfilter@lists.netfilter.org
Subject: Re: Synfloods - SNAT slow down
Date: Fri, 23 Apr 2004 08:01:57 +0100 [thread overview]
Message-ID: <200404230801.57077.lists@edeca.net> (raw)
In-Reply-To: <005201c428d1$a2ab2ea0$2800a8c0@jupiter>
On Friday 23 April 2004 02:23, krv wrote:
> We have a Linux gateway (2.4.22) which does NAT for all local hosts.
> Where there is ICMP or SYN floods to be forwarded, the gateway starts
> slowing down an there will be serious drop in packets being forwarded.
You could try using the limit match in your FORWARD chain, with --limit
and --limit-burst to limit the number of ICMP or packets with only the
SYN flag set per second. Your gateway would still have to process the
packets, at least as far as deciding to drop them, but would not have to
forward them on so you might see an improvement in performance.
If you do examine this route, be careful you don't quench good ICMP
packets as there is no retransmission in ICMP and you'll never know if
certain wanted messages didn't get through. For example, host X is
sending you an ICMP flood so netfilter starts to drop ICMP packets, but
host Y tries to send you a host unreachable message.
Also don't forget that even if you decide not to forward the packets they
are still there "on the wire", thus you will not see any improvement with
external speeds.
David
next prev parent reply other threads:[~2004-04-23 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 1:23 Synfloods - SNAT slow down krv
2004-04-23 7:01 ` David Cannings [this message]
2004-04-23 13:43 ` krv
2004-04-23 14:37 ` Rob Sterenborg
2004-04-23 14:55 ` krv
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=200404230801.57077.lists@edeca.net \
--to=lists@edeca.net \
--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 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.