It appears that atalkd.conf gets rewritten by netatalk.
For example my atalkd.conf file originally had...
ne1 -phase 2 -zone "printing"
rl0 -phase 2
but after a reboot it became...
ne1 -phase 2 -net 65280-65534 -addr 65280.83
rl0 -phase 2 -net 65280-65534 -addr 0.0
It was accompanied by the following error messages...
Apr 24 18:35:31 alpha atalkd[212]: restart (1.4b2+asun2.1.4)
Apr 24 18:35:33 alpha atalkd[212]: zip_getnetinfo for ne1
Apr 24 18:35:51 alpha last message repeated 2 times
Apr 24 18:36:01 alpha atalkd[212]: as_timer multiple interfaces, no seed
Apr 24 18:36:01 alpha atalkd[212]: as_timer can't configure ne1
Apr 24 18:36:01 alpha atalkd[212]: as_timer waiting for router
Apr 24 18:36:01 alpha atalkd[212]: ready 0/0/0
Apr 24 18:36:28 alpha afpd[227]: Can't register alpha:AFPServer@*
Apr 24 18:36:28 alpha afpd[227]: ASIP started on 192.168.1.2:548(1)
(1.4b2+asun2.1.4)
Apr 24 18:36:28 alpha afpd[227]: uam: uams_clrtxt.so loaded
Apr 24 18:36:28 alpha afpd[227]: uam: "Cleartxt Passwrd" available
Not knowing whether the messages referred to my configuration or the newly
created version, I rebooted...
Apr 24 18:47:44 alpha atalkd[212]: restart (1.4b2+asun2.1.4)
Apr 24 18:47:44 alpha atalkd: difaddr(0.0): Can't assign requested address
Apr 24 18:47:44 alpha last message repeated 2 times
Apr 24 18:47:45 alpha afpd[227]: main: atp_open: Can't assign requested
address
Apr 24 18:47:45 alpha afpd[227]: ASIP started on 192.168.1.2:548(1)
(1.4b2+asun2.1.4)
Apr 24 18:47:45 alpha afpd[227]: uam: uams_clrtxt.so loaded
Apr 24 18:47:45 alpha afpd[227]: uam: "Cleartxt Passwrd" available
*** plus a few more that appear on the console but not in the log file...
Net (0) not in net range (65280-65534).
AppleTalk not up! Check your syslog for reasons. Child died.
Apr 24 18:47:44 alpha atalkd: difaddr(0.0) Can't assign requested address.
...
So I changed to config to...
ne1 -phase 2 -net 1-2 -addr 1.1 -zone "printing"
rl0 -phase 2 -net 3-4 -addr 3.2
Following a reboot, the following messages were observed...
Apr 24 19:27:48 alpha atalkd[212]: restart (1.4b2+asun2.1.4)
Apr 24 19:27:50 alpha atalkd[212]: zip_getnetinfo for ne1
Apr 24 19:28:08 alpha last message repeated 2 times
Apr 24 19:28:18 alpha atalkd[212]: as_timer multiple interfaces, no seed
Apr 24 19:28:18 alpha atalkd[212]: as_timer can't configure ne1
Apr 24 19:28:18 alpha atalkd[212]: as_timer waiting for router
Apr 24 19:28:18 alpha atalkd[212]: ready 0/0/0
Apr 24 19:28:45 alpha afpd[227]: Can't register alpha:AFPServer@*
Apr 24 19:28:45 alpha afpd[227]: ASIP started on 192.168.1.2:548(1)
(1.4b2+asun2.1.4)
Apr 24 19:28:45 alpha afpd[227]: uam: uams_clrtxt.so loaded
Apr 24 19:28:45 alpha afpd[227]: uam: "Cleartxt Passwrd" available
And the atalkd.conf was changed again!
ne1 -phase 2 -net 1-2 -addr 1.1
rl0 -phase 2 -net 3-4 -addr 0.0
Gone has the zone name and now have the return of the bad address (0.0)
Even when I have removed the rl0 NIC and use the following in atalkd.conf...
ne1 -phase 2 -zone "printing"
Still do not get AppleTalk services visible (get a large number of error
messages) and the atalkd.conf file is changed to...
ne1 -phase 2 -net 0-65534 -addr 65280.210
The problems are:
(1) rl0 does not fully support hardware multicast (yet), its services are
not visible in the chooser. Will get updated driver when available.
(2) My zone names get clobbered/removed
(3) The substituted net ranges do not make sense - they are reserved
addresses.
(4) The address value for the second interface is incorrect (see error
message)
(5) To disable a NIC, it has to be physically removed from the computer.
(6) I do NOT need routing of AppleTalk services - seems to be close to
impossible to to set this configured when there are two interfaces.
Some background:
System = NetBSD/i386 1.4.2, 32MB RAM
Netatalk = 1.4b2+asun2.1.4-39_test (however the rewriting behaviour has
existed on previous versions)
ne1 = ne2000 NIC (DLink DF-200) - supports hardware multicast
rl0 = RealTek 8139 NIC (DLink DFE-530TX+)
IP(ne1) = 192.168.2.1
IP(rl0) = 192.168.1.2
Overall, what I am trying to do is to put Appletalk printers on a separate
non-routable network and get the workstations to use the spoolers. This is
so that the printers would not be visible in the chooser only the netatalk
spoolers would be.
But what is confusing is the self-modifying config files that exist in
netatalk. It makes it very hard to diagnose problems with configurations.
Any constructive suggestions would be appreciated.
Is there any way of disabling the self modifying atalkd.conf in netatalk?
--
Stephen Welker
