Date: Fri, 28 May 1999 23:38:38 -0400 From: Brandon Fosdick <bfoz@glue.umd.edu> To: freebsd-questions@FreeBSD.ORG Subject: Re: Crossover Ethernet Message-ID: <374F613E.5BDFA667@glue.umd.edu> References: <374E0508.C82BDA02@glue.umd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brandon Fosdick wrote: > > I've been trying for two days now to get two 3.2-S boxes talking to each other > with a crossover cable. After searching the archives it sounds like its an easy > thing to do, for everybody else at least. > > Here's what I've been using. > Computer A: > P120, Intel EtherExpress 10/100 > ifconfig fxp0 inet 10.0.0.2 netmask 0xfffffffc > route add 10.0.0.3 10.0.0.2 > > Computer B: > P200, 3Com 3c509 > ifconfig ep0 inet 10.0.0.3 netmask 0xfffffffc > route add 10.0.0.2 10.0.0.3 > > after doing the above, then type ifconfig fxp0, get "status: no carrier". > Thought that was the problem, so replaced fpx0 board with NE2000T (ed0) same > configuration but get "device timeout" for every attempted access to the board. > man pages says that error is the result of an irq conflict, so I set ed0's irq > to 8. Same problem. Back to fxp0 board since it worked on the campus LAN (10 > MBps) just a few days ago... What do I do about the "no carrier" message? > > Do I have two bad NIC's or am I doing something wrong? > > Thanks, > Brandon Turns out it was just a bad crossover cable. Nothing a little minor surgery couldn't fix. Thanks for the help. -Brandon -- bfoz@glue.umd.edu "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?374F613E.5BDFA667>