Date: Thu, 26 Feb 2009 13:30:34 +0000 From: Faizan ul haq Muhammad <faizi62@hotmail.com> To: <lists@jnielsen.net> Cc: 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-W7768E70C67D57329B7E82EB6AD0@phx.gbl> In-Reply-To: <200902251515.47094.lists@jnielsen.net> References: <BLU149-W4690F7B871E6EB8BF6159B6AC0@phx.gbl> <200902251306.14765.lists@jnielsen.net> <BLU149-W748054287E4E4FA47DA500B6AC0@phx.gbl> <200902251515.47094.lists@jnielsen.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks dude=2C it helped me. if i configure the NICs with IPs belonging to = different subnets=2C I get ping working locally. I can see multiple routes for different subnets in NETSTAT too. Now i assume that in order to configure the NICs with the same NETWORK and = make them working i need to configure the System as router. Anyways=2C for now Thanks for your help ..=20 Regards /Faizan > From: lists@jnielsen.net > To: faizi62@hotmail.com > Date: Wed=2C 25 Feb 2009 15:15:46 -0500 > CC: freebsd-questions@freebsd.org > Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on= builtin NIC >=20 > On Wednesday 25 February 2009 01:11:42 pm Faizan ul haq Muhammad wrote: > > > From: lists@jnielsen.net > > > On Wednesday 25 February 2009 12:35:23 pm Faizan ul haq Muhammad=20 > 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 multicas= t>metric 0 > > > > mtu 1500 options=3D9b<RXCSUM=2CTXCSUM=2C VLAN_HWTAGGING. VLAN_HWCSU= M> > > > > 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=2C it works >=20 > That's good. >=20 > > > > sk0: flags=3D8843<UP=2C broadcast=2C runing=2C simplex=2C multicast= >metric 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 > > > > > > Neither is this one. > > > > You are right=2C but it does not reply to ping even if i plug this to a= n > > external system with crossover cable and ping from that PC. >=20 > Still not surprising. See below. >=20 > > 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=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 > > > > kinda errors.. > > > > > > 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 th= is > > machine a bridge and configure dummynet on this machine. >=20 > You might try a different configuration for your testing. I suspect if yo= u=20 > changed the IP address of sk0 to 192.168.1.2 or similar it would behave=20 > as you are expecting. >=20 > > > > 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=2C 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. > > > > 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 > There can only be one route at any time for any given network. When you=20 > bring up bge0 with 192.168.0.1 a route is automatically created for=20 > 192.168.0.0 pointing to that interface. When you then bring up sk0 with=20 > 192.168.0.2 no additional route can be added for 192.168.0.0 since there= =20 > is already one present. Therefore ALL traffic destined for the=20 > 192.168.0.0 network will go out via bge0. >=20 > In order to be able to ping 192.168.0.2 _locally_ you'd either need to=20 > connect the interfaces with a crossover cable (well=2C crossover isn't=20 > strictly necessary since gigabit ethernet adapters can figure it out on=20 > their own..) OR plug both interfaces into a switch/hub. Ping packet goes= =20 > out bge0 (according to the route)=2C across the wire and comes in on sk0= =20 > (destination address). The response would be delivered directly to bge0=20 > (without going over the wire). >=20 > Similarly=2C in order to be able to ping 192.168.0.2 from a second machin= e=20 > all _three_ interfaces would need to be connected to the same network=20 > segment (via a switch/hub=2C etc). Ping packet goes out from peer=2C acro= ss=20 > the wire and in on sk0 (destination address). Response goes out bge0=20 > (according to route)=2C across the other wire and back to the peer. >=20 > I hope this helps you make sense of things. >=20 > JN >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe=2C send any mail to "freebsd-questions-unsubscribe@freebsd= .org" _________________________________________________________________ It=92s the same Hotmail=AE. If by =93same=94 you mean up to 70% faster.=20 http://windowslive.com/online/hotmail?ocid=3DTXT_TAGLM_WL_HM_AE_Same_022009=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BLU149-W7768E70C67D57329B7E82EB6AD0>