Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!group1!johnw From: johnw@group1.UUCP (John Wheeler) Newsgroups: comp.protocols.appletalk Subject: Re: Split-addressing with Fastpaths & atalkad Keywords: Split addressing mode, Fastpaths, atalkad, Bad news Message-ID: <1991Jun21.054142.7295@group1.UUCP> Date: 21 Jun 91 05:41:42 GMT References: <4545@stl.stc.co.uk> Organization: Group One, Ltd.; San Francisco Lines: 106 In article <4545@stl.stc.co.uk> "Stewart Tansley" writes: >Questions: >- Has anyone got a copy of their atalkatab and atalk.local files that they > could send me, where you are using a similar split-addressing setup? Sure: We have 8 subnets spread across 3 cities (San Francisco, Chicago, and New York) with FastPaths in each. The top 2 subnets are unused, and the other 6 are divided as follows: 1 -- SF regular TCP/IP stuff 2 -- SF MacTCP on LocalTalk using split addressing 3 -- Chicago regular TCP/IP stuff 4 -- Chicago MacTCP on LocalTalk using split addressing 5 -- New York regular TCP/IP stuff 6 -- New York MacTCP on LocalTalk using split addressing Our CAP/AUFS host (we only have one set up right now) is running atalkad to configure the FastPaths. Our atalk.local file: # # mynet mynode myzone 5 1 IPTalk # bridgenet bridgenode bridgeIP 5 3 192.101.31.3 Our atalkatab: # the IPTalk networks: 0.5 N0 192.101.31.1 IPTalk #SF IPTalk 1.5 N0 192.101.31.65 CBOE #Chicago IPTalk 2.5 N0 192.101.31.159 New_York #NY IPTalk # the EtherTalk networks: 0.2 E 192.101.31.3 Ethernet #SF Ethertalk 1.2 E 192.101.31.67 CBOE #Chicago Ethertalk 2.2 E 192.101.31.131 New_York #NY Ethertalk # the FastPaths: # Madonna: # Mon May 20 11:36:03 PDT 1991 #---------------------------------------------------------------------------- 0.10 KC 192.101.31.3 LocalTalk #madonna, localtalk I192.101.31.31 L0 #ipbroad ipname L0 L0 #ipdebug ipfile L0 L0 L0 L0 S0.2 S200 #ipother atnetet ddprangestart LX0 S16 S8 #flags ipstatic ipdynamic S0.10 S0.5 #atneta atnete ## Prince (Chicago): ## Mon May 20 11:43:49 PDT 1991 ##---------------------------------------------------------------------------- 1.10 KC 192.101.31.67 CBOE #prince, localtalk I192.101.31.95 L0 #ipbroad ipname L0 L0 #ipdebug ipfile L0 L0 L0 L0 S1.2 S200 #ipother atnetet ddprangestart LX0 S16 S8 #flags ipstatic ipdynamic S1.10 S1.5 #atneta atnete # # # Sting (NY): # Mon May 20 11:41:50 PDT 1991 #---------------------------------------------------------------------------- 2.10 KC 192.101.31.131 New_York #sting, localtalk I192.101.31.159 L0 #ipbroad ipname L0 L0 #ipdebug ipfile L0 L0 L0 L0 S2.2 S200 #ipother atnetet ddprangestart LX0 S16 S8 #flags ipstatic ipdynamic S2.10 S2.5 #atneta atnete # # >- Any problems I should know about in this setup -- eg. why would we get > such a broadcast storm? Does split addressing *work* using atalkad? Make sure you also have option 17 - transition mode - set. Unless it is, a "storm" of FwdReq packets seems to get generated instead of being converted to lookups within the FP. We had this problem, too. Also, if you don'y have it, get K-STAR 8.1.1 from Shiva. It's available all over for downloading (CompuServe, I believe, other public places, etc., they also have a BBS). It allows subnet masks to be entered in 'user parameter 3'. >- To experiment, I may wish to setup a second atalkad -- can I run this > while the existing one is running (it's control is out of my hands), but > running different atalkatab files? I wouldn't try that....I have enough trouble keeping ONE running. >- Why me? :-) Because you're willing to attempt the unproven... > >Thanks for any assistance! :-) -- ________ John Wheeler - Informix-4GL / SQL * Unix * Broadcast Audio Production \rrrr/ Group One Ltd. \/ San Francisco