BTW, firestarter doesn't seem to help here. I suspect that if it appears to work for anyone, it's probably coincidental. Please feel free to correct me if I'm wrong.
What's confusing about this bug is that it certainly appears to be in the TCP stack somewhere, but it obviously isn't affecting a lot of people or there would be more reports. It's not limited to a particular driver, though, because I see it with both my wired and wireless connections.
This is a real show-stopper for me, though. TCP becomes totally unreliable.
BTW, firestarter doesn't seem to help here. I suspect that if it appears to work for anyone, it's probably coincidental. Please feel free to correct me if I'm wrong.
What's confusing about this bug is that it certainly appears to be in the TCP stack somewhere, but it obviously isn't affecting a lot of people or there would be more reports. It's not limited to a particular driver, though, because I see it with both my wired and wireless connections.
This is a real show-stopper for me, though. TCP becomes totally unreliable.