On Monday, 11. August 2008 23:44:21 David Miller wrote: > Trying to come up with a signature for this bogus stuff is both time > consuming and having a risk of false positives. And I really question > whether this thing is worth it. > > The sane thing to do in this case is to declare the box inoperative > and that it needs to be fixed to avoid this behavior. > > Any reasonable congestion control scheme is going to run into problems > trying to react to the packet patterns this thing creates. It is > therefore not really limited to FRTO so it really shouldn't be treated > like an FRTO problem even though it shows up more pronounced when > FRTO is enabled. David, I agree with you, though I'm not sure about the end user experience: The kernel is an early adopter of FRTO and will be bitten by bugs of other TCP implementations like we've experienced. I guess most affected users just see stalled or slow connections and won't have the time or knowledge to debug this. A proper warning could help them and the kernel developers to get this issue solved as quickly as possible. We called the hotline of the ISP several times and they always claimed sending big mails with Outlook/Windows works, so it must be linux's fault. That view of things is totally biased, but it's something I want to make sure people can't get away with easily :-) So, if it's possible to detect broken middleware boxes without spending too much time on it, that would really be nice. Thomas -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
