From owner-freebsd-questions@FreeBSD.ORG Tue Dec 28 01:30:51 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C79116A4CE for ; Tue, 28 Dec 2004 01:30:51 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5A4743D48 for ; Tue, 28 Dec 2004 01:30:50 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iBS1UfAv003643; Mon, 27 Dec 2004 19:30:41 -0600 (CST) (envelope-from dan) Date: Mon, 27 Dec 2004 19:30:41 -0600 From: Dan Nelson To: Doug Lee , freebsd-questions@freebsd.org Message-ID: <20041228013041.GB44954@dan.emsphone.com> References: <20041228003030.GL900@kirk.dlee.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041228003030.GL900@kirk.dlee.org> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i Subject: Re: Tcpdump says I'm getting incomplete packets; how to find the culprit? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 01:30:51 -0000 In the last episode (Dec 27), Doug Lee said: > I use FreeBSD 4.10-STABLE as a nat/firewall box. When connected to > DSL, I got fast web surfing but many gaps in incoming audio traffic > using some audio software. I switched to cable, and now audio works > great, but at least when I pop open pages in Lynx right on the > FreeBSD box, I often experience five-second delays--one at "202 OK" > and one or more during the loading of the page. Tcpdump reports that > I'm receiving incomplete packets, so I assume the five-second delays > are timeouts on my box before a request for packet resends. What is tcpdump printing that makes you think that packets are incomplete? If you are manually decoding packets by looking at tcpdump -X output, make sure you also use -s 0 to grab the entire packet. > Please Cc me on replies (I hope this is not rude to ask; I'm just > afraid of missing answers). That's the standard on these lists. -- Dan Nelson dnelson@allantgroup.com