Subject: Re: netatalk, zones & routers
From: wesley.craig@umich.edu
Date: Wed Jan 19 1994 - 18:18:17 EST
> From: Jon Piesing <jon@prl.philips.co.uk>
> To: netatalk-admins@umich.edu
> This question really belongs in an FAQ but I haven't managed to
> find one so ......
There is one, for anon-ftp in terminator. However, I don't think it
would answer any of the questions you've posed.
> Does this mean that atalkd would let Macs on the two different networks
> talk to each other?
Yes, certainly. The machine I sit at acts as a router for a variety of
machines, for AppleTalk and IP.
> The atalkd.conf file for the gateway Sun is :-
> # le1 = network all Macs are currently connected to
> le1 -phase 2
> # le0 - network we would like to connect some Macs to
> le0 -seed -phase 2 -net 9461-9471 -zone PRL
> The atalkd.conf file for the Sun connected to the same network as le0
> above is :-
> le0 -phase 2 -net 9461 -zone PRL
So, it appears that you don't have any AppleTalk routers, other than
the netatalk machine you're trying to bring up. If that's the case,
then the le1 interface will need to have network numbers defined. For
instance, your atalkd.conf on the router could be
le0 -seed -phase 2 -net 1 -zone PRL
le1 -seed -phase 2 -net 2 -zone PRL
If you do have another router on the le1 interface, then you
configuration is fine, if a little esoteric, e.g. do you really need
room for 2500 nodes on the le0 interface?
Just in general, the non-routing machine doesn't need an atalkd.conf,
at all. It will dynamically configure. Having (incorrect) information
in a machine's atalkd.conf can cause problems similar to what you
describe, since atalkd is not as good as it could be at ignoring
incorrect information.
:wes
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:20:47 EST