All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stafke@iname.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Setting up CBQ
Date: Fri, 20 Apr 2001 06:17:22 +0000	[thread overview]
Message-ID: <marc-lartc-98774777321385@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98645080606855@msgid-missing>

Daniel Camacho wrote:
> 
> Stef,
> 
> Thank you so much for having to go through all this. I also want to know
> what do I need to enable in the kernel to have this working.  I'm using
> 2.4 kernel.
No problem, just cut-and-past from one of my scripts.  Realy, if you
wanna learn about, take a few PC's, put Linux on them and try ot out. 
For fast setup, download my scripts (see link below) and adabt them to
your needs like I did in my previous mail.

Enable everything in the kernel (as module or build-in).  You can find
it as the last option in submenu "Networking Options".

> 
> I'm a little confused to your following statement.  Do you mean I can't
> throttle incoming bandwidth at the same time as the outgoing bandwidth?
> 
>  >For the upstream direction, you can of course using the same setup to
>  >throttle the output bandwidth of eth1 and eth2.  But you can't use them
>  >together : you can't say that eth2 needs allways 75% of upstream of the
>  >T1.
You can control outgoing bandwidth.  But when you are looking at the
upstream traffic, the data to the DMZ-zone is going out on the eth2 NIC
and the data to the office is going out on the eth1 NIC.  You can
control the data that's going out on ONE NIC, but you can't manage the
data together.  You can't say that the outgoing data on eth2 has to be
at least 75% of the data that's going out on NIC eth1.  There's no way
you can manage the two NIC's together.  You can try to control the
incoming data on NIC eth0 (with a few patches, you can do this with QOS,
but I never tried), but when you use NAT, you don't know wich data
coming in on NIC eth0 is going out on wich NIC because they are all
coming in to the ip-adres of NIC eth0.

Hop you understand what I'm trying to say.


-- 

Staf

More QOS info : http://users.belgacom.net/staf/

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

      parent reply	other threads:[~2001-04-20  6:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-05  6:07 [LARTC] Setting up CBQ Daniel Camacho
2001-04-10  1:51 ` Daniel Camacho
2001-04-10  2:01 ` Daniel Camacho
2001-04-19  9:20 ` Stef Coene
2001-04-20  6: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=marc-lartc-98774777321385@msgid-missing \
    --to=stafke@iname.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.