Date: Mon, 27 Dec 2004 19:30:41 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Doug Lee <dgl@dlee.org>, freebsd-questions@freebsd.org Subject: Re: Tcpdump says I'm getting incomplete packets; how to find the culprit? Message-ID: <20041228013041.GB44954@dan.emsphone.com> In-Reply-To: <20041228003030.GL900@kirk.dlee.org> References: <20041228003030.GL900@kirk.dlee.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041228013041.GB44954>