On Mon, 8 Oct 2007, Jozsef Kadlecsik wrote:
On Mon, 8 Oct 2007, Krzysztof Oledzki wrote:
It seems to me conntack is just right.
So? This bug is in Linux IP stack, as it should not reopen this port or reopen
using a different SEQ, right? It seems I should go to a different ML. :|
What is the exact kernel version of this machine?
It is 2.6.22.6 exactly. AFAIK there is a new "tcp source port
randomization" code included in 2.6.21 or 2.6.22. Maybe it is somehow
related? Or maybe it only make the problem easier to trigger?
Do you have got any kernel patches which might touch the IP stack
installed?
No, I hope. ;)
Best regards,
Krzysztof Olędzki
