From owner-freebsd-questions Mon Jun 22 07:54:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13147 for freebsd-questions-outgoing; Mon, 22 Jun 1998 07:54:03 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from smtp.interlog.com (root@smtp.interlog.com [207.34.202.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13108 for ; Mon, 22 Jun 1998 07:53:48 -0700 (PDT) (envelope-from paulg@interlog.com) Received: from shell1.interlog.com (paulg@shell1.interlog.com [207.34.202.8]) by smtp.interlog.com (8.8.8/8.8.5) with SMTP id KAA22367 for ; Mon, 22 Jun 1998 10:53:49 -0400 (EDT) Date: Mon, 22 Jun 1998 10:53:48 -0400 (EDT) From: Paul Griffith To: freebsd-questions@FreeBSD.ORG Subject: Solved: Solaris/FreeBSD can't talk to each other 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 See orginal post at end of message. What I did was install and configure a SMC 16bit ISA ethernet card (8416), and used the same crossover cable as before. It worked fine, I could telnet, ping, and use Lynx to access the Document server on the Sun box. I then swapped the Intel card from the Sun box with the one in the FreeBSD box just in case it was a bad card. But the card that was in the Sun box worked fine in the FreeBSD box. The problem lies with the Sun Solaris v2.6 Intel EtherExpress driver (iprb0). I can only assume that it is looking for the heartbeat pulse from a hub. All I know is that with Solaris v2.6 X86 and the Sun Intel ExtherExpress 10+ driver (iprb0) will not work with a crossover cable. ------ original message follows ------- Okay all you FreeBSD/Solaris experts here is the problem: my FreeBSD and Solaris box can't talk to each other here are the details: Sunbox - P166 w/256KB L2 cache running Solaris v2.6 5/98 release. unit has 80MB of ram, Intel EtherExpress 10+ (iprb0), Adaptec 1542, no ide devices. ip-info= 192.168.1.10, netmask 255.255.255.0, broadcast on 192.168.1.255 note: Before I installed Solaris, this box was a ppp gateway to the net running a ftp server, and 2 web servers. The hardware works. FreeBSDbox - p133 w/512KB L2 cache running FreeBSD 2.2.5 release. Unit has 24MB of ram, Intel EtherExpress 10+ card (fxp0) , SMC isa card (ed0), running off on-board IDE 2.1 GB HDD. ip-info=192.168.1.11, netmask 255.255.255.0, broadcast on 192.168.1.255 ip-info(ed0)=192.168.1.12, netmask 255.255.255.0 broadcast on 192.168.1.255 Both boxes are connected to each other with a 10BaseT crossover cable. To test the cable I connected it between the ed0, and fxp0 on the FreeBSD box. Pinging the ed0 from the fxp0 worked just fine, the rx (receive), and tx (transmitt) leds on the ed0 (SMC) both flashed. Ping reported no errors. >From the BSD box when I ping the sunbox, tcpdump reports the following: arp who-has 192.168.1.10 tell 192.168.1.11 over and over. But the traffic light on the fxp0 only flashes 6 times. ping reports host is down. >From the Sun box when I ping the BSD box, snoop reports the following: arp c who is 192.168.1.11 tell 192.168.1.10 over and over. But the traffic light on the iprb0 flashes 6 times. ping reports no answer from host. If I move the same cable from the fxp0 on the BSD box to the ed0 on the BSD box the rx light only with flash about 6 times also. The tx light stays off. arp -a on the sunbox or the BSD will only report the MAC addresss for the local network cards. When I ping the sunbox from the BSD box, then do a arp -a from the BSD box it will report 192.168.1.10 ? (incomplete) likewise on the sunbox. Any want to take a crack at this ? Do I have to start disassembing packets now ? Any helpful info you have please e-mail me. I will post a summary once it's all working. Either I missed one simple step, or God wants me a run all FreeBSD boxes :-) Many Thanks Paul Griffith BTW: Reinstalling Solaris is not an option. Paul Griffith - paulg@interlog.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message