From: "Sumit Pandya" <sumit@elitecore.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Two-way Shared Traffic shaping and NAT
Date: Sat, 22 Dec 2001 06:31:05 +0000 [thread overview]
Message-ID: <marc-lartc-100900203201914@msgid-missing> (raw)
Hi all,
From: Stef Coene <stef.coene@docum.org>
> 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?
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.
Thanks for taking time to write in.
-- Sumit
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2001-12-22 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 6:31 Sumit Pandya [this message]
2001-12-22 8:52 ` [LARTC] Re: Two-way Shared Traffic shaping and NAT Stef Coene
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-100900203201914@msgid-missing \
--to=sumit@elitecore.com \
--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.