> After taking a close look at tcp_input, I think I see a senario where this > could happen. Say header prediction handles ~2 GB of data without > problems, then a retransmission happens. snd_wnd starts collapsing as it > should. The header prediction code is correctly skipped as the snd_wnd no > long matches the advertised window. We recover from the retransmission, > *BUT* the code that reopens window is skipped because of rolled over > sequence numbers.
probably in the same sequence, we took a possibly un-necessay timeout because quick recovery was suppressed because of a wrapped snd_recover. These variables should be kept more up to date. --Mark Tinguely To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
