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: Fri, 02 May 2003 17:13:45 +0000	[thread overview]
Message-ID: <marc-lartc-105189682612357@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105170099614585@msgid-missing>

On Friday 02 May 2003 11:54, Girts Folkmanis wrote:
> Hello!
>
> > 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.
>
> Thanks for the answer, but can you point me to what documentation to
> read to do the shaping on _bridge level_? Lots of information about
> shaping on IP level are around, but I have found none on the lower
> level shaping.
Shaping on a bridge is the same as shaping on a router.  So there is no 
special configuration needed to shape on a bridge.  The u32 can be used on a 
router and on a bridge to match the packets.

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/

      parent reply	other threads:[~2003-05-02 17:13 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
2003-05-02  9:54 ` Girts Folkmanis
2003-05-02 17:13 ` Stef Coene [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=marc-lartc-105189682612357@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.