On Mon, Apr 24, 2006 at 01:56:09AM +0200, Florian Zumbiehl wrote: > > Well, at least the tcp part of it, it seems, yep. The debugging I've > done so far also seems to confirm that the problem is somewhere beyond > the tcp code, but I don't have any real clue yet ...
One way to proceed is to add printk's to the error paths in the output path through TCP, IPv6, netfilter, ... These should be rare so the it shouldn't flood your syslog. Based on which error path is taken or not taken you should be able to work out where you need to focus your search on. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
