Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 12 Aug 2002 06:05:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 12 Aug 2002 06:05:09 -0400 Received: from pizda.ninka.net ([216.101.162.242]:23963 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Mon, 12 Aug 2002 06:05:08 -0400 Date: Mon, 12 Aug 2002 02:54:53 -0700 (PDT) Message-Id: <20020812.025453.114975744.davem@redhat.com> To: mroos@linux.ee Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org Subject: Re: Linux TCP problem while talking to hostme.bkbits.net ? From: "David S. Miller" In-Reply-To: References: <200208112125.BAA16174@sex.inr.ac.ru> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1042 Lines: 27 From: Meelis Roos Date: Mon, 12 Aug 2002 10:28:10 +0300 (EEST) Before and after the connetion attempt - looks like the number of bad segments is increasing so probably not a TCP bug. Since I can connect to this server fine from different locations, it looks like something (ISP caches/shapers? cable modem?) is corrupting specific packets in a reproducible way. Aparently something is wrong with the checksums. InErrs gets incremented in three cases: 1) Header too small, unlikely what you see 2) Bad SYN sequences, Abort On Syn in TcpExt would have been incremented also if this were the case, it was not 3) Bad TCP checksum Hmmm, do you have messages that say "hw tcp v4 csum failed" in your kernel logs? Any other interesting kernel messages? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/