Date: Thu, 26 Feb 2009 14:19:14 -0500 From: Steve Bertrand <steve@ibctech.ca> To: Faizan ul haq Muhammad <faizi62@hotmail.com> Cc: lists@jnielsen.net, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC Message-ID: <49A6EB32.6030006@ibctech.ca> In-Reply-To: <BLU149-W814A3309D674ADFC7242E5B6AD0@phx.gbl> References: <BLU149-W4690F7B871E6EB8BF6159B6AC0@phx.gbl> <200902251306.14765.lists@jnielsen.net> <BLU149-W748054287E4E4FA47DA500B6AC0@phx.gbl> <200902251515.47094.lists@jnielsen.net> <BLU149-W7768E70C67D57329B7E82EB6AD0@phx.gbl> <49A69E9C.2090807@ibctech.ca> <BLU149-W751827F7E010EAE528293DB6AD0@phx.gbl> <49A6E853.1030605@ibctech.ca> <BLU149-W814A3309D674ADFC7242E5B6AD0@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49A6EB32.6030006>