From: Thomas Braun <tb@westend.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Syn Flood Protection
Date: Thu, 18 Apr 2002 09:42:39 +0000 [thread overview]
Message-ID: <marc-lartc-101912302203653@msgid-missing> (raw)
Hallo Group,
i want to implement a syn Flood Protection on our linux Router.
on our Cisco we have this Access-list and rat-limit
rate-limit input access-group 190 128000 128000 128000 conform-action transmit exceed-action drop
access-list 190 deny tcp any any established
access-list 190 permit tcp any any
access-list 190 deny ip any any
now i was trying to wrote the same config with tc
iptables -A PREROUTING -i $uplinkdev -t mangle -p tcp --syn -j MARK --set-mark 1
tc qdisc add dev $uplinkdev handle ffff: ingress
tc filter add dev $uplinkdev parent ffff: protocol ip prio 50 handle 1 fw police rate 128kbit burst 10 mtu 15k drop flowid :1
But many from our Customers can't connect to our Webservers.
what is wrong on my config?
cu thomas braun
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-04-18 9:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-lartc-101912302203653@msgid-missing \
--to=tb@westend.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox