From owner-freebsd-current@FreeBSD.ORG  Tue Feb 17 10:59:20 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9809516A4D6
	for <freebsd-current@freebsd.org>;
	Tue, 17 Feb 2004 10:59:20 -0800 (PST)
Received: from arginine.spc.org (arginine.spc.org [195.206.69.236])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6BB5543D31
	for <freebsd-current@freebsd.org>;
	Tue, 17 Feb 2004 10:59:20 -0800 (PST)	(envelope-from bms@spc.org)
Received: from localhost (localhost [127.0.0.1])
	by arginine.spc.org (Postfix) with ESMTP
	id A7CB165439; Tue, 17 Feb 2004 18:59:19 +0000 (GMT)
Received: from arginine.spc.org ([127.0.0.1])
 by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id 34894-01-2; Tue, 17 Feb 2004 18:59:19 +0000 (GMT)
Received: from saboteur.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com
	[82.147.17.88])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by arginine.spc.org (Postfix) with ESMTP
	id 295CC65339; Tue, 17 Feb 2004 18:59:19 +0000 (GMT)
Received: by saboteur.dek.spc.org (Postfix, from userid 1001)
	id 643FEC9; Tue, 17 Feb 2004 18:59:18 +0000 (GMT)
Date: Tue, 17 Feb 2004 18:59:18 +0000
From: Bruce M Simpson <bms@spc.org>
To: Doug White <dwhite@gumbysoft.com>
Message-ID: <20040217185918.GB933@saboteur.dek.spc.org>
Mail-Followup-To: Doug White <dwhite@gumbysoft.com>,
	freebsd-current@freebsd.org
References: <20040215072046.GD22136@saboteur.dek.spc.org>
	<20040215072250.GE22136@saboteur.dek.spc.org>
	<20040217104801.V29882@carver.gumbysoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040217104801.V29882@carver.gumbysoft.com>
cc: freebsd-current@freebsd.org
Subject: Re: Unusual fxp behaviour with link0 flag
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2004 18:59:20 -0000

On Tue, Feb 17, 2004 at 10:52:26AM -0800, Doug White wrote:
> tcpdump shows the [|foo] when you're using the default snarflen and it
> thinks there's more data to look at. The default snarflen is 68.  But TCP
> stuff should have been ID'd as [|tcp] and not [|ip], so I suppose it had
> the intended effect :)

The fxp which did this is now reporting nothing but 'SCB Timeout'. I have
declared it dead and fallen back to the onboard vr0. This is my primary
build box, so I'm a bit miffed about it. I was indeed using -s 0...

BMS