In short: a result of your remote host having a buggy TCP stack and Linux protecting you.
Longer: setting up a connection between your server A and remote host B needs A and B to agree on the amount of data to be sent. In the old situation B was able to manipulate the windows size w/o conversing with A. Basically that could mean B could keep readjusting the size (sliding the window size) untill it reaches zero, which would mean A cannot send data, but the connection remains open. That's a nice way to do resource starvation on A :-] The messages you get are the kernel warning the remote side of the connection changed it's receiving window size. In the new situation this can't happen unless A and B keep agreeing. As protection the kernel will try to time out the connection even tho the connection wasn't torn down the proper way.
Last edited by unSpawn; 05-16-2003 at 05:35 AM.
|