Date: Fri, 27 Feb 2009 14:41:34 +0000 From: Faizan ul haq Muhammad <faizi62@hotmail.com> To: <steve@ibctech.ca> Cc: 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-W237729D500D66C139A03F9B6AA0@phx.gbl> In-Reply-To: <49A7F3F8.9050102@ibctech.ca> References: <BLU149-W4690F7B871E6EB8BF6159B6AC0@phx.gbl> <200902251306.14765.lists@jnielsen.net> <BLU149-W748054287E4E4FA47DA500B6AC0@phx.gbl> <200902251515.47094.lists@jnielsen.net> <BLU149-W7768E70C67D57329B7E82EB6AD0@phx.gbl> <49A69E9C.2090807@ibctech.ca> <BLU149-W751827F7E010EAE528293DB6AD0@phx.gbl> <49A6E853.1030605@ibctech.ca> <BLU149-W814A3309D674ADFC7242E5B6AD0@phx.gbl> <49A6EB32.6030006@ibctech.ca> <BLU149-W607BFBA69E3AD052F36606B6AA0@phx.gbl> <49A7E98A.3040109@ibctech.ca> <BLU149-W16C3843CA85D396A0A20ABB6AA0@phx.gbl> <49A7F3F8.9050102@ibctech.ca>
index | next in thread | previous in thread | raw e-mail
> Date: Fri, 27 Feb 2009 09:08:56 -0500 > From: steve@ibctech.ca > To: faizi62@hotmail.com > CC: lists@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=8843<UP, BROADCAST, RUNNING, SIMPLEX, MULTICAST> metric 0 > > mtu 1500 > > ther 0e:04:7b:09:e7:b0 > > inet 192.168.0.1 network 0xffffff00 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 Address Size Name > > 1 7 0xc0400000 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-unsubscribe@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_022009home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BLU149-W237729D500D66C139A03F9B6AA0>