Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Two-way Shared Traffic shaping and NAT
Date: Wed, 19 Dec 2001 13:38:03 +0000	[thread overview]
Message-ID: <marc-lartc-100876918311940@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100874928107102@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 ;-)

precisely it is virtual network device. It can be used for two-way
shaping and several people already uses it ..
devik


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

  parent reply	other threads:[~2001-12-19 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19  8:17 [LARTC] Two-way Shared Traffic shaping and NAT Sumit Pandya
2001-12-19 10:17 ` Stef Coene
2001-12-19 13:38 ` Martin Devera [this message]
2001-12-19 14:21 ` Michael T. Babcock
2001-12-19 18:02 ` Jerome PETAZZONI

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-100876918311940@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox