All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] shaping (policing) on a bridge
Date: Wed, 30 Apr 2003 18:55:57 +0000	[thread overview]
Message-ID: <marc-lartc-105172927915676@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105170099614585@msgid-missing>

On Wednesday 30 April 2003 13:08, Girts Folkmanis wrote:
> Hello!
>
> First, excuse me for the dumb questions as currently I don't have much
> experience in this field. I looked through all the documentation and I
> haven't found an answer to my problem.
>
> The situation is following:
>
> I need to do shaping (or is it called policing?) on Linux on the
> incoming traffic _in bridge mode_. Each "user" is shaped according to a
> token bucket filter, so that the rate and bucket size can be configured.
> "User" is determined by IP address, so one "user" could have several IP
> addresses that all point to the same bucket. No borrowing is needed. The
> solution should be CPU-friendly, as the data flow is about 100 Mbps,
> maybe even more.
>
> What combination of software should I use? Ebtables in combination with
> u32 and sch_tbf?
>
> I would be very grateful if you could give me some hints what to look at
> and what documentation to read. There are different guides for
> configuring shaping in IP level, but I haven't found any for bridging.
Policing incoming traffic can be done with the infress qdisc and u32 + 
policers.  A policer is some sort of tbf in the filter.  This is limited in 
usage.  You can only limit some traffic.

If you want to shape incoming bandwidth with htb or cbq, you need the ingress 
qdisc, or shape the outgoing traffic on the other nic.  This can be more 
complex, you can share bandwidth between users in a controlled way.

Stef


-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-04-30 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 11:08 [LARTC] shaping (policing) on a bridge Girts Folkmanis
2003-04-30 18:55 ` Stef Coene [this message]
2003-05-02  9:54 ` Girts Folkmanis
2003-05-02 17:13 ` Stef Coene

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-105172927915676@msgid-missing \
    --to=stef.coene@docum.org \
    --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.