El 20/10/13 15:24, Antony Stone escribió:
On Sunday 20 October 2013 at 19:09, Alfredo Rezinovsky wrote:
El 20/10/13 13:03, Antony Stone escribió:
There's nothing you can do to stop a packet arriving at your router - you
can only decide what to do with it afterwards.
The package arrives to my router but it can be delayed before reaches
app layer.
Ah, sorry - I had thought that you were asking if it was possible to limit the
bandwidth of traffic coming in over your ISP link.
Obviously, you can restrict the bandwidth of the connection between your
router and Squid, as you are already doing:
I know how to do it with qsdisc in linux. I can queue them and let them
pass with delay.
If that provides the effect you are seeking, I'd say that is the best
approach.
All I want to know is if I can do this with squid.
No, since the receiver can never really control incoming bandwidth. Only the
transmitter can limit the rate data goes over a link (whether that's your ISP
Internet connection, or the hope between your router and Squid).
Squid's delay pools can obvious limit the bandwidth from Squid to the clients,
but that's only an indirect way of limiting the bandwidth from the source into
Squid.
It looks to me like you're doing it the best way possible already.
Delaying the packets arribal to their final destination do limits the
incoming bandwith. The packets arribes late, the acks are sent late. TCP
flowcontrol takes care of the rest.
