Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 May 1999 00:09:21 -0700 (PDT)
From:      Annelise Anderson <andrsn@andrsn.stanford.edu>
To:        Brandon Fosdick <bfoz@glue.umd.edu>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Crossover Ethernet
Message-ID:  <Pine.BSF.3.96.990527235602.22248A-100000@andrsn.stanford.edu>
In-Reply-To: <374E0508.C82BDA02@glue.umd.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
First, after each machine is booted, you should check dmesg
to determine that the card was found and assigned a driver.

My 3-com card looks like this in dmesg:

1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 10 on isa
ep0: aui/utp/bnc[*BNC*] address 00:20:af:be:eb:e0

And the green light should be on.

After that, you can
ifconfig ep0 inet 10.10.10.3 netmask 0xffffff00
And similarly for the other box.
You can look at ifconfig -a to see all the interfaces,
and ifconfig -au to see what is up and running.

A ping from one box to the other should then work, and the
routes should be established.  netstat -rn should show
the MAC address of the card in the other box.  

Sounds to me like the failure is in finding the cards and
assigning drivers in the first place (getting the irq and
address right for each one).

If you have a dos program or if either gets running on
Windows, you can look and see what resources it's using.

Annelise
 
On Thu, 27 May 1999, 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
> -- 
> 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
> 



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?Pine.BSF.3.96.990527235602.22248A-100000>