From: George Alexandru Dragoi <waruiinu@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] limit number of TCP connections.
Date: Mon, 25 Oct 2004 15:12:47 +0000 [thread overview]
Message-ID: <3063e5041025081257f6152f@mail.gmail.com> (raw)
In-Reply-To: <000f01c4ba58$a7df3c90$5c9cfea9@stillnicks>
iptables -I FORWARD -s 192.168.1.202 -p tcp --syn -m state --state NEW
-m limit --limit 50/s --limit-burst 100 -j ACCEPT
iptables -I FORWARD 2 -s 192.168.1.202 -p tcp --syn -m state --state NEW -j DROP
with udps things are a bit simmilar, except you dont need the --syn
On Mon, 25 Oct 2004 17:45:14 +0000, Rio Martin. <rio@martin.mu> wrote:
> On 25 October 2004 am 06:05, Cristiano Soares wrote:
>
>
> > Hi all. I have a simple question. Is that a way to limit the number os TCP
> > or UDP connection of a single HOST in my network? For exemple:
> > I have a host with IP 192.168.1.202 and he is using edonkey, Kazaa, and
> > Bittorrent at the same time, and he also is infected by a virus that opens
> > more than 500 TCP ports at the same time. So, i want to limit that host to
> > be able to open no more then 30 TCP connections at once, so he wouldnt hurt
> > the other users.
> > Thanks in advance,
> > Cristiano Soares
>
>
> Try connlimit patches from Iptables POM
> www.netfilter.org
>
> - Rio.Martin -
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
--
Bla bla
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-10-25 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 6:05 [LARTC] limit number of TCP connections Cristiano Soares
2004-10-25 10:52 ` Rio Martin.
2004-10-25 15:12 ` George Alexandru Dragoi [this message]
2004-10-26 5:39 ` Rio Martin.
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=3063e5041025081257f6152f@mail.gmail.com \
--to=waruiinu@gmail.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 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.