From owner-freebsd-questions Sat Dec 12 14:06:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02836 for freebsd-questions-outgoing; Sat, 12 Dec 1998 14:06:06 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from hyperhost.net (ether.lightrealm.com [207.159.132.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02831 for ; Sat, 12 Dec 1998 14:06:05 -0800 (PST) (envelope-from patseal@hyperhost.net) Received: from port7.annex4.radix.net (port7.annex4.radix.net [209.48.225.135]) by hyperhost.net (8.8.5/8.8.5) with ESMTP id QAA02306; Sat, 12 Dec 1998 16:40:35 -0500 (EST) Date: Sat, 12 Dec 1998 16:40:09 -0500 (EST) From: Patrick Seal To: ken keeler cc: Steve Friedrich , "freebsd-questions@FreeBSD.ORG" Subject: Re: cannot connect on LAN In-Reply-To: <3672DD2C.DE0D1147@nwlink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually you will need a crossover cable, Unless you are using a hub or something. The problem is that they are both using the same 2(or more) paths for trasmitting and receiving. A crossover switches them around. Normal comp 1 S --------------------------------- S comp 2 R --------------------------------- R Crossover comp 1 S -----------\ /----------------- S comp 2 \/ /\ R -----------/ \----------------- R See the difference? With a normal cable its like holding a phone upside-down. _____________________________ Patrick Seal Hyperhost hosting and Design http://www.hyperhost.net On Sat, 12 Dec 1998, ken keeler wrote: > Steve Friedrich wrote: > > > > On Sat, 12 Dec 1998 11:01:43 -0800, ken keeler wrote: > > > > >fxp0: flags=8843 mtu 1500 > > > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > > > ether 00:a0:c9:90:78:09 > > > media: autoselect > > > > Someone else may give you an authoritive answer, but I've noticed on > > this list that some of the ethernet drivers and/or cards don't > > autoselect properly. You should have a diskette that came with the > > card that allows you to change the board's config. Set the "port" > > manually, i.e., one of aui/utp/bnc. And then use the appropriate > > ifconfig media option in /etc/rc.conf. See man fxp for that. > > > Actually I don't have any disks for any of these cards. The cards came > from running machines that had been upgraded, and thus no disks were > available. For the fxp0 device, I plugged it in to see what would > happen, and that was how it was probed. I just read man fxp, and it says > it's based on Intel i82557 ethernet chip. The number on the chip in the > card is S82557. Is this the same? There is an i on the chip, but not > part of that number. The card appears to be something other than Intel. > > I'm going attempt to locate some more info on this card. > > > For the ed0 device, it has numbers on the back 8013EWC, which seemed to > be just fine for ed0. It is jumper configurable. I made an assumption > that all SMC 8013 cards will work with the ed0 device, but perhaps that > was an error on my part? > -- > > E=m*(c*c) > Ken Keeler > "Look, it's all a bunch of ones and zeros." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message