Subject: [netatalk-admins] I'm missing something. [long]
From: Andrew Brennan (brennan@crashprone.auhs.edu)
Date: Mon Sep 15 1997 - 22:05:09 EDT
Ok. I have here a Pentium/90 running Linux (kernel is a freshly-
compiled 2.0.30 with Appletalk in the kernel, not modularized).
3Com Etherlink III card inside. I also have a clean network --
courtesy of an 8 port hub with only the Linux box and a portable
Mac connected.
I have had nothing but difficulty with the Debian install of the
netatalk package (mildly untrue, but you'll find out where I'm
going momentarily) and decided to get the 1.4b2 source and load
it in by hand. Installed it, rebooted and ran rc.atalk with the
zones I need in the /usr/local/atalk/etc/atalkd.conf file.
eth0 -seed -phase 2 -net 500-502 -addr 500.133 -zone SanAndreas
... and once again, I see no zone information and my atalkd.conf
has been rewritten to:
eth0 -seed -phase 2 -net 0-65534 -addr 500.133
Looking at the tips sheet, I see possible reasons for problems.
o non-multicast Ethernet cards.
... but the card works fine for afpd and appears to advertise
the system correctly, so this one isn't(?) it.
o Large range of defined networks on cable segment.
... I tested with a disconnected hub and a single Mac portable
(even had it disconnected for a few tries). Not this one.
o No router on network, atalkd can't assign it's own number.
... it's *never* had difficulty assigning itself an address.
o No DDP support in kernel.
... (above) fresh kernel, shouldn't be the problem.
o Second start of atalkd.
... I'm rebooting between tries, so this one isn't it.
I'm out of ideas. Possibly the card doesn't support multicast
completely? IFCONFIG reports it as having MULTICAST enabled,
but maybe it's lying? It also reports "Ethertalk Phase 2 addr
500/133", so I don't think it's my card. (also visible afpd
activity from the portable Mac)
This is probably related ... getzones -l, getzones -m and even
getzones 500.133 (above - the netatalk box itself) all respond
with a "atp_rresp: Connection timed out" error. At the same
time, aecho 500.133 reports a 0% packet loss (and can echo the
other Mac w/o any loss as well).
I would really like to have this system act as an AppleTalk
router (we need one on this segment) but it's refusing me at
every turn. Anyone see something obvious that I've missed??
andrew. (brennan@auhs.edu)
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:26:40 EST