From: John Heffner <[EMAIL PROTECTED]>
Date: Tue, 16 May 2006 14:28:23 -0400
> The problem really is that the window_clamp variable is overloaded.
> It's used as a kind of cache for rcvbuf -> window conversion, but also
> as a user-settable bound in window size. On examination, it looks like
>
Andy Furniss wrote:
John Heffner wrote:
Andy Furniss wrote:
I've been doing some testing of my new wan connection and noticed
that when I specify a window with ip route it still changes after a
while.
Looks like this is occurring in
net/ipv4/tcp_input.c:tcp_rcv_space_adjust().
The pro
John Heffner wrote:
Andy Furniss wrote:
I've been doing some testing of my new wan connection and noticed that
when I specify a window with ip route it still changes after a while.
Looks like this is occurring in
net/ipv4/tcp_input.c:tcp_rcv_space_adjust().
The problem really is that th
Andy Furniss wrote:
I've been doing some testing of my new wan connection and noticed that
when I specify a window with ip route it still changes after a while.
Looks like this is occurring in net/ipv4/tcp_input.c:tcp_rcv_space_adjust().
The problem really is that the window_clamp variable i
I've been doing some testing of my new wan connection and noticed that
when I specify a window with ip route it still changes after a while.
Using 2.6.16.11 and latest iproute2.
ip ro del default
ip ro add default via 192.168.0.1 window 28000
ip ro ls
192.168.0.0/24 dev eth0 proto kernel sc
