From: Stef Coene <stef.coene@www.docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Two-way Shared Traffic shaping and NAT
Date: Sat, 22 Dec 2001 08:52:21 +0000 [thread overview]
Message-ID: <marc-lartc-100901134010222@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100900203201914@msgid-missing>
> > Devik is developping something that can help you. It's a virtual qdisc
>
> that holds all packets from all queues before they are queued in the real
> queue. from Devik : " It allows you to implement cross device bandwidth
> sharing.",just wat you need ;-)
>
> May i know status of this devlopment? Can i've any version of this, i mean
> alpha/beta/devlopment/release?
You can find more information on http://luxik.cdi.cz/~devik/qos/. There is
only one relase, but it's so simple, that are no bugs (according to Devik).
> I also want basic as well as advance information about ingress and egress.
> I'm a frequent user of TC/CBQ/IPTABLES/IP but never knew about
> ingress/egress. Some links to the document where i can start all about.
It's simple. On the egress you can do everything you want. But on the
ingress side, you are limit to the ingress qdisc. And that's a qdisc that
can do allmost nothing. But you can use the policy of filters to limit the
bandwidth. I never tried it myself, but other people did.
Stef
--
stef.coene@docum.org
More QOS info : http://docum.org/
Title : "Using Linux as bandwidth manager"
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2001-12-22 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 6:31 [LARTC] Re: Two-way Shared Traffic shaping and NAT Sumit Pandya
2001-12-22 8:52 ` 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-100901134010222@msgid-missing \
--to=stef.coene@www.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.