On Thursday 06 February 2003 17:49, Martin A. Brown wrote:
> Stef,
>
> Am I overlooking something obvious?
>
> I'd suggest that Tomas throttles his bandwidth on transmit to the internal
> network. It is a router, so very little traffic will be initiated from
> the router itself.
>
> Why not perform traffic control on packets transmitted to the Internet on
> the outward facing NIC.
>
> Then perform traffic control on packets received from the Internet on the
> inward facing NIC.
>
> What's wrong with this?
Euh nothing :)
But you have the same problem. You are controlling already received data. So
you can only hope that the other end of the link stops sending data if you
drop packets.
Stef
>
> -Martin
>
> : > well, if tcp throttles down at the point where packets are dropped is
> : > of course good, but still, when a download is peaking at the maximum
> : > speed minus a couple kbits, the delay is terrible, that's what i want
> : > to change. any idea?
> :
> : You can give the download 98% of the link so there is always 2%
> : available for something else. It also helps to throttle down _all_
> : incoming bandwidth to 99% of your link so _you_ are shaping and not your
> : router.
> :
> : Stef
> :
> : > > > it is a 2mbit fiber stub network which looks pretty much like
> : > > > this:
> : > > >
> : > > > lan - router - fw - isp - internet
> : > > >
> : > > > the egress qos is at the moment at the router which pretty much
> : > > > says "prioritize interactive sessions".
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
