All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raghuveer <raghuveer-rc@naturesoft.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Please check the follow script for diffserv
Date: Wed, 20 Aug 2003 06:36:09 +0000	[thread overview]
Message-ID: <marc-lartc-106136063625392@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106024505223878@msgid-missing>

Thanks Damion,

I would like to re-confirm the last few days discussion.

		------------------ 
Private --------| eth1      eth0 |-------Internet
ipaddresses     |                |
                ------------------
                   Linux firewall 

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).
3. For CBQ I can use the interface bandwidth(using ethtool or mii-diag) and 'interesting' DSL/ISP speeds for the classes.
4. HTB qdiscs don't need to know any speeds.

Any suggestions and help is invaluably appreciated.

Regards
-Raghu



Damion de Soto wrote:

> Steffen Moser and Raghuveer wrote:
>
> SM> If I then want to shape the traffic I send to the "ppp0" interface,
> SM> which bandwidth would be used for setting up a CBQ?
> SM>
> SM> I suppose that here the "virtual" (e.g. limited by the ISP) bandwidth
> SM> of my "ppp0" connection (e.g. 128 kbit/s) is the interesting one, not
> SM> the bandwidth of my "eth0" (10 Mbit/s), because the CBQ is attached
> SM> to the "ppp0" device and has nothing to do with the underlaying 
> "eth0".
> SM>
> SM> Is this assumption correct?
> no.
> SM>
> SM> TIA,
> SM> Steffen
> R>
> R> Can you please tell me for HTB and CBQ what bandwidth should I use 
> whether
> R> interface bandwidth or real/actual bandwidth....?
> R> Regards
> R> -Raghu
>
> as it says in the HOW-TO, the cbq device uses the ethernet speed 
> (bandwidth) for idle time calculations.  so when you create a cbq 
> qdisc, it needs to know either 10mbit or 100mbit.
> you then use the 'interesting' DSL/ISP speeds for the classes.
>
> htb qdiscs don't need to know any speeds.
>
> regards.
>


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

  parent reply	other threads:[~2003-08-20  6:36 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 [this message]
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-106136063625392@msgid-missing \
    --to=raghuveer-rc@naturesoft.net \
    --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.