gillian@uniwa.uwa.oz (Gillian Affleck) (07/02/90)
Many thanks to Tom Evans of Webster Computer Corp. for his reply (yet again) to my call for help. I seem to get better support for my FastPath from the makers of MultiGate than I do from those who are supposed to support it! (I don't think my next AppleTalk-to-Ethernet Gateway will be a FastPath unless they can provide better support). The reply from Tom follows: > > I'm having problems setting up a Kinetics FastPath 4 (K-STAR v. 7.0) to > > obtain its configuration from a Sun running atalkad. > > Why not ask TriCom (no they won't know), Kinetics, Excelan, Novelle, > Shiva (no they havn't got the box yet, let alone the support). Sorry, I > couldn't resist that. > > > My problem is that I'm using "split addressing" (i.e. the LocalTalk network > > is set up as a different IP (classs B) subnet to the Ethernet network). > > It should work if you treat it simply. The FastPath manual tells you to > enter everything into the config that you DON'T enter into atalkatab. > Thus you'll need the separate IP address. Note it MIGHT also be one > of the four "Police" entries in atalkatab - you know the line that > goes "L0 L0 L0 L0". Bad pun, sorry. These four "unused" entries might > (might, mind you) map to the four "Local Parameters" in the kbox. > > You'll probably have to set bit 9 in the flags field. We can only assume > that atalkad takes precedence, but who knows? I didn't have to do this. See below for more details. > > Note that atalkad and atalkatab (and the reason for them existing) couldn't > give a damn about the split addressing, now that Megan 1.24 and 1.25 > have been released. You now do not need atalkad and atalkatab with > MultiGate UNLESS you are trying to transport AppleTalk across IP networks > with intervening IP routers. The requirement for all the MacIP addresses > (IP addresses and Static and Dynamic parameters) for the creation of the > IP Proxy Table is now no longer necessary. > > Atalkad now only maps IP Networks to IPTalk (AppleTalk) network numbers, > and LocalTalk network numbers with the IP address of the box that gets > you to them. It is the source of the AppleTalk routing table. > > If MacIP (NCSA Telnet etc.) services don't work it is either: > > atalkatab is "wrong" and a pre-Megan-1.24 MultiGate is stomping it > > You havn't got routing information in your IP hosts to tell them > how to route to the "split-off" IP network on the kbox. Check > the routing tables in your Unix hosts - "netstat -r". > > > Now, in my atalkatab file I have a "K" entry for the FastPath which > > specifies the IP address of the FastPath on the LocalTalk side. That is, > > the first line of the entry looks like: > > > 0.3 KC 130.95.96.1 microzone > > > The IP address of the FastPath on the Ethernet side is 130.95.128.9. > > Won't work. You're telling everyone that AppleTalk network 3 is > connected to the IP device 130.95.96.1, which will be your first Mac > to run NCSA Telnet. The FastPath doesn't own n IP address on this > network (unlike the MultiGate which does). > > > I'd also like to know exactly what the FastPath does when option 9 is turned > > on and it's getting its configuration from atalkad (i.e. why does option 9 > > need to be turned rather than getting this information from atalkad as well)? > > A problem. The kbox doesn't really need to get any configuration info > from atalkad, but it does. The MultiGate does too, but only for the > first entry (main motherboard IP address) and it ignores all data except > for the "UDPPort" entry. They all need the aaROUTE table info so they > know how to get to other networks. Note if they aren't separated by IP > routers then they will be exchanging EtherTalk RTMP packets and keeping > themselves updated that way. > > Tom Evans > wcc@cup.portal.com > Webster Computer Corporation > Suite J, 2109 O'Toole Ave. San Jose, California 95131-1303 > Ph (408) 954-8054 FAX (408) 954-1832 > > Head Office > tom@wcc.oz.au, multigate@wcc.oz.au > 1270 Ferntree Gully Rd. Scoresby, Victoria, Australia > Ph 61 3 764-1100 FAX 61 3 764-1179 > Now for what I did. First I upgraded to K-STAR version 8 as it appeared to have better support for atalkad. I got it to work by specifying the following as my "K" entry in atalkatab for the LocalTalk side: 0.3 KC 130.95.128.9 microzone Using the FastPath manager I specified: - the IP address of the FastPath (130.95.128.9) - the IP address of the Admin host - turned on options 9, 17, 18 (17,18 are required if you want to use EtherTalk Phase 1 with K-STAR 8). - the IP address of the subnet on the LocalTalk side (130.95.96.1) local parameter #1 (I also specified the netmask in local param #2 but this is probably not necessary). And it all works ok. One thing I did notice when I ran "atalkad -c" was that the proxy entries for the static and dynamic addresses showed up as being on the 128 subnet. Does atalkad doing anything with these entries, or should I just ignore them? The macs themselves get allocated addresses on the 96 subnet. From a Mac on the LocalTalk network I can telnet to anywhere and access a Sun running CAP as an AppleShare File Server. I did have a problem with netmasks initially, as the netmask on the Sun which was running CAP was set up incorrectly to be 255.255.0.0, whereas the FastPath had the (correct) netmask of 255.255.255.0. Hence, NBP broadcasts on the ethernet were being sent to 130.95.128.255, and the atis program on the Sun never got the broadcasts. I just thought I'd mention this in case any one else comes across the same problem. --------------- Gillian Affleck Internet: gillian@uniwa.uwa.oz.au West Australian Regional Computing Centre ph. : (09) 380 3692 University of W.A. fax : (09) 382 1688