From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23335 invoked from network); 8 Dec 2004 10:08:28 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 8 Dec 2004 10:08:28 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1CbykF-0001oU-R9 for arch-gentoo-user@lists.gentoo.org; Wed, 08 Dec 2004 10:08:27 +0000 Received: (qmail 19164 invoked by uid 89); 8 Dec 2004 10:08:10 +0000 Mailing-List: contact gentoo-user-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-user@lists.gentoo.org X-BeenThere: gentoo-user@gentoo.org Received: (qmail 23587 invoked from network); 8 Dec 2004 10:08:10 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=WmDSgbknPUxOQ7/3AsMLho94Sz58sKC+lcL3tpxnbEL5pZWVe1malGBDluQriCtZVjokiEGQJvgB3N/5Uemvv35xaTmfFMxrmWcEo14uHfSmSeyesBJtyBoABwC5eGbRFYcL4Uou9x/kPr1wutx3lKZsFl2jHfe/2nC3eRRznGA= Message-ID: <2ab8d39a0412080208641746b2@mail.gmail.com> Date: Wed, 8 Dec 2004 11:08:09 +0100 From: krzaq Reply-To: krzaq To: gentoo-user@lists.gentoo.org In-Reply-To: <41B6D003.4060806@pbp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <2ab8d39a04120801436357c3b@mail.gmail.com> <41B6D003.4060806@pbp.net> Subject: Re: [gentoo-user] packets with bad cheksum X-Archives-Salt: ac3eeeb6-d844-4070-8c3b-0aac78e69cb1 X-Archives-Hash: 8d96a0318c221b3eeced7199bfe3ef62 On Wed, 08 Dec 2004 01:57:23 -0800, Jonathan Nichols wrote: > > > When I run iptraf I see that > > approx. 30% of all packets are classified as BadIP (bad checksum in > > header right?). > > That concerns all intefraces (WAN, home LAN and even LO!!!!). > > Reboot helps but the problem returns shortly. > > > > Start looking at the physical layer - replace a cable, see if it helps. > Sounds like you've already done a lot of software troubleshooting to no > avail. Could a faulty cable/switch cause such havock on all interfaces (lo in particular)? I am no expert and I have no idea where to start looking. The problem seems to be with hardware but not with memory (CPU? , motherboard?). -- Regards Karol Krzak -- gentoo-user@gentoo.org mailing list