search

rdmark / netatalk-2.x

Netatalk is an Open-Source AFP file server for Linux, NetBSD, and Solaris, capable of serving AppleShare over AppleTalk and TCP/IP with multiple Macintosh or Apple II clients.
Other
52 stars 2 forks source link

TimeLord is not working with atalkd in router mode #39

Open NJRoadfan opened 1 year ago

NJRoadfan commented 1 year ago

Any attempts to use the tardis application on a client Macintosh results in a "ding" and the time is not synced with the server.

Client: Quadra 605 running System 7.1 and tardis 1.6. tardis 1.3 was also tested.

Server: netatalk-2.x tested on both a x86_64 VM and ARM RPi 400. Both are running the latest patches for Debian 11/bullseye.

NJRoadfan commented 1 year ago

Figured out the problem. The tardis extension doesn't seem to like working in an AppleTalk zone for some reason. Turning off atalkd's router functionality allows tardis to sync the clock.

rdmark commented 1 year ago

Huh, that's an unexpected limitation/bug. Too bad we don't have the source code for tardis to fix it.

And you're sure netatalk's timelord itself isn't to blame? Does a2boot work with zones (it is based on timelord code)?

NJRoadfan commented 1 year ago

a2boot works fine. Heck, when I boot my Apple IIgs over the network, its on a separate network number and zone. I did further testing using my Shiva Fastpath 5 as a router, and it fails there too. So that rules out atalkd as the source of the problem. I also tried out syncing the clock to the original TimeLord CDEV, and it isn't working either. I suspect it is a tardis bug at this point.

Running Wireshark, I'm not seeing any ATP packets from timelord or tardis over the network. Just normal NBP packets from Chooser while it is open. This seems like a really obvious bug, particularly if Timelord was ever used on a medium/large sized network.

rdmark commented 1 year ago

That's so strange, given that tardis/timelord was developed at the University of Melbourne which must certainly have had an appletalk network with significant complexity up and running at one point... Or maybe they had one timelord server per zone or something...?

NJRoadfan commented 1 year ago

The original TimeLord server for CAP is here: https://github.com/mabam/CAP/tree/master/contrib/Timelord

The code does handle NBP registration with zones.