Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Andrew Beverley <andy@andybev.com>
To: binary <dreamer.binary@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: traffic shape per ip
Date: Thu, 19 Sep 2013 21:34:26 +0100	[thread overview]
Message-ID: <1379622866.3407.93.camel@andylaptop> (raw)
In-Reply-To: <523B45EA.5090501@gmail.com>

On Thu, 2013-09-19 at 21:43 +0300, binary wrote:
> i would to limit the bandwidth of some users based on IPs:

[...]

This is not as simple as you might think. In order to shape per-IP,
you'll need to set up a class for each individual IP address, and then
filter to that class. I am not aware of a way to write one rule to say
"limit each IP address to this amount".

Presumably the reason to filter per-IP is to stop single users hogging
the bandwidth. If so, a better approach might be to classify the type of
traffic and then shape on that, or alternatively share bandwidth evenly
per-IP rather than per-connection (as is the default). There is some
information on how to do this on this page at the end of the "downlink"
section:

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

If you have any more questions you might want to use the LARTC mailing
list instead of this mailing list.

Andy



  reply	other threads:[~2013-09-19 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 18:43 traffic shape per ip binary
2013-09-19 20:34 ` Andrew Beverley [this message]
     [not found]   ` <CALFTrnNDLHW0NDJVE_sKRjP7DMsnfKXcuiEXado+p6nYUJpUbA@mail.gmail.com>
2013-09-20 13:17     ` Ray Soucy
2013-10-01 16:47       ` Bob Miller
2013-10-01 16:44   ` Bob Miller
2013-10-01 16:50     ` Andrew Beverley
2013-10-01 17:21       ` Bob Miller

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=1379622866.3407.93.camel@andylaptop \
    --to=andy@andybev.com \
    --cc=dreamer.binary@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox