hflai@squid.ucsb.edu (Hsun-Feng Lai) (05/10/91)
A small bug was found in CAP6.0 library. The term 'at-zis' is typo of 'atzip' in abkip.c, ddp2ipskt. Fixed it would make getzones work on well known UDP port. However, I still couldn't get atlook working. It reported the correct gateway address and UDP port. But it timeouts each time I run it. I have the following questions: Do I need to run kip or uab to run atlook? What is wrong if getzones works but atlook doesn't? Thanks in advance for any kind help. Hsun-Feng Lai ///////////////////////////////////////////////////////////// hflai@squid.ucsb.edu \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
djh@cs.mu.oz.au (David Hornsby) (05/10/91)
In article <11155@hub.ucsb.edu>, hflai@squid.ucsb.edu (Hsun-Feng Lai) writes: > A small bug was found in CAP6.0 library. The term 'at-zis' > is typo of 'atzip' in abkip.c, ddp2ipskt. This isn't a bug, "at-zis" is the correct official port name for the Zone Information Socket (ZIS) from the Zone Information Protocol (ZIP). From your problem description, and the fact that changing at-zis to something else makes getzones work, it seems that your gateways are using the old port range (768) and your CAP host /etc/services file contains entries for the new port range (200). The alternative, of course, is that the /etc/services file contains the wrong names entirely and you should be using the 200 range ... Try commenting out/correcting the the at-* entries in /etc/services (and doing whatever magic it takes to make yellow pages learn the new information) and run the CAP programs again. See the discussion on port numbers in the CAP 6.0 doc/install.ms file. - David.