roy@alanine.phri.nyu.edu (Roy Smith) (04/16/91)
As I understand the setup documents that come with CAP-60, you have
to statically assign the CAP server an AppleTalk node number to put in the
atalk.local file. Where does one come up with this number, and how does
one ensure that it doesn't duplicate an existing node number? Why can't
CAP engage in the dynamic node ID assignment (LLAP Enquiry/Acknowledge)
like every other AppleTalk object?
--
Roy Smith, Public Health Research Institute
455 First Avenue, New York, NY 10016
roy@alanine.phri.nyu.edu -OR- {att,cmcl2,rutgers,hombre}!phri!roy
"Arcane? Did you say arcane? It wouldn't be Unix if it wasn't arcane!"kre@cs.mu.OZ.AU (Robert Elz) (04/17/91)
roy@alanine.phri.nyu.edu (Roy Smith) writes: >Why can't >CAP engage in the dynamic node ID assignment (LLAP Enquiry/Acknowledge) >like every other AppleTalk object? The IPtalk protocol (that CAP uses in the way you're using it) requires a 1:1 mapping between IP address and appletalk address, so it knows to which IP address to send packets addressed to any particular appletalk address (things could have been done other ways, but they weren't). The IPtalk node number is the low 8 bits of your IP address (subnet masks are irrelevant here). No choice, no options, that's just how it is. What's not quite so clear is just why CAP requires you to configure it, instead of just configuring it ... I think that derives from very ancient history before the 1:1 mapping was created, and instead gateways had tables of addresses compiled in - and the direct relationship wasn't required. Needless to say this couldn't survive beyond the times when everyone built their own gateways with their own soldering iron... kre