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.
>
