From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Please check the follow script for diffserv
Date: Wed, 20 Aug 2003 19:30:48 +0000 [thread overview]
Message-ID: <marc-lartc-106140792909727@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106024505223878@msgid-missing>
Raghuveer,
: I would like to re-confirm the last few days discussion.
Good summary.
: 1. For shaping the incomming and outgoing traffic at eth0 I can use
: IMQ + HTB/CBQ with NAT(--set-mark option).
: 2. Another way I can shape the incomming and outgoing traffic is :
: incomming traffic at eth1 interface with CBQ/HTB and outgoing
: traffic at eth0 with CBQ/HTB with NAT(--set-mark option).
Yes and yes.
: 3. For CBQ I can use the interface bandwidth(using ethtool or
: mii-diag) and 'interesting' DSL/ISP speeds for the classes.
Yes, to reiterate Stef's posting of earlier today.....
CBQ "bandwidth" (parameter)
must be the speed of the real device.
10Base-T card? Use 10mbit.
100Base-T card? Use 100mbit.
CBQ "rate" (parameter)
is the desired rate.
This is the bandwidth "speed" knob. Traffic you transmit
will be shaped to this rate.
: 4. HTB qdiscs don't need to know any speeds.
Sort of. If you mean that HTB qdiscs need no knowledge of the real device
speed, that is accurate. HTB uses tokens (replenished at rate) to
determine the rate at which packets will be dequeued.
It seems to me that you have accurately understood and restated the
discussion.
Best of luck,
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-08-20 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 8:29 [LARTC] Please check the follow script for diffserv anzp
2003-08-07 12:42 ` Steffen Moser
2003-08-07 16:45 ` Stef Coene
2003-08-14 9:13 ` Raghuveer
2003-08-14 13:41 ` Martin A. Brown
2003-08-15 10:02 ` Steffen Moser
2003-08-18 11:16 ` Raghuveer
2003-08-18 23:41 ` Damion de Soto
2003-08-19 9:42 ` Steffen Moser
2003-08-19 10:23 ` Raghuveer
2003-08-20 0:24 ` Damion de Soto
2003-08-20 6:36 ` Raghuveer
2003-08-20 19:30 ` Martin A. Brown [this message]
2003-08-21 5:11 ` Raghuveer
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-106140792909727@msgid-missing \
--to=mabrown-lartc@securepipe.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.