RE: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Date: Thu, 26 Feb 2009 14:19:14 -0500 From: st...@ibctech.ca To: faiz...@hotmail.com CC: li...@jnielsen.net; freebsd-questions@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___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Faizan ul haq Muhammad wrote: 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 ? Provide the output to ifconfig bridge0, and kldstat. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Date: Fri, 27 Feb 2009 08:24:26 -0500 From: st...@ibctech.ca To: faiz...@hotmail.com CC: li...@jnielsen.net; freebsd-questions@freebsd.org Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC Faizan ul haq Muhammad wrote: 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 ? Provide the output to ifconfig bridge0, and kldstat. ifconfig bridge0 bridge0: flags=8843UP, BROADCAST, RUNNING, SIMPLEX, MULTICAST metric 0 mtu 1500 ther 0e:04:7b:09:e7:b0 inet 192.168.0.1 network 0xff00 broadcast 192.168.0.255 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 kldstat: id REfs AddressSize Name 1 7 0xc040 9111ec kernel 2 1 0xc0d12000 6a32c acpi.ko 3. 1 0xc4628000 22000 lunux.ko ...One more thing: do i need to enable bridging through some SCTL command. somthing like sysctl net.link.ether.bridge.config=sk0:0, sk1:0 by the way this command generates this error: unknown oid net.link.ether.bridge.config Regards! Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ Access your email online and on the go with Windows Live Hotmail. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_AE_Access_022009___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Faizan ul haq Muhammad wrote: Provide the output to ifconfig bridge0, and kldstat. ifconfig bridge0 bridge0: flags=8843UP, BROADCAST, RUNNING, SIMPLEX, MULTICAST metric 0 mtu 1500 ther 0e:04:7b:09:e7:b0 inet 192.168.0.1 network 0xff00 broadcast 192.168.0.255 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 kldstat: id REfs AddressSize Name 1 7 0xc040 9111ec kernel 2 1 0xc0d12000 6a32c acpi.ko 3. 1 0xc4628000 22000 lunux.ko That is what I kind of thought... ...One more thing: do i need to enable bridging through some SCTL command. somthing like sysctl net.link.ether.bridge.config=sk0:0, sk1:0 by the way this command generates this error: unknown oid net.link.ether.bridge.config Put: if_bridge_load=YES in /boot/loader.conf. You can also load the module with: kldload if_bridge IIRC, your settings in rc.conf should be enough to configure the bridge, so if you choose to load dynamically while running, try a /etc/netstart to configure the bridge. If that doesn't work, a reboot should. If you can't get it to work, supply the same output I asked for above, and then I'll set up a quick lab here to test it. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Date: Fri, 27 Feb 2009 09:08:56 -0500 From: st...@ibctech.ca To: faiz...@hotmail.com CC: li...@jnielsen.net; freebsd-questions@freebsd.org Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC Faizan ul haq Muhammad wrote: Provide the output to ifconfig bridge0, and kldstat. ifconfig bridge0 bridge0: flags=8843UP, BROADCAST, RUNNING, SIMPLEX, MULTICAST metric 0 mtu 1500 ther 0e:04:7b:09:e7:b0 inet 192.168.0.1 network 0xff00 broadcast 192.168.0.255 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 kldstat: id REfs AddressSize Name 1 7 0xc040 9111ec kernel 2 1 0xc0d12000 6a32c acpi.ko 3. 1 0xc4628000 22000 lunux.ko That is what I kind of thought... ...One more thing: do i need to enable bridging through some SCTL command. somthing like sysctl net.link.ether.bridge.config=sk0:0, sk1:0 by the way this command generates this error: unknown oid net.link.ether.bridge.config Put: if_bridge_load=YES in /boot/loader.conf. You can also load the module with: kldload if_bridge this command gives the output: module if_bridge already exists.. ... failed to register... bla bla (I have device if_bridge in my kernel setting so that already exists) IIRC, your settings in rc.conf should be enough to configure the bridge, so if you choose to load dynamically while running, try a /etc/netstart to configure the bridge. If that doesn't work, a reboot should. If you can't get it to work, supply the same output I asked for above, THE out put is the same for the above said commands and then I'll set up a quick lab here to test it. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ Windows Live™: Discover 10 secrets about the new Windows Live. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!7540.entry?ocid=TXT_TAGLM_WL_t2_ugc_post_022009___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Thanks dude, it helped me. if i configure the NICs with IPs belonging to different subnets, 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, for now Thanks for your help .. Regards /Faizan From: li...@jnielsen.net To: faiz...@hotmail.com Date: Wed, 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 On Wednesday 25 February 2009 01:11:42 pm Faizan ul haq Muhammad wrote: From: li...@jnielsen.net 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=8843UP, broadcast, runing, simplex, multicastmetric 0 mtu 1500 options=9bRXCSUM,TXCSUM, VLAN_HWTAGGING. VLAN_HWCSUM ether 00:13:21:f8:7e:56 inet 192.168.0.1 netmask 0xff00 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 That's good. sk0: flags=8843UP, broadcast, runing, simplex, multicastmetric 0 mtu 1500 options=bRXCSUM,TXCSUM, VLAN_MTU ether 00:0a:5e:1a:69:25 inet 192.168.0.2 netmask 0xff00 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. Still not surprising. See below. 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. You might try a different configuration for your testing. I suspect if you changed the IP address of sk0 to 192.168.1.2 or similar it would behave as you are expecting. 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. 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..? There can only be one route at any time for any given network. When you bring up bge0 with 192.168.0.1 a route is automatically created for 192.168.0.0 pointing to that interface. When you then bring up sk0 with 192.168.0.2 no additional route can be added for 192.168.0.0 since there is already one present. Therefore ALL traffic destined for the 192.168.0.0 network will go out via bge0. In order to be able to ping 192.168.0.2 _locally_ you'd either need to connect the interfaces with a crossover cable (well, crossover isn't strictly necessary since gigabit ethernet adapters can figure it out on their own..) OR plug both interfaces into a switch/hub. Ping packet goes out bge0 (according to the route), across the wire and comes in on sk0 (destination address). The response would be delivered directly to bge0 (without going over the wire). Similarly, in order to be able to ping 192.168.0.2 from a second machine all _three_ interfaces would need to be connected to the same network segment (via a switch/hub, etc). Ping packet goes out from peer, across the wire and in on sk0 (destination address). Response goes out bge0 (according to route), across the other wire and back to the peer. I hope this helps you make sense of things. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ It’s the same Hotmail®. If by “same” you mean up to 70% faster. http://windowslive.com/online/hotmail?ocid
Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Faizan ul haq Muhammad wrote: 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. No. A router's responsibility is to route packets between DISSIMILAR network prefixes. In essence, trying to do what you want is similar to this: - you live at 100 John St - you need to go to 50 John St - the street is addressed in a way that a 50 John street is to your left AND to the right Which way do you go? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Date: Thu, 26 Feb 2009 08:52:28 -0500 From: st...@ibctech.ca To: faiz...@hotmail.com CC: li...@jnielsen.net; freebsd-questions@freebsd.org Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC Faizan ul haq Muhammad wrote: 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. No. A router's responsibility is to route packets between DISSIMILAR network prefixes. In essence, trying to do what you want is similar to this: - you live at 100 John St - you need to go to 50 John St - the street is addressed in a way that a 50 John street is to your left AND to the right Which way do you go? In this case I can take any of them Steve Anyways,- Today i got some time to play around and i tried to configure the machine as bridge. I added device if_bridge to kernel then i added the code to the rc.conf cloned_interfaces=bridge0 ifconfig_bridge0=addm sk0 addm sk1 up ifconfig_sk0=up ifconfig_sk1=up now, i dun have any network address assigned to any of the interface and connect the two lan cards to two other machines and try to ping those machines from each other. but no success. ... do you think, this is as expected..? (i think bridge does not need to have any IP address..) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ Windows Live™: Discover 10 secrets about the new Windows Live. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!7540.entry?ocid=TXT_TAGLM_WL_t2_ugc_post_022009___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Faizan ul haq Muhammad wrote: Which way do you go? In this case I can take any of them Perhaps you will freeze in your tracks indefinitely due to confusion. Or perhaps you will go around the entire block a few times before making a decision ;) Anyways,- Today i got some time to play around and i tried to configure the machine as bridge. I added device if_bridge to kernel then i added the code to the rc.conf cloned_interfaces=bridge0 ifconfig_bridge0=addm sk0 addm sk1 up ifconfig_sk0=up ifconfig_sk1=up now, i dun have any network address assigned to any of the interface and connect the two lan cards to two other machines and try to ping those machines from each other. but no success. Did the bridge interface actually come up? ... do you think, this is as expected..? (i think bridge does not need to have any IP address..) It depends. Are you doing any sort of firewalling? What is the IP addressing info on the two end hosts? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
Date: Thu, 26 Feb 2009 14:06:59 -0500 From: st...@ibctech.ca To: faiz...@hotmail.com CC: li...@jnielsen.net; freebsd-questions@freebsd.org Subject: Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC Faizan ul haq Muhammad wrote: Which way do you go? In this case I can take any of them Perhaps you will freeze in your tracks indefinitely due to confusion. Or perhaps you will go around the entire block a few times before making a decision ;) lol, i got confused when i first time saw ur previous reply ... that which way should i take. Anyways,- Today i got some time to play around and i tried to configure the machine as bridge. I added device if_bridge to kernel then i added the code to the rc.conf cloned_interfaces=bridge0 ifconfig_bridge0=addm sk0 addm sk1 up ifconfig_sk0=up ifconfig_sk1=up now, i dun have any network address assigned to any of the interface and connect the two lan cards to two other machines and try to ping those machines from each other. but no success. Did the bridge interface actually come up? I could see the bridge interface in the printout of Ifconfig and i assigned the IP address to the bridge interface and can ping to that IP as well (locally) ... do you think, this is as expected..? (i think bridge does not need to have any IP address..) 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 Steve _ Access your email online and on the go with Windows Live Hotmail. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_AE_Access_022009___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
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. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
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=8843UP, broadcast, runing, simplex, multicastmetric 0 mtu 1500 options=9bRXCSUM,TXCSUM, VLAN_HWTAGGING. VLAN_HWCSUM ether 00:13:21:f8:7e:56 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 media: Ethernet autoselect (none) status: no carrier This is NIC doesn't appear to be plugged in. sk0: flags=8843UP, broadcast, runing, simplex, multicastmetric 0 mtu 1500 options=bRXCSUM,TXCSUM, VLAN_MTU ether 00:0a:5e:1a:69:25 inet 192.168.0.2 netmask 0xff00 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
From: li...@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, 25 Feb 2009 13:06:14 -0500 CC: faiz...@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=8843UP, broadcast, runing, simplex, multicastmetric 0 mtu 1500 options=9bRXCSUM,TXCSUM, VLAN_HWTAGGING. VLAN_HWCSUM ether 00:13:21:f8:7e:56 inet 192.168.0.1 netmask 0xff00 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=8843UP, broadcast, runing, simplex, multicastmetric 0 mtu 1500 options=bRXCSUM,TXCSUM, VLAN_MTU ether 00:0a:5e:1a:69:25 inet 192.168.0.2 netmask 0xff00 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___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ping stucks/hangs on PCI 3com NIC sk0 interface but works on builtin NIC
On Wednesday 25 February 2009 01:11:42 pm Faizan ul haq Muhammad wrote: From: li...@jnielsen.net 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=8843UP, broadcast, runing, simplex, multicastmetric 0 mtu 1500 options=9bRXCSUM,TXCSUM, VLAN_HWTAGGING. VLAN_HWCSUM ether 00:13:21:f8:7e:56 inet 192.168.0.1 netmask 0xff00 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 That's good. sk0: flags=8843UP, broadcast, runing, simplex, multicastmetric 0 mtu 1500 options=bRXCSUM,TXCSUM, VLAN_MTU ether 00:0a:5e:1a:69:25 inet 192.168.0.2 netmask 0xff00 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. Still not surprising. See below. 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. You might try a different configuration for your testing. I suspect if you changed the IP address of sk0 to 192.168.1.2 or similar it would behave as you are expecting. 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. 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..? There can only be one route at any time for any given network. When you bring up bge0 with 192.168.0.1 a route is automatically created for 192.168.0.0 pointing to that interface. When you then bring up sk0 with 192.168.0.2 no additional route can be added for 192.168.0.0 since there is already one present. Therefore ALL traffic destined for the 192.168.0.0 network will go out via bge0. In order to be able to ping 192.168.0.2 _locally_ you'd either need to connect the interfaces with a crossover cable (well, crossover isn't strictly necessary since gigabit ethernet adapters can figure it out on their own..) OR plug both interfaces into a switch/hub. Ping packet goes out bge0 (according to the route), across the wire and comes in on sk0 (destination address). The response would be delivered directly to bge0 (without going over the wire). Similarly, in order to be able to ping 192.168.0.2 from a second machine all _three_ interfaces would need to be connected to the same network segment (via a switch/hub, etc). Ping packet goes out from peer, across the wire and in on sk0 (destination address). Response goes out bge0 (according to route), across the other wire and back to the peer. I hope this helps you make sense of things. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
