All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Beverley <andy@andybev.com>
To: dmitry.korzhevin@stidia.com
Cc: netfilter@vger.kernel.org
Subject: Re: Bittorrent blocking
Date: Wed, 20 Feb 2013 17:45:19 +0000	[thread overview]
Message-ID: <1361382319.1694.6.camel@andrew-desktop> (raw)
In-Reply-To: <51249E58.1080307@stidia.com>

On Wed, 2013-02-20 at 11:58 +0200, Dmitry Korzhevin wrote:
> Guys, i understand, that this is too frequent question, and i'm already 
> made solid investigation in google, but.. mabe you already have good 
> iptables rules to block such type of traffic (Bittorrent), or maby you 
> can give advice.

What's your reason for blocking? Is it just to stop excessive use of
bandwidth? If so, I'd recommend shaping the traffic instead of blocking,
otherwise you just create an arms race whereby users will try and get
around your blocks (and it's unlikely any block will be perfect).

I've had quite good success with some rudimentary detection rules that
just look for lots of traffic to lots of high port numbers. I wrote it
up here:

http://www.andybev.com/index.php/Fair_traffic_shaping_an_ADSL_line_for_a_local_network_using_Linux

I've not updated the page for a while, but the concept should still work
even if you need to adjust the rules.

Andy



      parent reply	other threads:[~2013-02-20 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51249E58.1080307@stidia.com>
2013-02-20 11:22 ` Bittorrent blocking Humberto Jucá
2013-02-21  2:58   ` Michael Rash
2013-02-20 17:45 ` Andrew Beverley [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=1361382319.1694.6.camel@andrew-desktop \
    --to=andy@andybev.com \
    --cc=dmitry.korzhevin@stidia.com \
    --cc=netfilter@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.