On 01/09/2017 02:33 AM, Per Jessen wrote:
As I mentioned above, I don't think that's supported anymore.
You suggested broadcast is no longer used with cups, yet it clearly is.
+1 The operative line in the config file is Browser on Go grep to see if you have it.
I know when I try to enable it in Yast, I get an error: "Either BrowseAddress @LOCAL or BrowseAddress none is supported for cups-browsed."
I'm not using cups-browsed - still, BrowseAddress @LOCAL is what came with the installation, but I don't see how that could work with IPv6 multicast.
As James points out, multicast is not broadcast. I started this thread by pointing out what seems to be broadcast. When I grepped my config file I did find the "Broadcast on" line. I commented it out and now don't have that broadcast flood, but my mobile devices can still address my CUPS server. I'm running CUPS server 1.5.4-21.9.1 I may have initially, years and years ago, set it up with YAST, but subsequently I've always maintained it either via the web interface or via editing the config file. I'd strongly suggest using the web interface over the Yast! VERY STRONGLY! Perhaps at http://127.0.0.1:631/ -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org