Bandwidth shaping on the local machine HELP!

Hiya
I would like to know if anyone can help me with a problem RE bandwidth
shaping.

The situation is this. We have a backup server which backs up our
servers via ethernet. Now the server could quite easily saturate the port
on one of the client machines, so we have had to throttle it back in the
software, this however means that when backing up 30 machines the thottle
applies across the whole group and not per machine. So the backup server
isn't using all of the availible bandwidth.

Idealy we want to be able to throttle per machine, but this functionality
will not be availible until somewhere like 2004 or 2005.

I came up with the idea of using the linux kernel to do the bandwidth
shaping on the machines and have been looking into this. What I want to
do, is have a script that will shape the INBOUND traffic to the box, so
hold back the incomming data (drop packets whatever) before it gets to the
backup software, and hence throttling back the server. As the data comes
from the clients this is the neatest way I can see of doing it, not all
clients are capable of QoS and not all are linux (unfortunately).

I have had a play with CBQ.init but this seems to only work on outbound
traffic from the machine, which is great but in the wrong direction.

Does anyone know of a nice way that I could throttle bandwidth on INBOUND
connections, and ideally apply a hierachy, or at least apply the throttle
to multiple IP addresses or an entire subnet.

Many thanks

Graeme

On Friday 05 September 2003 17:27, Graeme Hinchliffe wrote:

[Traffic shaping on inbound traffic]
>
> I have had a play with CBQ.init but this seems to only work on outbound
> traffic from the machine, which is great but in the wrong direction.
> Does anyone know of a nice way that I could throttle bandwidth on INBOUND
> connections [...]

If you want to shape inbound traffic you need to deploy the
Immediate Queueing Device (IMQ). More information at
http://lartc.org/howto/lartc.imq.html
http://trash.net/~kaber/imq/

I don't know whether there are good ready-to-go scripts utilizing
this and allow INBOUND shaping. In the worst case you need to
write your own. :-(

HTH

Ciao, Horst
--
»When pings go wrong (It hurts me too)« E.Clapton/E.James/P.Tscharn

In article <bjaees$1jjp$(E-Mail Removed)>, Horst Knobloch wrote:
> On Friday 05 September 2003 17:27, Graeme Hinchliffe wrote:
>
> [Traffic shaping on inbound traffic]
>>
>> I have had a play with CBQ.init but this seems to only work on outbound
>> traffic from the machine, which is great but in the wrong direction.
>> Does anyone know of a nice way that I could throttle bandwidth on INBOUND
>> connections [...]
>
> If you want to shape inbound traffic you need to deploy the
> Immediate Queueing Device (IMQ). More information at
> http://lartc.org/howto/lartc.imq.html
> http://trash.net/~kaber/imq/
>
> I don't know whether there are good ready-to-go scripts utilizing
> this and allow INBOUND shaping. In the worst case you need to
> write your own. :-(
>
me me me me me

/me steps into the limelight as the audience leaves....

http://digriz.org.uk/jdg-qos-script/

Regards

Alex

Alexander Clouter <alex.junk-(E-Mail Removed)> wrote in message news:<pu8bjb.pro.ln@127.0.0.1>...
> In article <bjaees$1jjp$(E-Mail Removed)>, Horst Knobloch wrote:
> > On Friday 05 September 2003 17:27, Graeme Hinchliffe wrote:
> >
> > [Traffic shaping on inbound traffic]
> >>
> >> I have had a play with CBQ.init but this seems to only work on outbound
> >> traffic from the machine, which is great but in the wrong direction.
> >> Does anyone know of a nice way that I could throttle bandwidth on INBOUND
> >> connections [...]
> >
> > If you want to shape inbound traffic you need to deploy the
> > Immediate Queueing Device (IMQ). More information at
> > http://lartc.org/howto/lartc.imq.html
> > http://trash.net/~kaber/imq/
> >
> > I don't know whether there are good ready-to-go scripts utilizing
> > this and allow INBOUND shaping. In the worst case you need to
> > write your own. :-(
> >
> me me me me me
>
> /me steps into the limelight as the audience leaves....
>
> http://digriz.org.uk/jdg-qos-script/
>
> Regards
>
> Alex


You just need 1 box in between and you can control traffic in either
direction with a commercial add-on to linux. You'll spend more in time
than it costs trying to cobble together stuff that works half as well.
You'll even be able to manage the aggregate (ie set dynamic limits
based on how many servers are active or based on the other traffic on
the network).

www.etinc.com