From: "Svein E. Seldal" <Svein.Seldal@solidas.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Connection opening problem (prev: FTP/auth problems (slooow links))
Date: Tue, 15 Oct 2002 23:21:17 +0200 [thread overview]
Message-ID: <3DAC86CD.9030506@solidas.com> (raw)
In-Reply-To: 3DAA80EA.7070106@solidas.com
Hello,
The root of my problem was this:
> [0:0] -A SYNFLOOD -m limit --limit 1/s --limit-burst 4 -j RETURN
> [0:0] -A SYNFLOOD -j DROP
> [0:0] -A CHECK -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j SYNFLOOD
When the HTTP/FTP-clients etc. spawned several connections (in this case
>4) to download files, the router blocked them.
I guess that it adds protection to keep the SYNFLOOD check there. What
are sensible values to use on -m limit, making it work for flooding, yet
not stopping normal clients?
Thanks guys,
Svein
next prev parent reply other threads:[~2002-10-15 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 13:08 FTP/auth problems (slooow links) Svein E. Seldal
2002-10-13 16:48 ` Alistair Tonner
2002-10-13 20:36 ` Svein E. Seldal
2002-10-14 9:52 ` Nuitari
2002-10-13 23:50 ` Antony Stone
2002-10-14 8:31 ` Connection opening problem (prev: FTP/auth problems (slooow links)) Svein E. Seldal
2002-10-15 21:21 ` Svein E. Seldal [this message]
2002-10-15 21:46 ` Antony Stone
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=3DAC86CD.9030506@solidas.com \
--to=svein.seldal@solidas.com \
--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