Subject: Re: [netatalk-admins] routing problem
From: Bill Studenmund (skippy@macro.stanford.edu)
Date: Wed Jul 30 1997 - 14:07:30 EDT
On Wed, 30 Jul 1997, Jeffrey Thompson wrote:
> >atalkd listens for other routers on the wire. Normal mac clients
> >shouldn't respond, so there won't be a problem. Please let me know if
> that's
> >wrong.
>
> Mac clients will not respond, however, other appletalk routers will,
> such as routers, netware servers routing appletalk (3.1x servers
> providing appletalk services), HP directjet cards, will all respond to
> the router query for existing network info
> on the network. However, if appletalk routing devices agree on the
> network number/range, zone names, and default zone for the network then
> bringing up a new router should not be a problem.
>
> I thought macs broadcasted their address every so often? It should be
> the case that atalkd would listen for mac clients that may want to use
> it's services. My problem is, when mac clients are turned on, after
> atalkd starts, that the mac clients can't use the atlakd service. But
> that's not what happens with our AppleShare server. It simply doesn't matter
> if your mac is on or not, the AppleShare server listens for additional
> clients coming online. Since I can't rely on an atalkd connection, it makes
> atalkd all but unusable in a mac network.
Appletalk ROUTERS broadcast their address every so often. Actually, on
phase 2 nets, I think they limit themselves to the multicast addresses.
Is you appleshare server trying to be a router? If not, then what you
describe above makes sense. It's not the fact that atalkd will permit file
sharing, but that atalkd acts as a router. When atalkd fires up, the wire
goes from routerless to with-router. If your Appleshare server is just a
file server, it doesn't touch the router question, so its presance won't
change the net numbers on the wire.
I'm puzzled by the latter half of your comment above. If atalkd is acting
as a router (really linking nets together), why isn't it up 24/24 7/7? If
it's not going to be up all the time, then a better choice would be to run
it (atalkd and your net) routerless. Don't add a "-seed" to the
atalkd.conf line for that net. Then your net won't be going from router to
routerless all the time.
> >Also, I don't think you have to have the macs off before booting the
> >server/router. You just have to restart them after the router comes up
> >before they will do appletalk correctly.
>
> Strange. Why does AppleShare not act this way?
As above, it's not the file serving of netatalk (afpd), but the routing,
which is the problem.
> I'm contemplating switching to Columbia Appletalk Server, CAP.
I think you'll have the same problem with CAP, if you configure it the
same (if you configure UAR to seed the network but don't have UAR up all
the time).
Take care,
Bill
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:25:52 EST