Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 19 Mar 2002 15:17:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 19 Mar 2002 15:17:18 -0500 Received: from chaos.analogic.com ([204.178.40.224]:40833 "EHLO chaos.analogic.com") by vger.kernel.org with ESMTP id ; Tue, 19 Mar 2002 15:17:00 -0500 Date: Tue, 19 Mar 2002 15:19:55 -0500 (EST) From: "Richard B. Johnson" Reply-To: root@chaos.analogic.com To: Andreas Dilger cc: John Jasen , Mike Galbraith , Denis Vlasenko , linux-kernel Subject: Re: reading your email via tcpdump In-Reply-To: <20020319154734.GM470@turbolinux.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 19 Mar 2002, Andreas Dilger wrote: > On Mar 19, 2002 10:11 -0800, Mike Fedyk wrote: > > That's not the problem part of the tcpdump output. The problem is that part > > of an email previously read on the linux box (with no samba runing. (also, > > no smbfs MikeG?)) showed up in the tcpdump output... > The data sent/received on the network is precious. You will not have any 'extra' data on its end except for possibly a single byte if the data didn't have an even length. Note that these things are checksummed and also CRCed in the hardware. If you got part of somebody's email, I think you should look at the `tcpdump` source. It may be the culprit... Cheers, Dick Johnson Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips). Windows-2000/Professional isn't. - 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/