cordy@qucis.queensu.CA (Jim Cordy) (06/08/89)
As anyone who owns one is well aware by now, Cayman's NFS-to-AppleTalk software runs out of memory every little while, rendering the GB more or less useless as a file service device. (Yes, I know they are diligently working on it.) Meanwhile, I read that some people have gotten around this problem by running CAP through the GB instead. I'm interested in setting this up, but I can't seem to get CAP and the GB to recognize one another. IT seems that the CAP, KIP and GB documentation don't mesh very well and don't tell me which network numbers must be the same as which. I think I have it right, but then nothing works. If you've made CAP work through a GB, *PLEASE* drop me a line and tell me the secret incantation. Thanks. Jim Cordy@Qucis.QueensU.CA
chip@ateng.ateng.com (Chip Salzenberg) (06/09/89)
According to cordy@qucis.queensu.CA (Jim Cordy): >If you've made CAP work through a GB, *PLEASE* drop me a line and >tell me the secret incantation. Thanks. Since this should be of general interest, I'm posting. Here is a working CAP-with-GatorBox configuration. I use it with NCSA Telnet, aufs and lwsrv. I'm not Internet-connected, so I've appropriated the class A network "50" for my own use; modify as appropriate. /etc/tcp on CAP host: # # network host configuration (two max) # ifconfig wd0 50.0.3.5 -trailers \ arp netmask 0xffffff00 broadcast 50.255.255.255 /usr/local/lib/cap/atalk.local on CAP host:: # mynet mynode myzone 3 5 Danger # bridgenet bridgenode bridgeIP 3 120 50.0.3.120 GatorKeeper configuration: TCP/IP: TCP/IP Option On (but you knew that :-)) IP Address 50.0.3.120 Broadcast 50.255.255.255 Subnet mask 255.255.255.0 MacIP: From 50.0.3.128 To 50.0.3.159 AppleTalk Routing: LocalTalk Net 1 LocalTalk Zone "LocalTalk" EtherTalk Net 2 EtherTalk Zone "EtherTalk" KIP: KIP Net 3 KIP Zone "Danger" KIP IP Net 50.0.3.0 I think the trickiest part of this configuration is the "KIP IP Net". If I understand this number correctly, it is the three most significant bytes of all KIP-related IP addresses. I had an -- er -- "interesting" time configuring my network, especially since I could never be sure whether problems were due to configuration or to the System V environment. But it's working now. -- You may redistribute this article only to those who may freely do likewise. Chip Salzenberg | <chip@ateng.com> or <uunet!ateng!chip> A T Engineering | Me? Speak for my company? Surely you jest!