From owner-freebsd-current Wed Dec 22 21: 8:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B34F915633 for ; Wed, 22 Dec 1999 21:08:42 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40330>; Thu, 23 Dec 1999 15:59:39 +1100 Content-return: prohibited Date: Thu, 23 Dec 1999 16:08:30 +1100 From: Peter Jeremy Subject: Re: Odd TCP glitches in new currents In-reply-to: <199912230412.UAA15384@apollo.backplane.com>; from dillon@apollo.backplane.com on Thu, Dec 23, 1999 at 03:12:53PM +1100 To: Matthew Dillon Cc: freebsd-current@freebsd.org Message-Id: <99Dec23.155939est.40330@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <199912230412.UAA15384@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-23 15:12:53 +1100, Matthew Dillon wrote: > In fact, while its > running in the background I am *still* getting TCP stutters and tcpdump > still shows one machine sending a packet that the other machine never > gets! I have no friggin clue as to why TCP packets fail when UDP packets > don't. If the problem shows up at 10baseX speeds, you could try setting up a 10base2 network comprising the two test machines and a third machine as a sniffer. The thinwire will allow an independent sniffer without introducing any other hardware (like hubs) that might affect the results. If you suspect a s/w problem, have the sniffer run different s/w (a commercial LAN analyser if you have one available, otherwise maybe something non-FreeBSD). This should allow you to identify whether it's a transmit or receive problem. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message