That's quite an impressive test you did.
I'm not sure I understand all specifics, but as far as I see it, you managed to avoid their attack by just telling your router to reject it.
If I understand it correctly, this also means, that the utilized TCP implementation of the program is the target.
Does the TCP management happen at the OS level, or at the program level?
If it is at the program level, it might be possible to add some code which detects excess levels of reset packets in the pipe and just ignores them. Maybe that's what LimeWire already does... |