[opensuse] CUPS is doing something strange
I see this repeating in my logs every minute, sometimes more often 2017-01-08T12:50:49-05:00 2017 SYSLOG[0]: message repeated 14 times: [ [Host 192.168.2.1] UDP 192.168.2.14,631 --> 192.168.2.255,631 DENY: Inbound or outbound access request ] 2017-01-08T12:51:16-05:00 2017 SYSLOG[0]: [Host 192.168.2.1] UDP 192.168.2.14,631 --> 192.168.2.255,631 DENY: Inbound or outbound access request 192.168.2.1 is my firewall 192.168.2.14 is my host running CUPS There is no problem printing from the host. The printer is at .32 and while I see the occasional 2017-01-07T22:32:06-05:00 2017 SYSLOG[0]: [Host 192.168.2.1] UDP 192.168.2.32,138 --> 255.255.255.255,138 DENY: Inbound or outbound access request The CUPSd on .14 should be listening to other devices on the network, notably portable devices, sending print requests, but I don't see why it should be doing outbound like that. However my knowledge on CUPS internals is limited. I'm just thinking of what a (passive) server would be doing. That I can't account for it doesn't bother me so much. Its a brother laser printer, a HL5170DM, and has never given me any technical problems. This is not a showstoper of a problem, but I do wonder why there is all this network traffic and if I've possibly made a configuration error that is causing it and that the configuration error is somehow limiting or wasteful in other ways. -- 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
Anton Aylward wrote:
I see this repeating in my logs every minute, sometimes more often
2017-01-08T12:50:49-05:00 2017 SYSLOG[0]: message repeated 14 times: [ [Host 192.168.2.1] UDP 192.168.2.14,631 --> 192.168.2.255,631 DENY: Inbound or outbound access request ] 2017-01-08T12:51:16-05:00 2017 SYSLOG[0]: [Host 192.168.2.1] UDP 192.168.2.14,631 --> 192.168.2.255,631 DENY: Inbound or outbound access request
192.168.2.1 is my firewall 192.168.2.14 is my host running CUPS
There is no problem printing from the host. The printer is at .32 and while I see the occasional
2017-01-07T22:32:06-05:00 2017 SYSLOG[0]: [Host 192.168.2.1] UDP 192.168.2.32,138 --> 255.255.255.255,138 DENY: Inbound or outbound access request
The CUPSd on .14 should be listening to other devices on the network, notably portable devices, sending print requests, but I don't see why it should be doing outbound like that.
It's a broadcast, telling everyone "hello I'm here". Clients will be listening for that. -- Per Jessen, Zürich (0.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/08/2017 10:06 AM, Per Jessen wrote:
Anton Aylward wrote:
The CUPSd on .14 should be listening to other devices on the network, notably portable devices, sending print requests, but I don't see why it should be doing outbound like that.
It's a broadcast, telling everyone "hello I'm here". Clients will be listening for that.
Ung! How Un-UNIX-like! That's the sort of thing we expect from M$ and Apple with their closed networks running not-tcp/ip from years back. Imagine if all the servers we grew up with in the *NIX world were like that, every SMTP server, every HTTP server, broadcast "I'm Here" over the Internet! Heck, it bad enough with the routers doing that with the routing protocols! What's the world coming to? -- 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
* Anton Aylward
On 01/08/2017 10:06 AM, Per Jessen wrote:
Anton Aylward wrote:
The CUPSd on .14 should be listening to other devices on the network, notably portable devices, sending print requests, but I don't see why it should be doing outbound like that.
It's a broadcast, telling everyone "hello I'm here". Clients will be listening for that.
Ung!
How Un-UNIX-like! That's the sort of thing we expect from M$ and Apple with their closed networks running not-tcp/ip from years back.
Imagine if all the servers we grew up with in the *NIX world were like that, every SMTP server, every HTTP server, broadcast "I'm Here" over the Internet! Heck, it bad enough with the routers doing that with the routing protocols!
What's the world coming to?
you maybe using software meant for linux (drivers) but built by people *assuming* most usage from windoz, so the drivers reflect the windoz way in a linux maner :) isn't it a windoz manner to broadcast a devices availability rather than just acknowledging is existance when asked? for the most part, doesn't bluetooth do the same in order to pair? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 08 Jan 2017 10:44:47 -0500, Anton Aylward wrote:
On 01/08/2017 10:06 AM, Per Jessen wrote:
Anton Aylward wrote:
The CUPSd on .14 should be listening to other devices on the network, notably portable devices, sending print requests, but I don't see why it should be doing outbound like that.
It's a broadcast, telling everyone "hello I'm here". Clients will be listening for that.
Ung!
How Un-UNIX-like! That's the sort of thing we expect from M$ and Apple with their closed networks running not-tcp/ip from years back.
CUPS has been doing it for years, it's unrelated to Apple being the CUPS maintainer. /Per -- Posted with pan 0.139 from openSUSE Leap42.2 office34: Cyrix 486DX2/66MHz, 4096Mb RAM, #9 GXE -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 08 Jan 2017 15:57:31 +0000, Per Jessen wrote:
On Sun, 08 Jan 2017 10:44:47 -0500, Anton Aylward wrote:
On 01/08/2017 10:06 AM, Per Jessen wrote:
Anton Aylward wrote:
The CUPSd on .14 should be listening to other devices on the network, notably portable devices, sending print requests, but I don't see why it should be doing outbound like that.
It's a broadcast, telling everyone "hello I'm here". Clients will be listening for that.
Ung!
How Un-UNIX-like! That's the sort of thing we expect from M$ and Apple with their closed networks running not-tcp/ip from years back.
CUPS has been doing it for years, it's unrelated to Apple being the CUPS maintainer.
By the way, I think it's configurable - either use the broadcast or have all clients poll the server. The latter requires individual configuration on each client. It used to be easier to rely on the broadcast because it needed no local config, but now where each client has to be enabled any way, maybe it doesn't matter much. /Per -- Posted with pan 0.139 from openSUSE Leap42.2 office34: Cyrix 486DX2/66MHz, 4096Mb RAM, #9 GXE -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/08/2017 10:44 AM, Anton Aylward wrote:
On 01/08/2017 10:06 AM, Per Jessen wrote:
The CUPSd on .14 should be listening to other devices on the network, notably portable devices, sending print requests, but I don't see why it should be doing outbound like that. It's a broadcast, telling everyone "hello I'm here". Clients will be
Anton Aylward wrote: listening for that. Ung!
How Un-UNIX-like! That's the sort of thing we expect from M$ and Apple with their closed networks running not-tcp/ip from years back.
Imagine if all the servers we grew up with in the *NIX world were like that, every SMTP server, every HTTP server, broadcast "I'm Here" over the Internet! Heck, it bad enough with the routers doing that with the routing protocols!
What's the world coming to?
My understanding was that broadcast were no longer used with CUPS. The intent of broadcasts was to make the computers on the network "aware" of the printers, so the users could simply click on a printer to select it. For that sort of thing, broadcasts or multicasts are necessary. I believe CUPS can be configured for multicast and, in fact, it's mandatory for IPv6, where there is no such thing as a broadcast. All those web sites won't be able to use broadcasts, as broadcasts are not normally forwarded by routers. Multicasts may be, provided the routers are configured to do that. There are many other things that use broadcasts, such as arp and the networks wouldn't be usable without them or mulitcasts. On IPv6, there is no such thing as a broadcasts, but a long list of multicast addresses that limit the devices that are disturb by such traffic. That is, with a broadcast, every device has to receive it and then determine if it has to do anything. With multicast, any packet that a device isn't interested in is discarded by the NIC and never goes on to bother the device. There are multicast addresses for a lot of things, such as all nodes, all routers, all OSPF routers and more. Also, there were some older routing protocols, such as RIP that used broadcast, but more modern ones, such as OSPF & EIGRP use multicast on both IPv4 & IPv6. Bottom line, there is still a need for broadcasts or, preferably, mulitcasts. BTW, on IPv6, there's something called a solicited node multicast, where the right most 24 bits of the multicast address correspond to the 24 bits of the IPv6 address. This is used for things like neighbour solicitation, to minimize disturbing other than the desired target. With 24 bits, the chances of an unintended target receiving the packet are less than 1 in 16 million (2^24). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 08 Jan 2017 11:32:11 -0500, James Knott wrote:
On 01/08/2017 10:44 AM, Anton Aylward wrote:
On 01/08/2017 10:06 AM, Per Jessen wrote:
The CUPSd on .14 should be listening to other devices on the network, notably portable devices, sending print requests, but I don't see why it should be doing outbound like that. It's a broadcast, telling everyone "hello I'm here". Clients will be
Anton Aylward wrote: listening for that. Ung!
How Un-UNIX-like! That's the sort of thing we expect from M$ and Apple with their closed networks running not-tcp/ip from years back.
Imagine if all the servers we grew up with in the *NIX world were like that, every SMTP server, every HTTP server, broadcast "I'm Here" over the Internet! Heck, it bad enough with the routers doing that with the routing protocols!
What's the world coming to?
My understanding was that broadcast were no longer used with CUPS. The intent of broadcasts was to make the computers on the network "aware" of the printers, so the users could simply click on a printer to select it. For that sort of thing, broadcasts or multicasts are necessary. I believe CUPS can be configured for multicast and, in fact, it's mandatory for IPv6, where there is no such thing as a broadcast.
Interesting point. I can't figure out how to configure cups for that - I tried using an ipv6 address with "BrowseAddress", but cupsd (1.5.4) didn't accept it. With or without []. /Per -- Posted with pan pan 0.139 from openSUSE Leap42.2 office34: Cyrix 486DX2/66MHz, 4096Mb RAM, #9 GXE -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/08/2017 12:25 PM, Per Jessen wrote:
intent of broadcasts was to make the computers on the network "aware" of the printers, so the users could simply click on a printer to select it. For that sort of thing, broadcasts or multicasts are necessary. I believe CUPS can be configured for multicast and, in fact, it's mandatory for IPv6, where there is no such thing as a broadcast. Interesting point. I can't figure out how to configure cups for that - I
My understanding was that broadcast were no longer used with CUPS. The tried using an ipv6 address with "BrowseAddress", but cupsd (1.5.4) didn't accept it. With or without [].
As I mentioned above, I don't think that's supported anymore. 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." Perhaps someone with more CUPS experience can elaborate. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-08 21:27, James Knott wrote:
On 01/08/2017 12:25 PM, Per Jessen wrote:
intent of broadcasts was to make the computers on the network "aware" of the printers, so the users could simply click on a printer to select it. For that sort of thing, broadcasts or multicasts are necessary. I believe CUPS can be configured for multicast and, in fact, it's mandatory for IPv6, where there is no such thing as a broadcast. Interesting point. I can't figure out how to configure cups for that - I
My understanding was that broadcast were no longer used with CUPS. The tried using an ipv6 address with "BrowseAddress", but cupsd (1.5.4) didn't accept it. With or without [].
As I mentioned above, I don't think that's supported anymore. 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."
Perhaps someone with more CUPS experience can elaborate.
This paragraph in the release notes may hint at the cause: The network printer discovery protocol has changed. The native method to discover network printers is now based on DNS Service discovery (DNS-SD, that is, via Avahi). The cups-browsed service from the cups-filters package can be used to bridge old and new protocols. Both cupsd and cups-browsed need to run to make "legacy" clients discover printers (that includes LibreOffice and KDE). -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote: > On 2017-01-08 21:27, James Knott wrote: >> On 01/08/2017 12:25 PM, Per Jessen wrote: >>>> My understanding was that broadcast were no longer used with CUPS. >>>> The >>>>> intent of broadcasts was to make the computers on the network >>>>> "aware" of the printers, so the users could simply click on a >>>>> printer to select it. >>>>> For that sort of thing, broadcasts or multicasts are necessary. >>>>> I >>>>> believe CUPS can be configured for multicast and, in fact, it's >>>>> mandatory for IPv6, where there is no such thing as a broadcast. >>> Interesting point. I can't figure out how to configure cups for that >>> - I tried using an ipv6 address with "BrowseAddress", but cupsd >>> (1.5.4) didn't accept it. With or without []. >> >> As I mentioned above, I don't think that's supported anymore. 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." >> >> Perhaps someone with more CUPS experience can elaborate. > > This paragraph in the release notes may hint at the cause: > > The network printer discovery protocol has changed. The native method > to discover network printers is now based on DNS Service discovery > (DNS-SD, that is, via Avahi). The cups-browsed service from the > cups-filters package can be used to bridge old and new protocols. Both > cupsd and cups-browsed need to run to make "legacy" clients discover > printers (that includes LibreOffice and KDE). I guess this is the situation as seen from the server side - so far, printer discovery works fine from my leap422 clients. Our print server is running 12.3, cups 1.5.4. -- Per Jessen, Zürich (-2.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote: > On 01/08/2017 12:25 PM, Per Jessen wrote: >>> My understanding was that broadcast were no longer used with CUPS. >>> The >>> > intent of broadcasts was to make the computers on the network >>> > "aware" of the printers, so the users could simply click on a >>> > printer to select it. >>> > For that sort of thing, broadcasts or multicasts are necessary. >>> > I believe CUPS can be configured for multicast and, in fact, it's >>> > mandatory for IPv6, where there is no such thing as a broadcast. >> Interesting point. I can't figure out how to configure cups for that >> - I tried using an ipv6 address with "BrowseAddress", but cupsd >> (1.5.4) didn't accept it. With or without []. > > 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. > 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. -- Per Jessen, Zürich (-2.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/09/2017 02:33 AM, Per Jessen wrote: > James Knott wrote: > >> On 01/08/2017 12:25 PM, Per Jessen wrote: >>>> My understanding was that broadcast were no longer used with CUPS. >>>> The >>>>> intent of broadcasts was to make the computers on the network >>>>> "aware" of the printers, so the users could simply click on a >>>>> printer to select it. >>>>> For that sort of thing, broadcasts or multicasts are necessary. >>>>> I believe CUPS can be configured for multicast and, in fact, it's >>>>> mandatory for IPv6, where there is no such thing as a broadcast. >>> Interesting point. I can't figure out how to configure cups for that >>> - I tried using an ipv6 address with "BrowseAddress", but cupsd >>> (1.5.4) didn't accept it. With or without []. >> 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. > >> 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." According to a few articles I've read, it's no longer supported. Here's one: "First, existing versions of CUPS allow client machines to browse for printers accessible on the network. In this system, printers announce their availability using short messages sent on UDP port 631. Mac OS X, however, uses DNS Service Discovery (DNS-SD) to locate network printers instead, a feature introduced with CUPS 1.3 in 2007. CUPS 1.6 will drop the UDP-based CUPS Browsing feature, and make DNS-SD the only method for "automatic" network printer discovery." https://lwn.net/Articles/485617/ Also, I left Wireshark running all night, watching for broadcasts. All I saw was my notebook's DHCP requests and something from my Android phone when I shut it down for the night. > 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. > > There are a few things that were broadcast on IPv4, but use multicast on IPv6. No big deal. The closest multicast to broacasts would be an all nodes multicast. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/09/2017 06:18 AM, James Knott wrote:
Also, I left Wireshark running all night, watching for broadcasts. All I saw was my notebook's DHCP requests and something from my Android
That was with IP broadcast. If I go with Ethernet broadcasts, I also see ARP requests and SMB announcements, but still no CUPS. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/09/2017 02:33 AM, Per Jessen wrote:
James Knott wrote:
On 01/08/2017 12:25 PM, Per Jessen wrote:
intent of broadcasts was to make the computers on the network "aware" of the printers, so the users could simply click on a printer to select it. For that sort of thing, broadcasts or multicasts are necessary. I believe CUPS can be configured for multicast and, in fact, it's mandatory for IPv6, where there is no such thing as a broadcast. Interesting point. I can't figure out how to configure cups for
My understanding was that broadcast were no longer used with CUPS. The that - I tried using an ipv6 address with "BrowseAddress", but cupsd (1.5.4) didn't accept it. With or without []. 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.
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."
According to a few articles I've read, it's no longer supported.
Well, despite those it works just fine. Has done since we moved the print server to openSUSE 12.3. Even with newer clients on Leap42x.
Here's one:
"First, existing versions of CUPS allow client machines to browse for printers accessible on the network. In this system, printers announce their availability using short messages sent on UDP port 631. Mac OS X, however, uses DNS Service Discovery (DNS-SD) to locate network printers instead, a feature introduced with CUPS 1.3 in 2007. CUPS 1.6 will drop the UDP-based CUPS Browsing feature, and make DNS-SD the only method for "automatic" network printer discovery."
I though I'd already mentioned it, the server is running cups 1.5.4. I have seen the article above too, and I do expect some changes when the print server moves to 1.6.
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.
There are a few things that were broadcast on IPv4, but use multicast on IPv6. No big deal. The closest multicast to broacasts would be an all nodes multicast.
Do you have a suggestion on how to make cups 1.5.x work on IPv6? It seems to me it ought to work, I just can't figure out how. -- Per Jessen, Zürich (1.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/09/2017 07:54 AM, Per Jessen wrote:
Here's one:
"First, existing versions of CUPS allow client machines to browse for printers accessible on the network. In this system, printers announce their availability using short messages sent on UDP port 631. Mac OS X, however, uses DNS Service Discovery (DNS-SD) to locate network printers instead, a feature introduced with CUPS 1.3 in 2007. CUPS 1.6 will drop the UDP-based CUPS Browsing feature, and make DNS-SD the only method for "automatic" network printer discovery." I though I'd already mentioned it, the server is running cups 1.5.4. I have seen the article above too, and I do expect some changes when the print server moves to 1.6.
Yep, you'll lose the broadcasts.
Do you have a suggestion on how to make cups 1.5.x work on IPv6? It seems to me it ought to work, I just can't figure out how.
No I don't. The version included with 42.2 has no problem with IPv6. When I watch with Wireshark, I see all the CUPS traffic using IPv6. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/09/2017 07:54 AM, Per Jessen wrote:
Here's one:
"First, existing versions of CUPS allow client machines to browse for printers accessible on the network. In this system, printers announce their availability using short messages sent on UDP port 631. Mac OS X, however, uses DNS Service Discovery (DNS-SD) to locate network printers instead, a feature introduced with CUPS 1.3 in 2007. CUPS 1.6 will drop the UDP-based CUPS Browsing feature, and make DNS-SD the only method for "automatic" network printer discovery." I though I'd already mentioned it, the server is running cups 1.5.4. I have seen the article above too, and I do expect some changes when the print server moves to 1.6.
Yep, you'll lose the broadcasts.
Do you have a suggestion on how to make cups 1.5.x work on IPv6? It seems to me it ought to work, I just can't figure out how.
No I don't. The version included with 42.2 has no problem with IPv6. When I watch with Wireshark, I see all the CUPS traffic using IPv6.
Printing works fine on IPv6, it's only the printer discovery that doesn't. Anyway, I was just curious, I'm perfectly happy with IPv4 for printer discovery. -- Per Jessen, Zürich (1.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/09/2017 06:18 AM, James Knott wrote:
"... CUPS 1.6 will drop the UDP-based CUPS Browsing feature, and make DNS-SD the only method for "automatic" network printer discovery."
Per and I are running 1.5.4 -- 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
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
Anton Aylward wrote:
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.
It's actually "Browsing", and yes it is enabled.
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.
Right.
When I grepped my config file I did find the "Broadcast on" line.
Were you looking in /etc/cups/cupsd.conf? I don't have any such line in mine, nor does the man page mention such a setting.
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'm running 1.5.4-5.11.1. I can't imagine any major differences, it's the same release.
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!
For managing printers, sure. For editing the config file, I prefer vi. Regardless, the web gui does not help me getting it to work on IPv6.
Perhaps at http://127.0.0.1:631/
Mine's at https://printserver.example.com:631, but that's irrelevant. -- Per Jessen, Zürich (0.9°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/09/2017 08:07 AM, Per Jessen wrote:
When I grepped my config file I did find the "Broadcast on" line. Were you looking in /etc/cups/cupsd.conf? I don't have any such line in mine, nor does the man page mention such a setting.
I commented it out and now don't have that broadcast flood, but my mobile devices can still address my CUPS server.
The first few lines of that file, as you mention, are now: ----------------------------------- SystemGroup sys root # Allow remote access Port 631 Listen /var/run/cups/cups.sock # Enable printer sharing and shared printers. Browsing off # Browsing On # BrowseOrder allow,deny # BrowseAllow all # BrowseRemoteProtocols CUPS # BrowseAddress @LOCAL # BrowseLocalProtocols CUPS DefaultAuthType Basic WebInterface Yes ----------------------------------- Before editing browsing was on and all the other browser lines were enabled.
I'm running CUPS server 1.5.4-21.9.1 I'm running 1.5.4-5.11.1. I can't imagine any major differences, it's the same release.
:-)
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! For managing printers, sure. For editing the config file, I prefer vi. Regardless, the web gui does not help me getting it to work on IPv6.
I presume you have a like something like the "listen" but for an IPV6 address? I wonder if the software is smart enough to interpret "localhost" BOTH ways? So a statement like Listen localhost:631 would apply for both IPv4 and IPv6. it depends, I suppose, on how you /etc/hosts is set up. Some idiots, I've learnt, actually delete the 'localhost' entry from there!
Perhaps at http://127.0.0.1:631/ Mine's at https://printserver.example.com:631, but that's irrelevant.
Not 'irrelevant' but "Context is Everything" :-) -- 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
Anton Aylward wrote:
Before editing browsing was on and all the other browser lines were enabled.
Okay, we're on the same page.
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! For managing printers, sure. For editing the config file, I prefer vi. Regardless, the web gui does not help me getting it to work on IPv6.
I presume you have a like something like the "listen" but for an IPV6 address?
On the client? Let me see - Listen localhost:631 The cups-browse daemon doesn't have much config at all.
I wonder if the software is smart enough to interpret "localhost" BOTH ways? So a statement like
Listen localhost:631
would apply for both IPv4 and IPv6.
I'm sure it will come up with both 127.0.0.1 and ::1, but it doesn't matter, no cupsd broadcast can reach localhost. The question is - afaict - how do I make my cups server send out printer announcements on an IPv6 multicast address? I'll probably move towards a dns-sd setup anyway, but the question is intrigueing. -- Per Jessen, Zürich (0.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-09 13:49, Anton Aylward wrote:
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!
My recommendation is to use YaST the first time, for installation, because it may suggest to install missing rpms, configure the firewall, activate services, etc, then use the web interface for all maintenance. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 01/09/2017 08:33 AM, Carlos E. R. wrote:
On 2017-01-09 13:49, Anton Aylward wrote:
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!
My recommendation is to use YaST the first time, for installation, because it may suggest to install missing rpms, configure the firewall, activate services, etc, then use the web interface for all maintenance.
Yes, indeed! For that, for consistency checking and all, YaST is VERY good. -- 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
Per Jessen wrote: > James Knott wrote: > >> On 01/08/2017 12:25 PM, Per Jessen wrote: >>>> My understanding was that broadcast were no longer used with CUPS. >>>> The >>>> > intent of broadcasts was to make the computers on the network >>>> > "aware" of the printers, so the users could simply click on a >>>> > printer to select it. >>>> > For that sort of thing, broadcasts or multicasts are necessary. >>>> > I believe CUPS can be configured for multicast and, in fact, >>>> > it's >>>> > mandatory for IPv6, where there is no such thing as a broadcast. >>> Interesting point. I can't figure out how to configure cups for that >>> - I tried using an ipv6 address with "BrowseAddress", but cupsd >>> (1.5.4) didn't accept it. With or without []. >> >> 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. > >> 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. On my two leap42x clients, I see cups-browsed running and printers are clearly discovered by way of the ipv4 cups broadcast from the print server. -- Per Jessen, Zürich (0.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Anton Aylward
-
Carlos E. R.
-
James Knott
-
Patrick Shanahan
-
Per Jessen