On Thu, 10 Jul 2008 12:51:30 +0200 Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx> wrote: > We found a workaround by putting a linux-based AVM fritz!box router between > kernel 2.6.25.10 and the mailserver, now the TCP connection works again, > though it gets NATed. Still can't make any sense out of this. I have the same problem with connections stalled and the only "workaround" I found is to trigger a nmap -sS to the server with the stalled connection. I don't know why, but this helps it come back alive again... But it surely is a Linux network bug introduced in 2.6.25 kernel, I'm sure (with 2.6.24 and below it doesn't happen, or maybe we're talking about different symptoms of the same bug or 2 different similar bugs... who knows?). I use the tg3 kernel module for the NIC... the same configuration of the kernel doesn't trigger the bug with other types of nics... so could we suspect of tg3 kernel module? What's your NIC? -- Linux 2.6.25: Funky Weasel is Jiggy wit it http://u-br.net Marilyn Manson - "Wrapped in Plastic" (Portrait of an American Family - 1994) -- 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
