minar@reed.bitnet (Nelson Minar,(???)) (06/27/90)
three parts of this post - a machine specific question, an unknown NBP protocol question, and a details of ALAP destination and source address question. machine specific: I have been trying to get CAP version 5.00 to run on our DECstation 3100s. I have patched the sources to byteswap structures when appropriate by defining BYTESWAPPED (but not LOOSE_BYTESWAPPED) (I believe an earlier poster has pointed this out). With this patch, the DECstation can perform Lookups ok, and can indeed use the papif filter. However, I find that the DECstation is still incapable of registering via NBP. I have tried registering both through the aufs application, and registering by a test program I wrote. In all cases, a -1025 (nbpNoConfirm) is returned. By examining the net traffic (using a LAN program), I can see that the DEC is properly processing the NBPLookup phase of registration, but gets confused upon registration, which leads me to my question about NBP protocols. NBP protocol: In the AppleTalk manuals available to me, the NBP section details 3 NBP packet types: A BrRq (0x1), a LkUp (0x2), and a LkUpReply (0x3). I understand these packets. However, CAP seems to use several other packet types for which I have no documentation: Register (0x7), Delete (0x8), Tickle (0x9), StatusReply (0xa), and LookAside (0xb). Where can I read about these other NBP packet types? I am specifically interested in the Register request, as it is the one that I need to have working, and it is failing. The DECstation seems to send this packet (with a little oddity in the ALAP header), but things are fouled up after that. I am a little confused about the ALAP header. ALAP addresses: After the frame preamble of an ALAP packet, there are 3 bytes - Destination address, Source Address, and LAP type. For NBP packets, LAP type is 0x2 - I've been using this to identify packets when I am watching the network. I have noticed some inconsistencies in the usage of the Dest and Source addresses, however. When a DECstation sends an NBP request to its bridge (a Kinetics FastPath running KIP 06/88), the Destination and Source addresses are set up properly - Source is the DECstation, and Dest is the Kbox. However, when the bridge sends messages back to the DECstation (on any NBP request), these addresses are munged - Source is set to 0xFA, and Dest is set to 0xCE (which have no bearing to our network at all). The DECstation is still capable of understanding this message, however. Furthermore, when the DECstation sends a Registration packet, the ALAP Source and Destination addresses are BOTH set to the DECstation's address. I would worry about this, but this does seem to be correct behaviour (based upon another machine - a VAX - that operates correctly and yet does the same weird addressing). Why are the ALAP addresses set up this way? Summary: Has anyone gotten CAP to work correctly on a DECstation 3100? Specifically, I need to be able to make aufs work (I have papif working). What are the extra codes in NBP, specifically the NBP register code 0x7? Why are the ALAP addresses so inconsistent? They only make sense on BrRqs from the DECstation - the bridge munges them, and the Register requests look strange. I appreciate any help on this. I've been beating my head against it for an embarassingly long time. I'll be sure to summarize responses.