From owner-freebsd-current@FreeBSD.ORG  Fri Oct 31 13:24:57 2003
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 4A47216A4CE
	for <current@freebsd.org>; Fri, 31 Oct 2003 13:24:57 -0800 (PST)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7ADE043F93
	for <current@freebsd.org>; Fri, 31 Oct 2003 13:24:56 -0800 (PST)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id h9VLOt1G026139;
	Fri, 31 Oct 2003 16:24:55 -0500 (EST)
Date: Fri, 31 Oct 2003 16:24:55 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Lars Eggert <larse@ISI.EDU>
In-Reply-To: <3FA1EF1A.7070000@isi.edu>
Message-ID: <Pine.GSO.4.10.10310311620480.25100-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: wi problem with message > 7400 bytes
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: Fri, 31 Oct 2003 21:24:57 -0000

On Thu, 30 Oct 2003, Lars Eggert wrote:

> Daniel Eischen wrote:
> >>
> >>Could you post a tcpdump for each case? I wonder if this is related to a 
> >>fragmentation issue I've seen in the past.
> > 
> > 22:46:43.513038 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52198:1480@0+)
> > 22:46:48.522475 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52199:1480@0+)
> > 22:46:53.532018 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52200:1480@0+)
> > 22:46:58.541178 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52201:1480@0+)
> > 22:47:03.553048 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52202:1480@0+)
> > 22:47:08.568862 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52203:1480@0+)
> > 22:47:13.583328 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52204:1480@0+)
> > 22:47:18.578512 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52205:1480@0+)
> > 22:47:23.609098 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52206:1480@0+)
> > 22:47:28.597680 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52207:1480@0+)
> > 22:47:33.607059 gpz.foo.bar.com.38340 > vespa.12345: udp 7393 (frag 52208:1480@0+)
> 
> It's not what I've seen in the past - but also pretty strange! Only the
> first fragment seems to be received. Wonder what happened to the other
> fragments...

I guess the problem was with the access point.  Once I
swapped it with a Linksys WAP-11, it worked.

For future reference, the bad access point was a Dell
TrueMobile-branded Intel 1170 Wireless Base Station
(Model WLGW2011).

-- 
Dan Eischen