All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping incoming traffic?
Date: Tue, 20 Nov 2001 09:12:46 +0000	[thread overview]
Message-ID: <marc-lartc-100624751625882@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100608970116427@msgid-missing>

Exactly. Ingres is needed when packet end its trip inside
Linux box (so there is no queue to place it to).

devik

On Mon, 19 Nov 2001, Kristian Hoffmann wrote:

> Am I correct in assuming that you only need to use the Ingres qdisc if
> you're not the router between two networks (namely the internet and your
> customers).  We have CBQ/TBF setup for our incoming traffic (internet to
> customer).  Can the same rules be applied in reverse for outgoing traffic
> (customer to internet)?
> 
> Thanks,
> 
> Kristian Hoffmann
> PC-InTOUCH/FireToWire System Administrator
> khoff@pc-intouch.com
> ---
> 
> On Sun, 18 Nov 2001, Martin Devera wrote:
> 
> > It is nerly FAQ. You can use Ingres qdisc to do it and attach
> > policers here.
> > It would be nice to be able to attach every qdisc to incoming interface
> > but it is not possible. There is always problem - when packet already
> > hitted your box why do you want to drop/delay it ?
> > You should to do it on outgoing side of link to your box ..
> > 
> > When you are router (not app box) then you can shape both directions.
> > On your virtual-host note. I already did patch (called IMQ) which 
> > implements virtual inteface allowing to attach single qdisc to multiple
> > outgoing devices.
> > It should be relatively easy to extend it to catch incoming packets
> > too - only there is no time to do it.
> > 
> > best regards, devik
> > 
> > On 19 Nov 2001, Manfred Bartz wrote:
> > 
> > > 
> > > I would like to differentiate incoming traffic streams to guarantee
> > > minimum bandwidth to some services.  However, as per the
> > > Adv-Routing-HOWTO it appears that only outgoing traffic can be shaped.
> > > Is this correct or is there a way of shaping incoming traffic?
> > > 
> > > The problem could possibly be overcome if there is a way of routing 
> > > traffic through a virtual host.  Any tips on how to go about that?
> > > 
> > > -- 
> > > Manfred
> > > 
> > > 
> > > _______________________________________________
> > > LARTC mailing list / LARTC@mailman.ds9a.nl
> > > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
> > > 
> > > 
> > 
> > 
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
> > 
> 
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
> 
> 


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

      parent reply	other threads:[~2001-11-20  9:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-18 13:21 [LARTC] Shaping incoming traffic? Manfred Bartz
2001-11-18 13:48 ` Martin Devera
2001-11-18 14:17 ` Manfred Bartz
2001-11-18 23:50 ` Michael T. Babcock
2001-11-19 10:42 ` Fredrik Björk
2001-11-19 11:07 ` devik
2001-11-20  7:12 ` Kristian Hoffmann
2001-11-20  9:12 ` Martin Devera [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-100624751625882@msgid-missing \
    --to=devik@cdi.cz \
    --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.