ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC

Faizan ul haq Muhammad faizi62 at hotmail.com
Fri Feb 27 01:34:08 PST 2009






> Date: Thu, 26 Feb 2009 14:19:14 -0500
> From: steve at ibctech.ca
> To: faizi62 at hotmail.com
> CC: lists at jnielsen.net; freebsd-questions at freebsd.org
> Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
> 
> 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.
>
I have just checked this:
it says nothing ... except:
------------listening on bridge0, link-type EN10MB (Ethernet), capture size 96 bytes
I think it is unable to receive any packet . DO i miss something in the configuration ?
> Steve

_________________________________________________________________
Windows Live™ Hotmail®:…more than just e-mail. 
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t2_hm_justgotbetter_explore_022009


More information about the freebsd-questions mailing list