From: Nguyen Dinh Nam <64vn@cardvn.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] syn flood protection - inside initiated attacks
Date: Wed, 23 Mar 2005 10:02:59 +0000 [thread overview]
Message-ID: <42413ED3.6070109@cardvn.net> (raw)
In-Reply-To: <0c3e01c52f84$99a4f380$0100a8c0@newlife>
IMO, you have to --limit for each of the computer separately (1 chain
for each IP address), otherwise you will block both the instruder and
the legitimate users.
Perhaps the better solution is to install an IDS and completely block
instruder, wait until he/she contacts you and ask for worm removal
before removing the blockage.
Ming-Ching Tiew wrote:
>Perhaps someone will help me on this :-
>
>I have read a lot of examples of syn flood protect on the INPUT chain.
>That I have no question at all.
>
>I wonder if it make sense to perform syn flood protection
>at the FORWARD chain ? If packets are originated from a
>LAN worm, and are not targetted at the firewall itself, but
>rather at hosts in the internet, will it cause problem with
>the firewall itself, such as iptables connection table full etc ?
>
>I tried to do it, to be specific, I tried this :-
>
> iptables -N lan-syn-flood
> iptables -A lan-syn-flood -m limit --limit 1/s --limit-burst 4 -j RETURN
> iptables -A lan-syn-flood -j DROP
>
>Hook it to FORWARD chain,
>
> iptables -I FORWARD -p tcp --syn -j lan-syn-flood
>
>But this will result in denial of service of a lot of "legitimate" traffic.
>I try to increate the limits to bigger values it still does not work,
>primarily my firewall is also doubling as a router across subnet
>and there are a lot of traffic.
>
>Any advise or comments ?
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-03-23 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 8:45 [LARTC] syn flood protection - inside initiated attacks Ming-Ching Tiew
2005-03-23 10:02 ` Nguyen Dinh Nam [this message]
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=42413ED3.6070109@cardvn.net \
--to=64vn@cardvn.net \
--cc=lartc@vger.kernel.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.