From owner-freebsd-questions@FreeBSD.ORG Thu Feb 26 19:19:25 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCAFB106566B for ; Thu, 26 Feb 2009 19:19:25 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 5641C8FC16 for ; Thu, 26 Feb 2009 19:19:25 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 32126 invoked by uid 89); 26 Feb 2009 19:21:58 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by v6.ibctech.ca with ESMTPA; 26 Feb 2009 19:21:58 -0000 Message-ID: <49A6EB32.6030006@ibctech.ca> Date: Thu, 26 Feb 2009 14:19:14 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Faizan ul haq Muhammad References: <200902251306.14765.lists@jnielsen.net> <200902251515.47094.lists@jnielsen.net> <49A69E9C.2090807@ibctech.ca> <49A6E853.1030605@ibctech.ca> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: lists@jnielsen.net, FreeBSD Questions Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC 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: Thu, 26 Feb 2009 19:19:26 -0000 Faizan ul haq Muhammad wrote: >> It depends. Are you doing any sort of firewalling? What is the IP >> addressing info on the two end hosts? > well, in this configuration i havent enabled any firewalling. > the Ips are: 192.168.0.4 and 192.168.0.5 for the other two hosts and to > the bridge i assigned IP 192.168.0.1 Ok. On the box with the bridge, su to root and start a tcpdump session: # tcpdump -n -i bridge0 ...and then, on 192.168.0.4, ping 192.168.0.5 After the ping is done (whether it works or not), stop the tcpdump and email the output to the list if you can. If you can't email it, at least type out the IP addresses captured, and the direction the data is attempting to flow eg: 208.70.104.210.22 > 208.70.104.100.50885 208.70.104.100.50885 > 208.70.104.210.22 arp who-has 208.70.104.206 tell 208.70.104.193 etc. Steve