Subject: [netatalk-admins] Re: Problems w/ FreeBSD 3.1 as seeding router?
From: Stefan Bethke (stefan.bethke@hanse.de)
Date: Fri May 07 1999 - 09:28:26 EDT
"Douglas E. Wegscheid" <wegscd@whirlpool.com> wrote:
> 1) I am on an isolated LAN (no existing routers), running classic
> Appletalk on the Macs (no OT, no IP). anyway, I think the kernel is OK; I
> can see with the sniffer when netatalk comes up where it looks for other
> routers, and I can see the exchange between the FreeBSD box and the Macs
> when I do a nbplkup. Glenn Johnson (and anyone else), you said you had
> success running this setup, do you have other routers? Can you share your
> atalkd.conf?
> I am starting to suspect this is a bug that has gone undetected because
> everyone else's FreeBSD boxes are talking to existing routers, and I have
> none.
Most definitly not. I've run 2.2.8, 3.1 and -current in both router-less
and networks with routers, and as far as I can tell, it works.
> I put a sniffer on the wire, and the FreeBSD
> box will originate lookups when you do a nbplkup, correctly read the
> responses from the wire and display them, but my FreeBSD box is not
> responding to lookups from the Macs at all...
>
> 2) Have I possibly overlooked something I need to do to my 7.5.3 and 7.5.5
> Macs to get them to talk phase 2?
No. Phase 1 is dead for quite some years now. AFAIR, 7.5 needs OT (or at
least defaults to it), and OT doesn't do Phase 1.
> 3) Blew away /usr/local/etc/atalkd.conf. Shut down. Turn every Mac in the
> house off. Power up. Netatalk starts, comes up with address
> 65280.something.
That's correct if you don't have a router on the network.
> This looks suspicious to me, I thought that was 65280.* was reserved for
> startup. Edit the atalkd.conf to read:
>
> le0 -seed -phase 2 -net 100-200 -addr 100.1 -zone foo
>
> Reboot the box. atalkd rewrites atalkd.conf as
>
> le0 -seed -phase 2 -net 0-65535 -addr 100.1
>
> (perhap -net 0-65536, but definitely not -net 100-200). Why is it ignoring
> my -net and -zone? Am I misunderstanding what -seed should do?
No, but a router needs to route somewhere. You'll either have to use the
-router trick, or set up a (real or dummy) interface to route to. I
believe disc can be used for that. Then, I've never tried, and it might
well be that disc doesn't support AppleTalk. I'll try over the weekend.
> 4) So I think to myself, hey, mebbe I would just run appletalk phase 1.
> Blow away atalkd.conf, fix the netatalk.sh to start atalkd with -1,
> shutdown all the Macs, cycle FreeBSD. atalkd won't start, get kernel
> messages ('aa_addsingleroute: errno 17' (not sure if it was
> aa_addsingleroute, sure the message origniated in at_control.c in the
> kernel). Should blowing away atalkd.conf and putting -1 on atalkd
> successfully bring up netatalk phase 1?
I suspect Phase 1 is broken in FreeBSD. See above why it doesn't matter
anymore. IMHO, all references to Phase 1 should be nuked to avoid
confusion.
> 5) Is there anything I can do to atalkd to get it to provide me with more
> information that I can use to debug this? I already enabled the debugging
> printouts in the kernel netatalk/at_control.c, so I am getting more
> information when the interface gets jiggled...
atalkd is a mess (IMHO). It would be really nice if someone :-) would try
and add decent debugging.
Stefan
-- Mühlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@freebsd.org
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:16:41 EST