https://bugzilla.novell.com/show_bug.cgi?id=229848 ------- Comment #24 from okir@novell.com 2007-01-05 07:21 MST ------- John, this is a problem we can do little about. This is neither a bug in our stack nor in the destination system's stack - I assume there's a connection tracking router/filter at the remote site that does not understand window scaling. This problem has been cropping up for quite some time on the netdev mailing list and in other places. Essentially what happens is that the router happily passes all TCP options during the SYN handshake, including the options announcing window scaling. However, the router doesn't understand window scaling, so when it sees the Linux client announcing a window of "47" (which is really (47 << some scaling factor), it will discard any packets that are not fully inside that 47 byte window. When the stack announces different windows which (scaled or unscaled) are large enough, you will not see any connection hangs (but the download may be rather slow). The fact this issue didn't show up with 10.1 is more of a coincidence, I suspect - the window size announced by the stack depends on lots of factors, including the rmem values and your amount of physical RAM. There's really nothing we can do about this, short of turning off window scaling globally for all peers. The only thing you can do is turn off window scaling locally. (Note - I think this should be put into an article somewhere on the wiki) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.