From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] device independent qdisc?
Date: Wed, 20 Mar 2002 11:23:48 +0000 [thread overview]
Message-ID: <marc-lartc-101662348517601@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101662273316150@msgid-missing>
On Wednesday 20 March 2002 12:09, mario.wolff@sercon.de wrote:
> Hello ALL,
> is there a way to have a device independent qdisc, or a qdisc on some kind
> of virtuall interface?
>
> Background: I have a 5-Interface-Router with one Internet-Uplink. The
> Router should connect the clients on the other Interfaces to the Internet
> and to each other client. As i understood the hole TC stuff i can only get
> influence of outgoing traffic. In my case i can reduce the traffic of each
> net by putting a qdisc on the netinterface. I´ve done that and it runs
> fine. But the different nets could not take the free bandwith of other nets
> because they have not the same root.
>
> If i could have a device independent qdisc i could take this as root and
> filter the traffic for the the different nets to the classes.
You can use the IMQ device. ALL packets are first queued in this device and
after that it's enqueued in the real device.
http://luxik.cdi.cz/~devik/qos/imq.htm
Or you can take an other box and put that between the router and the uplink.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-03-20 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 11:09 [LARTC] device independent qdisc? mario.wolff
2002-03-20 11:23 ` Stef Coene [this message]
2002-03-20 13:10 ` Martin Devera
2002-03-20 13:53 ` Adrian Chung
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-101662348517601@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.