From: Steffen Moser <lists@steffen-moser.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Please check the follow script for diffserv
Date: Tue, 19 Aug 2003 09:42:20 +0000 [thread overview]
Message-ID: <marc-lartc-106128623919143@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106024505223878@msgid-missing>
Hi Damion,
* On Tue, Aug 19, 2003 at 09:41 AM (+1000), Damion de Soto wrote:
> Raghuveer wrote:
>
> >I feel it gets the interface bandwidth.
>
> yes, it does.
> you need the interface bandwidth for the cbq qdisc:
> http://lartc.org/howto/lartc.qdisc.classful.html#AEN935
Given a 10 Mbit/s ethernet device (eth0) which is used to establish a
PPP over ethernet (PPPoE) connection (ppp0) to a broadband ISP (e.g.
using ADSL, SDSL and so on as an underlaying system).
If I then want to shape the traffic I send to the "ppp0" interface,
which bandwidth would be used for setting up a CBQ?
I suppose that here the "virtual" (e.g. limited by the ISP) bandwidth
of my "ppp0" connection (e.g. 128 kbit/s) is the interesting one, not
the bandwidth of my "eth0" (10 Mbit/s), because the CBQ is attached
to the "ppp0" device and has nothing to do with the underlaying "eth0".
Is this assumption correct?
TIA,
Steffen
_______________________________________________
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-19 9:42 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 [this message]
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
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-106128623919143@msgid-missing \
--to=lists@steffen-moser.de \
--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.