Re: [netatalk-admins] routing problem


Subject: Re: [netatalk-admins] routing problem
From: Bill Studenmund (skippy@macro.stanford.edu)
Date: Fri Jul 25 1997 - 20:17:08 EDT


On Fri, 25 Jul 1997, Miles Nordin wrote:

> > Try something like:
> >
> > fxp0 -phase 2 -net 1-1 -addr 1.1 -zone "FirstZone" -seed
> > fxp1 -phase 2 -net 2-2 -addr 2.1 -zone "SecondZone" -seed
> > fxp2 -phase 2 -net 3-3 -addr 3.1 -zone "ThirdZone" -seed
> > ep0 -phase 2 -net 4-4 -addr 4.1 -zone "FourthZone" -seed
> >
> > Also, your FreeBSD box will now, I think, route between the nets.
>
> as a standard disclaimer, i've never done this bevore either but have read
> about it a lot. hopefully i am not about to make a fool of myself.
>
> I don't think you need to specify different zones on each net. I think
> you may be better off using one zone.

That's a matter of choice. If you have a few macs, you're probably right.

> Second, there is one more thing you need to know that he didn't tell you.
> There is an ordedr this has to be done in.
>
> 1. Shut off _every_ mac on all four subnets. NO EXCEPTIONS. maybe use
> nbplkup starting atalkd one net at a time to ensure this.
> 2. Start atalkd on the FreeBSD machine with Bill's suggested atalkd.conf
> 3. Restart all the Mac's.
>
> Mac's only choose their node address once at boot. If there is no router
> on the subnet, they will choose the zoneless nets above 65280. If there
> is a router, they will choose an address that falls in the acceptable
> range indicated by the router. but, you cannot start a -seed router if:
>
> a. there is another seed router on the subnet, or
> b. there is a Mac on the subnet powered on that did not boot under
> the controlling influence of the seed router you are trying to
> bring up.
>
> so... remember, 1 seed router per subnet, and don't start new seed
> routers until everyone else is off the subnet.

I've never heard of this latter restriction. It doesn't seem to be present
in netatalk, as far as I can tell. I've looked in etc/atalkd/main.c, and
there seems to be no checks to see if there are macs on the interface
before seeding an interface.

My copy of Inside Appletalk is at home, but I thought that if a mac booted
w/o seeing a router, but then saw a router, it would change its address to
be in the new netrange. Too bad for any existing connections.

I'll look it up, but it'll be a while before I can get back as I'm moving
across town this weekend.

> For example, if you were to get yet another FreeBSD box with two
> interfaces routing between the net on fxp2 and a fifth subnet, you would
> config the interface that shared fxp2's wire _without_ -seed, and the
> fifth subnet _with_ -seed. and, everyone on the fifth subnet would have
> to power down before you started this second FreeBSD router.

I'd suggest you put -seed in the second box's config too. I thought (and
I'm sure I'll be corrected) that you can have multiple seed routers AS
LONG AS THEY ALL AGREE. The code in etc/atalkd/zip.c around line 600 in
1.4b2 only squalks if we get a zip reply on a SEED interface which
differes from the seed config. I think it's ok if they agree.

Thus it won't matter what order you started the servers on fxp2!

> make sense? anyway good luck... as i say i've never done this myself,
> but as with most things that come out of Apple, the rules have an eerie
> almost essential seductive logic to them.

Yeah, but I thought they generally tried to deal with problems on the fly
(like not having a cable hooked up, etc).

Take care,

Bill



This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:25:49 EST