From: devik <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: AW: [LARTC] Shaping incoming traffic?
Date: Mon, 19 Nov 2001 21:29:56 +0000 [thread overview]
Message-ID: <marc-lartc-100620535215047@msgid-missing> (raw)
Hi,
You didn't send question to the list, why ?
I'm resending this to the list too.
Probably you don't ask me about how to setup linux qos
(there are sufficient resources to read).
The fundamental part of your question is probably how
to setup limit on total bw (in+out).
It is not generaly possible. But as I'm thinking about
it you should be able to use IMQ for this. You would
use simple HTB queue and create class for each direction.
Classify packets by source IP (to detect their direction).
Then attach htb to imq device.
It should work. If you succeed you could send more information
here.
devik
On Mon, 19 Nov 2001, Gunther Stammwitz wrote:
> Hello Martin,
>
> I'm running one Linux-PCs a router for a /20-Network and would like to do
> traffic-shaping.
>
> To be more exact: I'd like to sell my customers a bandwidth like 1 Mbits or
> 3 Megabits... as _total_ Bandwidth (this means: combined up and downsteam
> together.).
>
> What's the necessary setup using iproute2 to shape the traffic?
>
>
> Thanks a lot,
> Gunther Stammwitz
>
>
> -----Ursprungliche Nachricht-----
> Von: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]Im
> Auftrag von Martin Devera
> Gesendet: Sonntag, 18. November 2001 14:49
> An: Manfred Bartz
> Cc: Linux Advanced Routing and Traffic Control
> Betreff: Re: [LARTC] Shaping incoming traffic?
>
>
> 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/
reply other threads:[~2001-11-19 21:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-100620535215047@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.