From owner-freebsd-questions@FreeBSD.ORG Tue Feb 13 20:34:23 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7250116A402 for ; Tue, 13 Feb 2007 20:34:23 +0000 (UTC) (envelope-from nalists@scls.lib.wi.us) Received: from mail.scls.lib.wi.us (mail.scls.lib.wi.us [198.150.40.25]) by mx1.freebsd.org (Postfix) with ESMTP id 47D5E13C471 for ; Tue, 13 Feb 2007 20:34:23 +0000 (UTC) (envelope-from nalists@scls.lib.wi.us) Received: from [10.1.99.103] ([10.1.99.103]) by mail.scls.lib.wi.us (8.13.8/8.13.1) with ESMTP id l1DK3bCf080913; Tue, 13 Feb 2007 14:03:37 -0600 (CST) (envelope-from nalists@scls.lib.wi.us) Message-ID: <45D2198B.9020104@scls.lib.wi.us> Date: Tue, 13 Feb 2007 14:03:23 -0600 From: Greg Barniskis User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Matthew Pope References: <45CF9010.7040905@teksavvy.com> <448xf3hw0f.fsf@be-well.ilk.org> <45D20B9C.8080602@teksavvy.com> In-Reply-To: <45D20B9C.8080602@teksavvy.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Connection timed out X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2007 20:34:23 -0000 Matthew Pope wrote: > I find that during the blocking behaviour, when I try and ping the > windows box, a tcpdump shows that each second ping attempt is followed > by a response (it appears) from an IPv6 address... > 13:30:51.066625 802.1d config 8000.00:30:19:53:05:00.8011 root > 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 > 13:30:53.069431 802.1d config 8000.00:30:19:53:05:00.8011 root > 8000.00:30:19:53:05:00 pathcost 0 age 0 max 20 hello 2 fdelay 15 If you're referring to the above samples as "appears from IPV6", those are Spanning Tree Protocol packets originating from the Cisco switch, and are unrelated to your ping test. You will see them on the wire frequently even in the absence of any normal IP traffic. You probably want the following Cisco configuration directive added to those switch ports that do not connect the 2900 to other switches: spanning-tree portfast The presence of the STP packets may or may not be related to your performance issues. They shouldn't be, but some buggy NICs/drivers do seem to get freaked out by STP. When STP is enabled on a switch port, it definitely will delay your initial link establishment by 30 seconds or so, when the attached computer is first powered up. That alone can confuse things when the NIC is trying to negotiate a link speed and the switch is still thinking about STP. It's even possible that you're getting a link speed/duplex mismatch out of it, and of course that will play holy hell with your response time. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348