-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Server Location Protocol (SLP) #1370
Comments
MacOS 9 supports SLP 2.0, which works with Netatalk 2.x out of the box. MacOS 8.5 and 8.6 shipped with SLP 1.0, which is not compatible with the later protocol. Copying the extension from an OS9 install works though. In 3.x, any addition of SLP would be to the I don't know why SLP would conflict with Zeroconf/mDNS as they use separate ports. |
I'm certain this is simply a bug in netatalk. |
One situation we have to deal with here is the fact that OpenSLP is an abandoned project (2.0.0 released in 2013). As a result, it's started getting dropped from various repositories. Notably Debian and Alpine (both in 2016). And on macOS, the homebrew package is Intel-only with no support for Apple Silicon. Just to mention a few. Fedora still distributes a package, however. One idea to entertain here would be to bundle OpenSLP with netatalk, like we do with WolfSSL. The license is BSD-3-clause, which is compatible with GPLv2 to my best understanding. This is the amount of code we would be dealing with:
Additionally, we would have to write Meson build scripts for it. Currently Autotools. |
Maybe contact the author @jcalcote about doing another release? There are commits from the past few years that haven't seen release. From the netatalk perspective, are there any users actually using clients that only support SLP? MacOS X 10.0 and 10.1 were rare out on the field, even back in the early 2000s. When 10.2 came out, pretty much everybody upgraded and didn't look back! As for MacOS 9, most folks are/were likely relying on AppleTalk for service location. I think the main reason why SLP was removed is that the original implementation was janky and hacked into |
This is about forward-porting SLP (a.k.a. srvloc a.k.a. Server Location Protocol) from 2.x to the main branch.
It should be integrated in a better way, ideally to allow Zeroconf and SLP to co-exist side by side. But if unfeasible, the build system should only allow building with one or the other enabled.
In 2.x, the current state is that you can configure and build with both service discovery protocols, but only one will actually function.
SLP was used for service discovery in OSX 10.0 and 10.1, and reportedly also supported in OS9.
The text was updated successfully, but these errors were encountered: