Subject: [netatalk-admins] Trouble with nbprgstr...
From: Typeline Webmaster (web@typeline.com)
Date: Fri Mar 13 1998 - 00:34:27 EST
We've got a CAP server on our Network and have been playing with
Netatalk
for the past few weeks. I really like Netatalk. It's Much easier to
configure than CAP. For some reason CAP has come back to haunt us. After
getting Netatalk up
and running *while* the CAP server was still on our net, Netatalk
refuses to complete the registration part in the startup script after we
take the CAP server down.
With an early version of FreeBSD, we had to us UAR, a software based
router to get CAP to work. It seems like atalkd is relying on the UAR
router to get network information. With the router, atalkd creates the
atalkd.conf file as:
fxp0 -phase 2 net 97 -addr 97.12 -zone "MyZone"
Without the router it's:
fxp0 -phase 2 net 0-65536 -addr 97.130
With the UAR router we did specify a separate zone, "MyZone". It seems
as though
Netatalk needs this zone to complete an nbprgstr. I don't understand why
it
fails to complete the registration process in the netatalk.sh script
when the
default zone "*" is the target.
Please help. I'm really stuck on this.
Thanks
Bob
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:31:34 EST