hughes@eds.com (04/09/90)
Hi, I've been trying to get ISODE-6.0 to run over Sunlink OSI and have not been having much success so... I thought I'd try to see if the world can tell me I'm doing wrong. Firstly am I wrong in thinking that ISODE can be run over the Sunlink OSI transport (TP4) rather then over TCP? I've got a Sun running OS4.0.3 & Sunlink OSI 6.0 & ISODE-6.0. I use the sunlink.make & sunlink.h type configuration files for the compiles - and everything goes OK. The tsapd & application start up & work fine ...BUT they are running over TCP and not Sunlink's TP4. I've tried compiling without the TCPIP & SOCKETS switches but ran into problems... Also does anyone have a quick dissertation on how addressing in ISODE works? I understand the basic concepts but what I don't understand is what is the correlation between what's in the isoentities files and whats in the Sunlink OSI hosts files, how do I set up other nodes running Sunlink OSI to talk to me, etc? Mind you since I'm not currently able to run over TP4 I guess I should worry about this later... Anyways does any one have any ideas about what I'm doing wrong? Bill Hughes EDS TSD/PME/C4IT hughes@eds.com
hughes@eds.com (04/11/90)
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