Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Feb 2009 18:11:42 +0000
From:      Faizan ul haq Muhammad <faizi62@hotmail.com>
To:        <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:  <BLU149-W748054287E4E4FA47DA500B6AC0@phx.gbl>
In-Reply-To: <200902251306.14765.lists@jnielsen.net>
References:  <BLU149-W4690F7B871E6EB8BF6159B6AC0@phx.gbl> <200902251306.14765.lists@jnielsen.net>

next in thread | previous in thread | raw e-mail | index | archive | help

=20


> From: lists@jnielsen.net
> To: freebsd-questions@freebsd.org
> Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on=
 builtin NIC
> Date: Wed=2C 25 Feb 2009 13:06:14 -0500
> CC: faizi62@hotmail.com
>=20
> 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=3D8843<UP=2C broadcast=2C runing=2C simplex=2C multicast>me=
tric 0 mtu
> > 1500 options=3D9b<RXCSUM=2CTXCSUM=2C 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
>=20
> 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 a=
n external machine=2C it works
>=20
> > sk0: flags=3D8843<UP=2C broadcast=2C runing=2C simplex=2C multicast>met=
ric 0 mtu
> > 1500 options=3Db<RXCSUM=2CTXCSUM=2C 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
>=20
> Neither is this one.

You are right=2C but it does not reply to ping even if i plug this to an ex=
ternal system with crossover cable and ping from that PC.

that is the difference in behaviour of both NICs
>=20
> > Note: bge0 is builtin NIC
> > sk0 is 3com PCI NIC
> >
> > now after configuration of IPV4 Addresses=2C 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=2C neither it gives success or host unreachable or denied kind=
a
> > errors..
>=20
> Why do you want both interfaces to be configured on the same subnet?

that is not required as such=2C I am just preparing the setup to use this m=
achine a bridge and configure dummynet on this machine.

I hope now you get it.
>=20
> > it just hangs over there.. and i can juz see one line of ping=20
> > not proceeding anyway. and if I terminate it via CTRL C then i get
> > statistics sumthing like 3 packets sent=2C 0 received and 100% loss...
>=20
> This is probably expected behavior. What does "netstat -rn" show? My gues=
s=20
> is that the route for 192.168.0.0/24 is "link#1" aka bge0 and since it's=
=20
> 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=2C how this is the expected behavior then..?


>=20
> > I am stuck and my brain does not work any more here..
> > Can anybody help me ...
>=20
> JN
>=20
Thanks for your early response

_________________________________________________________________
Windows Live=99 Hotmail=AE:=85more than just e-mail.=20
http://windowslive.com/explore?ocid=3DTXT_TAGLM_WL_t2_hm_justgotbetter_expl=
ore_022009=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BLU149-W748054287E4E4FA47DA500B6AC0>