|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T r
Length: 3018 (0xbca) Types: TextFile Names: »rev0688«
└─⟦9ae75bfbd⟧ Bits:30007242 EUUGD3: Starter Kit └─⟦3b20aab50⟧ »EurOpenD3/network/snmp/kip-snmp.91.tar.Z« └─⟦b503a39fe⟧ └─⟦this⟧ »kip/doc/rev0688«
06/88 REVISION OF KIP (KFPS IP) The June 1988 revision of KIP is primarily a maintenance release providing improved capabilities for UDP port assigments and better functionality with non-KIP bridges. In addition, KIP now prints out a version number when starting up. UDP PORT ASSIGNMENTS Previous revisions of KIP used a range of UDP ports started at 768 to map the "well known" DDP sockets from 0 to 127. This was done to allow a fixed mapping from the DDP socket well known space to the well known UDP port space. In April, 1988, the NIC assigned a number of ports: 201 - AT-RMTP - AppleTalk Routing Maintenance 202 - AT-NBP - AppleTalk Name Binding 203 - AT-3 - AppleTalk Unused 204 - AT-ECHO - AppleTalk Echo 205 - AT-5 - AppleTalk Unused 206 - AT-ZIS - AppleTalk Zone Information 207 - AT-7 - AppleTalk Unused 208 - AT-8 - AppleTalk Unused for this purpose. Note that there are 126 (0 is invalid) ddp well known sockets to map to space of 8 udp ports. DDP Ports 1 through 63 are reservered for use by Apple and new assignments for these will be applied for as they are put into use by Apple. DDP ports 64 through 127 are designated for experimental use only. KIP now allows the specification of a different start range of UDP ports to accomodate these new assignments. It does not check to see if the ports have been assigned. You should be warned that it can conceivably use the UDP ports rangestart+1 through rangestart+127. However, in practice, only the "named" ports (e.g. at-nbp, etc) will be used unless you use the experimental ports which probably isn't recommended in any event. To do this, an unused field on the Kinetics box configuration is used (right after the ethertalk specification). A value of 0 implies the mappings starting at 768. A value of 200 specifies the NIC assigned values. WARNING: use of any other start values is NOT recommended. atalkad will warn of conflicting port usages between different Kinetics boxes in the same atalkatab. CAP 5.0 is configured to use the new port mappings by added specified names to /etc/services. In particular, it looks for the following "official service names": at-nbp, at-rtmp, at-echo, at-zip by using getservbyname. (man getservent for more information). NON-KIP BRIDGE FUNCTIONALITY Revisions of KIP prior to 6/88 had a tough time with non-KIP bridges. This was especially true of KIP 9/87. The problem was in the fact that KIP did not do Zone acquistions on routes. As of KIP 6/88 zone acquisitions are done. VERSION KIP now prints out a version number along with the number of buffers, etc. when it starts up. This is viewable from Prompt's (2.0 or later) "Show Diagnostics". OTHER CHANGES EtherTalk length was getting reset in the wrong way. Allzones was on for "unknown" zones. FILES MODIFIED OR ADDED README Makefile conf.h glob.h gw.c gw.h gw2.c gwctl.h ie.c kfpsversion.h rtmp.c doc/README doc/rev0688 doc/install etc/atalkad.c etc/atalkatab