Subject: Re: [netatalk-admins] Re: AppleTalk routing
From: Bill Studenmund (skippy@macro.stanford.edu)
Date: Wed Jan 28 1998 - 15:42:29 EST
On Sat, 17 Jan 1998, Amitai Schlair wrote:
> I wrote:
>
> > I'm running Netatalk 1.4b2 (with Arthur Sun's patches) on NetBSD 1.3,
> > and I'm trying to get AppleTalk routing, as described in atalkd(8),
> > working. I've got AppleShare IP on ae2 (accessible to the LAN), and I'd
> > like my Mac (connected to ae1) to be able to access AppleShare resources
> > on the outside network, as well as those on the NetBSD box. Is this
> > possible? If so, how do I configure ae1 in atalkd.conf? (Letting atalkd
> > auto-configure the interfaces on startup didn't work well at all.)
>
> Despite my total lack of experience with and understanding of AppleTalk
> internals, I managed to hack my way partly there. From my Mac (connected
> to ae1), I can now see all the zones on the LAN (connected to ae2).
> However, the only AppleShare volume I can see in the Chooser (or any
> AppleTalk service for that matter) is the one on my NetBSD box. I'd like
> to be able to see all the AppleShare volumes out there on the LAN, if
> possible.
>
> My atalkd.conf:
>
> ae2 -phase 2 -net 25-50 -addr 25.33 -zone "CWRUnet" -zone "Chemistry"
> -zone "Housing" -zone "Statistics" -zone "neurosciences" -zone "WSOM"
> -zone "Smith Lab" -zone "Physics" -zone "Neutral" -zone "Net Services"
> -zone "Music" -zone "MSASS" -zone "Medicine" -zone "Math" -zone
> "Libraries" -zone "Health Sci" -zone "ESS" -zone "Engr" -zone "EEAP"
> -zone "CIT" -zone "CP&P" -zone "CNS Internal" -zone "CIM" -zone "CES"
> -zone "BRB" -zone "BIOMED" -zone "Arts & Sci" -zone "Archives" -zone
> "AIS" -zone "Administration" -zone "South Residences" -zone "North
> Residences" -zone "Medlab" -zone "Meds" -zone "Asian Studies" -zone "INS
> Internal"
> ae1 -phase 2 -net 51-75 -addr 51.33
>
> The AppleTalk Phase II network range for the LAN, as described in the
> network docs, is 25-50. "CWRUnet" is the default zone; I have my AFP
> service running in "North Residences". (My connection to the LAN on ae2
> works great.) The bit of hackery I did to get on the AppleTalk network,
> sort of, was to set the netrange on ae1 in atalkd.conf to 51-75
> (wrong?), and manually set the network and node in the Mac's AppleTalk
> control panel to some reasonable numbers.
Are ALL of these zones available on the same wire?? If you go to the
Network (not OpenTransport) or the AppleTalk (OpenTransport) Control
panel, do you see all of these zones?
> Despite my inexperience, I'm pretty sure my ae1 netrange setting is why
> I can't see the machines on the LAN... but I can't get anything at all
> when I set it properly (25-50).
25-50 is NOT right! Each wire, like your internal net, should have its own
netowrk number, or net range. Node numbers (net.node) are address like IP
addresses (except they are randomly choosable and don't scale to world
sizes). So your internal wire will have to have its own number, so the
other computers can have a chance of talking to you.
I'd suggest a netrange of just one number (say 51). You can get upwards of
250 nodes per net, so you don't really need 25 of them. :-)
> I'm also getting a lot of messages on the console:
>
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast CIT exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast CIT exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast CWRUnet exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast CWRUnet exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast EEAPo exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast EEAPo exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast CWRUnet exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast CWRUnet exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast EEAPo exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast EEAPo exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast CWRUnet exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast CWRUnet exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast EEAPo exists
> Jan 17 20:27:08 b60735 atalkd[224]: zone_bcast EEAPo exists
>
> and so on. I hope I'm not making an AppleStorm on the LAN! How can I fix
> all this to work properly?
As Stefan said, talk to your admins. For this to work, the other routers
on campus have to know about your net number.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:30:36 EST