All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RE: LARTC digest, Vol 1 #1523 - 17 msgs
Date: Wed, 07 Jan 2004 17:17:49 +0000	[thread overview]
Message-ID: <200401071817.49598.stef.coene@docum.org> (raw)
In-Reply-To: <50F73B338A7FD943B7937BBCF99BFBDE2DAE95@mail.sofaware.com>

On Tuesday 06 January 2004 10:43, Aron Brand wrote:
> Hi Roy,
>
> It seems that I wasn't clear. Lets give an example.
>
> I have a machine with a single ethernet interface, with two IP addresses
> A and B. This is done using two virtual interfaces.
> A is my IP address in ISP-A. B is my IP address in ISP-B. The physical
> line to ISP-A is 1.5Mbps. The physical line to ISP-B is 256kbps.
>
> I want to shape the traffic so that, for example, HTTP traffic will take
> no more than 10% of the ISP-B link, and no more than 20% of the ISP-A
> link.
>
> There seems to be no way to do this without the ability to attach a
> qdisc to a virtual interface. Please correct me if I am wrong...
You can do this if this box is also natting.  The difference between packets 
leaving the 2 links is the source address.  You can use the source address to 
put the traffic in 2 different classes.  After that you can create subclasses 
for http traffic.

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/

      reply	other threads:[~2004-01-07 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06  9:43 [LARTC] RE: LARTC digest, Vol 1 #1523 - 17 msgs Aron Brand
2004-01-07 17:17 ` 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=200401071817.49598.stef.coene@docum.org \
    --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.