All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip_conntrack limit --- torrent , DC++ , eMule
Date: Wed, 18 May 2005 03:15:22 +0000	[thread overview]
Message-ID: <428AB34A.B8A37B84@iswest.com> (raw)
In-Reply-To: <a763a15b050516065476bd1e38@mail.gmail.com>

foxy 202 wrote:
> 
> I couldn't find any info how to limit IP to open for example over 200
> ip_conntrack  connections , not only for  single port for  with dport
>  I found connlimit
>     http://netfilter.org/patch-o-matic/pom-base.html#pom-base-connlimit
> 
> but there is port … I cannot limit hole IP
> 
> How can I prevent network from
> ip_conntrack: table full, dropping packet.
> ip_conntrack: table full, dropping packet.
> Increasing of ip_conntrack_max cannot be without limits……
> 
> Any suggestions are welcome

Use your judgement, but I compiled my 2.4 kernel reducing the
tcp_timeout_established from 5 days to 2 days in
src/linux/net/ipv4/netfilter/ip_conntrack_proto_tcp.c which I personally
think is still far too long.  Any TCP connection that is cca 5 minutes
without activity is DEAD AFAIAC.

Don't forget the Layer 7 stuff.  However, finding something to match
becomes ever more difficult.

Google may help with conntrack_max limit?
--
gypsy

> On 5/17/05, gypsy <gypsy@iswest.com> wrote:
> > foxy 202 wrote:
> > >
> > > Hi all,
> > >  i need advice how can i limit ip_conntrack per IP.
> > > clients of network that i support often uses  torrent , DC++ , eMule
> > > clients and i have lost packages  because they open too many ports.
> > >
> > > i have traffic control limits but this obviously isn't enough
> > >
> > > Any advance how to prevent server from this kind problems will be welcome.
> > >
> > > Best regards
> > > Emil
> >
> > The first hit from google on 'netfilter limit per ip'
> > returns:
> >
> > >Try the "dstlimit" match in current versions of netfilter.
> >
> > > Quoting from the man page: "This module allows you to  limit  the  packet  per
> > > second (pps) rate on a per destination IP or per destination port base.  As
> > > opposed to the `limit' match, every  destination ip / destination port has
> > > it's own limit."
> >
> > So what's wrong with YOUR google search?
> > --
> > Gypsy
> >
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-05-18  3:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 13:54 [LARTC] ip_conntrack limit --- torrent , DC++ , eMule foxy 202
2005-05-17  2:52 ` gypsy
2005-05-18  3:15 ` gypsy [this message]
2005-05-19  6:15 ` Krystian Antoni

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=428AB34A.B8A37B84@iswest.com \
    --to=gypsy@iswest.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.