All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Leach <raymondl@knowledgefactory.co.za>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: anti-dos
Date: Wed, 28 Jan 2004 12:35:02 +0200	[thread overview]
Message-ID: <1075286102.2000.61.camel@raylinux.internal> (raw)
In-Reply-To: <200401281108.04514.heinrici76@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]

On Wed, 2004-01-28 at 12:08, Axel Heinrici wrote:
> Hi
> 
> On Wednesday 28 January 2004 09:14, Ray Leach wrote:
> >
> > You can use the limit support to limit packet rates:
> >
> > ### syn-flood chain
> > $IPTABLES -N syn-flood
> > $IPTABLES -A syn-flood -i $IFACE_INET -m limit --limit 75/s
> > --limit-burst 100 -j RETURN
> > $IPTABLES -A syn-flood -i $IFACE_DMZ -m limit --limit 75/s
> > --limit-burst 100 -j RETURN
> > $IPTABLES -A syn-flood -i $IFACE_INT -j RETURN
> > $IPTABLES -A syn-flood -j LOG --log-prefix "SYN-FLOOD: "
> > $IPTABLES -A syn-flood -j DROP
> >
> > $IPTABLES -A INPUT -i $IFACE_INT -p tcp --syn -j syn-flood
> > $IPTABLES -A INPUT -i $IFACE_DMZ -p tcp --syn -j syn-flood
> > $IPTABLES -A INPUT -i $IFACE_INET -p tcp --syn -j syn-flood
> >
> I have a questions on this. As I interpret the rules any packet with is 
> not catched by the two limit-rules is targeted to LOG. 
> Due to the huge number of possible SYN-Packets in a dos-attack this does 
> not seem useful to me. Shouldn't there be a "-m --limit 
> 10/minute" in the log-rule?
The LOG rule is so I can trace where the DOS came from. The limit of
75/s is assuming that our 512K line is capable of receiving that many
packets per second (if it isn't, then we better start looking for new
hardware).


> 
> with kind regards
> 	Axel
-- 
--
Raymond Leach <raymondl@knowledgefactory.co.za>
Network Support Specialist
http://www.knowledgefactory.co.za
"lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
Key fingerprint = 7209 A695 9EE0 E971 A9AD  00EE 8757 EE47 F06F FB28
--

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-28 10:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28  7:18 anti-dos Fritz Mesedilla
2004-01-28  8:14 ` anti-dos Ray Leach
2004-01-28 10:08   ` anti-dos Axel Heinrici
2004-01-28 10:35     ` Ray Leach [this message]
2004-01-28 10:42       ` anti-dos Nilesh
2004-01-28 11:14         ` anti-dos Rob Sterenborg
  -- strict thread matches above, loose matches on Subject: below --
2004-01-29  3:30 anti-dos Fritz Mesedilla
2004-01-29  3:34 anti-dos Fritz Mesedilla
2004-01-29  5:55 ` anti-dos Ray Leach

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=1075286102.2000.61.camel@raylinux.internal \
    --to=raymondl@knowledgefactory.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 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.