From: Grant Taylor <gtaylor@riverviewtech.net>
To: James Harrison <jamesharrison@blackicehosting.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: SYN only packets
Date: Fri, 05 Aug 2005 00:51:28 -0500 [thread overview]
Message-ID: <42F2FE60.1070201@riverviewtech.net> (raw)
In-Reply-To: <42F2B892.30507@blackicehosting.com>
Try taking a look at SYN-Cookies in the Linux kernel. This code was
written explicitly for this type of situation.
You can not stop SYN packets as they are the very first packet in the
three way handshake to start a TCP connection. About all you can do
(other than SYN-Cookies) is to rate limit the number of packets per
source IP.
Grant. . . .
James Harrison wrote:
> Hi,
>
> I've been trying to calm down some DDoS attacks on my server, but i've
> been stymied on how to block them- however, as APF's AntiDOS plugin
> captured and reported to root, the really vigorous ones (The ones it
> catches) have no ACK in their headers. SYN, but no ACK. I've read that
> this is a common technique used by DDoSers, but i'm unsure if anything
> else depends on it.
>
> The plan i'm looking at is possibly blocking all packets with SYN
> alone, no ACK.. would this be possible with iptables, and how would
> this affect other web services?
>
> Here's one of the captured packet messages (MAC/IPs are removed
> obviously)
>
> Aug 4 21:02:30 ukdsl21 kernel: ** IN_TCP DROP ** IN=eth0 OUT= MAC=**
> SRC=** DST=** LEN=48 TOS=0x04 PREC=0x00 TTL=116 ID=53191 DF PROTO=TCP
> SPT=4122 DPT=4899 WINDOW=64240 RES=0x00 SYN URGP=0 OPT (020405B401010402)
>
>
> Any ideas?
>
> Sorry if this sounds completely barmy- if it does, do tell :-)
>
> Thanks in advance,
> James Harrison
>
next prev parent reply other threads:[~2005-08-05 5:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 0:53 SYN only packets James Harrison
2005-08-05 5:22 ` Ruben Cardenal
2005-08-05 5:51 ` Grant Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-05 14:26 Derick Anderson
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=42F2FE60.1070201@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=jamesharrison@blackicehosting.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 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.