Date: Fri, 18 Feb 2000 11:33:53 -0800 (PST) From: Jorge Aldana <jorge@salk.edu> To: "Jeffrey J. Mountin" <jeff-ml@mountin.net> Cc: stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) Message-ID: <Pine.BSF.3.96.1000218111714.41957D-100000@phelps.salk.edu> In-Reply-To: <3.0.3.32.20000218125024.009efd00@207.227.119.2>
next in thread | previous in thread | raw e-mail | index | archive | help
We upgraded to a newer Xylan Omni Switch/Router basically for more ports from an older Xylan (same model) with less ports. On the older Xylan we had to force the Media to 100baseTX otherwise the intel's would drop to 10base on reboots. With the new switch the Intel cards would have trouble with full duplex, drop to half or not be able to negotiate with the Xylan. Under the worst circumstances the Cards would emit runt packets causing the whole network to go down (a switch thing) thats why we got rid of them. Note: everything was fine with the old Xylan and Intel cards, the new Xylan (only newer technology from what we know) did work with Intels but not the way we needed them full duplex 100BT. We noticed that the 3Coms that were built into some of the machines which were using the Intel pci card did everything without a hitch so we pulled the cards and went with the built in 3Com's. Everything is fine now and like I said, I don't care who makes it just that it works. I'm sure we could of tweeked something somewhere (switch or ifconfig) to get things to work right but that would of been extra time, something I didn't have or want to use on that problem. Jorge On Fri, 18 Feb 2000, Jeffrey J. Mountin wrote: > At 11:08 PM 2/17/00 -0800, Jorge Aldana wrote: > >Before you go out and buy any card make sure the network you're plugging > >it into is going to work with it. Huh, you say. Well we had all Intel > >Pro/100's working just fine (although we had to muck with ifconfig as > >follows for 100BT ifconfig_fxp0="inet xx.xx.xx.xx netmask > >255.255.255.0 media 100baseTX), then we bought a new switch and the Intel > >cards went bonkers and caused several problems. Needless to say when we > >switch to 3Com all was fine, now we burn those Intel's. Not that Intel > >makes a bad card or 3Com is better, they just happen to work so 3Com it > is. So > >don't just look at the card, the network you're plugging it in to matters > >as well, switch, hub, bla bla bla... > > What switch? And why set the media? "Bonkers" is a bit vague. > > The Intel autosenses speed/duplex well with Intel, 3Com, and Cisco switches > from my dealings with and does so with FBSD or Win 9x/NT. Can't say the > same about 3Com 9xx (old and new). YMMV > > > > > Jeff Mountin - jeff@mountin.net > Systems/Network Administrator > FreeBSD - the power to serve > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.1000218111714.41957D-100000>