> The router could be sooo crappy that it drops all packets from > TCP streams that have SACK enabled and the client has opened > 200+ SACK connections previously... something like that?
I don't know, maybe. My router is a fairly new model Cisco and is pretty major (i.e. pretty expensive), so it's not just a total piece of crap. Plus, I never restart it when I see these issues. I just turn tcp_sack off, the problem goes away, and I'm able to renable tcp_sack a few hours later and it works fine until many hours later when I see the SYN_SENT problem again. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
