All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Soulfly" <zob_soulfly@hotmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb
Date: Wed, 20 Mar 2002 12:20:17 +0000	[thread overview]
Message-ID: <marc-lartc-101662694824709@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101661742904753@msgid-missing>

If 1.2.3.1 is absolute priority you should use the prio qdisc and put in a
filter that brings 1.2.3.1's traffic to a band with higher priority (read
the LARTC HOWTO in http://lartc.org/ ).  If you want to give 1.2.3.2 minimum
bandwidth to use (like 10 kbps) then I recommend HTB (
http://luxik.cdi.cz/~devik/qos/htb/ ) but you must patch both kernel and tc.

In either case or if you decide to use anything else you should understand
the problem domain. Start with readning LARTC-HOWTO.

----- Original Message -----
From: "George Tsuladze" <gio@ultracom.ge>
To: <lartc@mailman.ds9a.nl>
Sent: Wednesday, March 20, 2002 10:43 AM
Subject: [LARTC] htb


> How can i do the following: i have 100 kb leased line. I have 2 ips in
> my network 1) 1.2.3.1 2) 1.2.3.2 , i gave all of them 100 kbps, but if
> 1.2.3.1 needs 80 kb, and 1.2.3.2 downlloads with 90, 1.2.3.1 must get 80
> kb, and 1.2.3.2 continue download with 10 kbps.
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-03-20 12:20 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20  9:43 [LARTC] htb George Tsuladze
2002-03-20 12:20 ` Soulfly [this message]
2002-05-04 11:42 ` Stef Coene
2002-09-24 14:12 ` [LARTC] HTB Rimas
2002-09-24 14:12 ` Rimas
2002-09-24 14:17 ` Marc-Christian Petersen
2002-09-24 14:23 ` Esteban Maringolo
2002-09-24 14:30 ` Rimas
2002-09-24 14:55 ` Rimas
2002-09-24 15:00 ` Marc-Christian Petersen
2002-09-24 15:14 ` Rimas
2002-09-24 15:14 ` Rimas
2002-09-24 15:51 ` Esteban Maringolo
2002-09-24 16:16 ` Stef Coene
2002-09-25  4:27 ` mdew
2002-09-25  7:59 ` Stef Coene
2002-09-26 14:36 ` raptor
2002-11-08 13:45 ` Chandrashekhar Rane
2002-12-27 20:14 ` Reginald R. Richardson
2002-12-27 21:59 ` Stef Coene
2003-05-13 18:00 ` [LARTC] htb Evgeni Gechev
2003-05-13 18:34 ` Stef Coene
2003-05-13 19:03 ` Evgeni Gechev
2003-05-13 19:40 ` Stef Coene
2003-05-13 19:47 ` Evgeni Gechev
2003-05-13 19:53 ` Stef Coene
2003-05-13 20:47 ` Evgeni Gechev
2003-05-14 10:01 ` Stef Coene
2004-01-15  7:21 ` [LARTC] HTB Cristea Virgil Ionut
2004-01-15 12:12 ` Andre Correa
2004-04-09 23:09 ` Arturas Lapiene
2004-10-14 18:23 ` sistemas
2004-10-14 20:03 ` Jason Boxman
2004-10-17 11:44 ` [LARTC] htb James Lista
2004-10-17 12:08 ` James Lista
2004-10-17 12:19 ` Andreas Klauer
2004-10-17 12:41 ` James Lista
2004-10-17 12:53 ` ja
2004-10-17 13:02 ` James Lista
2004-10-17 13:20 ` Andreas Klauer
2004-10-17 13:22 ` Andreas Klauer
2004-11-10 14:48 ` [LARTC] HTB "Marcus Schäfer"
2007-06-10 16:27 ` Marco Aurelio
2007-06-11  8:09 ` m.innocenti
  -- strict thread matches above, loose matches on Subject: below --
2002-05-04  8:53 [LARTC] htb Anjaneya Pal
2002-05-04  8:56 ` Martin Devera

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-101662694824709@msgid-missing \
    --to=zob_soulfly@hotmail.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.