hi,
On Sat, 2005-07-30 at 21:38 -0300, :: L i n u XK i D :: wrote:
> Thank you very much...
>
> What values are recommended for diferent situations ?
>
> for a Vsat link ? ADSL ? LAN ? ... and so on...
For a vsat link, it depends on who's indoor unit your using -- if you're
running behind a Gi
On Sun, 2005-07-31 at 05:42 -0700, Gabriel wrote:
> Querying google for "tcp window size" returns some links. I
> don't know the recommended values and I don't know either
> if you can play with this value in linux,
AFAIK, this value isn't something which QoS can handle or dynamically
change. Thi
Querying google for "tcp window size" returns some links. I
don't know the recommended values and I don't know either
if you can play with this value in linux, or if it is wise.
There is built-in flow control in the TCP protocol and it
adjusts the window size according to your available
bandwidth.
Thank you very much...
What values are recommended for diferent situations ?
for a Vsat link ? ADSL ? LAN ? ... and so on...
is important to set this value on linux ?
If you have a URL to get more information, please post
it .
thanks again...
andres.
->
->
-> The TCP header has a 16 bits
The TCP header has a 16 bits field that specifies (and now
I'm quoting from the RFC 793): "The number of data octets
beginning with the one indicated in the acknowledgment
field which the sender of this segment is willing to
accept." In plain english: how much "useful" data you can
accept from the
