ping stucks/hangs on PCI 3com NIC sk0 interface but works on
builtin NIC
Faizan ul haq Muhammad
faizi62 at hotmail.com
Wed Feb 25 10:11:44 PST 2009
> From: lists at jnielsen.net
> To: freebsd-questions at freebsd.org
> Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
> Date: Wed, 25 Feb 2009 13:06:14 -0500
> CC: faizi62 at hotmail.com
>
> On Wednesday 25 February 2009 12:35:23 pm Faizan ul haq Muhammad wrote:
> > Hi
> > I have two PCI NICs and one builtin NIC on freebsd 7.0
> > ifconfig shows information somthing like:
> >
> > bge0: flags=8843<UP, broadcast, runing, simplex, multicast>metric 0 mtu
> > 1500 options=9b<RXCSUM,TXCSUM, VLAN_HWTAGGING. VLAN_HWCSUM>
> > ether 00:13:21:f8:7e:56
> > inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
> > media: Ethernet autoselect (none) status: no carrier
>
> This is NIC doesn't appear to be plugged in.
no it is not plugged into any other yet and if i plug it and ping it from an external machine, it works
>
> > sk0: flags=8843<UP, broadcast, runing, simplex, multicast>metric 0 mtu
> > 1500 options=b<RXCSUM,TXCSUM, VLAN_MTU>
> > ether 00:0a:5e:1a:69:25
> > inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
> > media: Ethernet autoselect (none) status: no carrier
>
> Neither is this one.
You are right, but it does not reply to ping even if i plug this to an external system with crossover cable and ping from that PC.
that is the difference in behaviour of both NICs
>
> > Note: bge0 is builtin NIC
> > sk0 is 3com PCI NIC
> >
> > now after configuration of IPV4 Addresses, when i verify the
> > configuration with ping
> >
> > if i ping bge0(ping 192.168.0.1) i get the response of success
> > but when i ping sk0 (ping 192.168.0.2) Ping gets stuck and gives no
> > response, neither it gives success or host unreachable or denied kinda
> > errors..
>
> Why do you want both interfaces to be configured on the same subnet?
that is not required as such, I am just preparing the setup to use this machine a bridge and configure dummynet on this machine.
I hope now you get it.
>
> > it just hangs over there.. and i can juz see one line of ping
> > not proceeding anyway. and if I terminate it via CTRL C then i get
> > statistics sumthing like 3 packets sent, 0 received and 100% loss...
>
> This is probably expected behavior. What does "netstat -rn" show? My guess
> is that the route for 192.168.0.0/24 is "link#1" aka bge0 and since it's
> not plugged in to anything that's as far as it gets.
exactly
btu it does not show any other interface in netstat printout with this -rn switch
and can you explain, how this is the expected behavior then..?
>
> > I am stuck and my brain does not work any more here..
> > Can anybody help me ...
>
> JN
>
Thanks for your early response
_________________________________________________________________
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