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

[John Nielsen]

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.

> 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.

> 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?

> 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.

> I am stuck and my brain does not work any more here..
> Can anybody help me ...

JN