Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!eds.com!hughes
From: hughes@eds.com
Newsgroups: comp.protocols.iso.dev-environ
Subject: ISODE 6.0 over Sunlink OSI 6.0
Message-ID: <9004111631.AA26792@molokai.eds.com>
Date: 11 Apr 90 16:31:28 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 33

Hi,

You may have seen my earlier request for information on getting
ISODE-6.0 running on a Sun 3 OS4.0.3 using Sunlink 6.0.  Well... I got
our Sniffer running and found out that for some reason the ISO IP
destination address being sent out is not correct and so the Sun is
broadcasting to the ES broadcast address looking for the destination
node.  What I see on the Sniffer when I run isode-test, for example, is
a destination address "0000000001<ethernetaddr>fe00" with the
appropriate Ethernet address inserted.  The source address is correct
"0001<ethernetaddr>fe00" - i.e. even when it's supposed to be talking
to itself (during isode-test) it gets it's own address correct as the
source address, but puts a bunch of 0s (5 to be exact) in front of the
"correct address" on the destination address.

Now I compiled this software on one Sun & installed it there and on two
others.  The Sun that it was compiled on works fine (i.e. talking to
itself and also talking to the other two Suns - as long as it is the
one initiating the session).  When I look on the Sniffer the source &
destination addresses are fine.  On the other two Suns they get the
destination addresses messed up.  I tried re-installing (carefully
checking that I set up the config.make files correctly), I synchronized 
the isoentities files etc. & still no luck.  I guess I don't know 
enough about the software to understand where it get's it's addresses 
from and how it interacts with the Sunlink software...
Any ideas from all of you ISODE/Sunlink gurus out there?


Thanks in advance,
Bill Hughes
EDS
TSD/PME/C4IT
hughes@eds.com