Discussion:
sysctl for TCP windows scaling
(too old to reply)
Lloyd Parkes
2009-01-11 20:16:41 UTC
Permalink
Is it my imagination, or does net.inet.tcp.win_scale completely fail to switch
TCP window scaling on or off? Maybe this isn't what it's for?

Tcpdump says this "13:35:06.520145 IP 10.40.101.129.65423 > 204.152.190.16.873:
S 2496279258:2496279258(0) win 32768 <mss 1478,nop,wscale
3,sackOK,nop,nop,nop,nop,timestamp 1 0>" for the first packet sent, and sysctl
says this "net.inet.tcp.win_scale = 0".

Cheers
--
Lloyd Parkes
Systems Consultant
Open Systems
Ph: +64 4 890 2437

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Arnaud Lacombe
2009-01-11 22:16:26 UTC
Permalink
Post by Lloyd Parkes
Is it my imagination, or does net.inet.tcp.win_scale completely fail to
switch TCP window scaling on or off?
The variable behind `net.inet.tcp.win_scale' seems to be only active
at TCP init time. There is more place in the code where RFC1323
related options seems hardcoded. It should be the same problem with
the timestamp option.
Post by Lloyd Parkes
Maybe this isn't what it's for?
I guess not, the current code seems to evaluate variables before the
system has a chance to set them.

- Arnaud

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...