All of lore.kernel.org
 help / color / mirror / Atom feed
From: "rio@martin.mu" <rio@martin.mu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB burstable for 2 interface , how ?
Date: Thu, 03 Jul 2003 09:38:54 +0000	[thread overview]
Message-ID: <marc-lartc-105722537704125@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105722285902235@msgid-missing>

It wont work..
eth0 only for public ip traffic. It wont handle private network traffic.
Traffic to private network can be manage through eth1 & eth2

I guess the answer is IMQ .. i'll try ..
Documentation please, or perhaps docum.org already have documentation
regarding IMQ ?

Regards,
Rio Martin.


Original Message:
-----------------
From: ???????? ????? skekes@pylones.gr

Well this can be done easily
You have to define a class having rate and ceiling 1024 kbps ( Kilobytes 
 if you want kilobits make its kbits ) in order not to exceed this limit.
Then you have to create two subclasses for the two networks by having as 
rate 512 and ceiling 1024. Then you must make the apropriate filters  
that will  classify the traffic in the right flows.
All theese for eth0.
So when the 192.168.1.0 is idle 192.168.2.0 will allocate all the 1024 
kbps bandwidth but when both will have traffic then they will take 512 each.



--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .


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

  parent reply	other threads:[~2003-07-03  9:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03  8:56 [LARTC] HTB burstable for 2 interface , how ? rio
2003-07-03  9:12 ` Stef Coene
2003-07-03  9:12 ` ???????? ?????
2003-07-03  9:18 ` Martin Devera
2003-07-03  9:38 ` rio [this message]
2003-07-03  9:50 ` Stef Coene
2003-07-03 11:45 ` Joel
2003-07-04 16:39 ` Don Cohen
2003-07-07  3:54 ` Leonardo Balliache
2003-07-09  3:22 ` Leonardo Balliache

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-105722537704125@msgid-missing \
    --to=rio@martin.mu \
    --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.