On 3/30/23 04:47, Jeremy Ardley wrote:

On 30/3/23 16:32, gene heskett wrote:
Greetings all;

hosts based local 192.158.xx.yy network.

cups at localhost:631 on any buster machine sees my printers just fine, and the buster machines can print to them.

Those machines running bullseye aren't allowed. can't see my printers unless I send ff to the ipv4 address of this machine.

This machine with the printers attached to its usb ports is an uptodate bullseye.

One scanner/printer also has an ipv4 address on the local net, but that is not found by the bullseye machines either.

What is preventing a bullseye machine from seeing my printers?

Thank You.

Cheers, Gene Heskett.


Debian 10 and 11 both use the Common Unix Printing System (CUPS) for printer management. CUPS comes with a tool called "Avahi" that allows for automatic discovery of network printers that support the Bonjour or Zeroconf protocols.

When a printer that supports Bonjour/Zeroconf is connected to the network, it announces itself to the network using Multicast Domain Name System (mDNS) protocol. The Avahi daemon running on Debian listens for these announcements and creates a local service for each printer discovered. The printer should then be automatically available for use in CUPS.

In your case see whether avahi is running, and if not, enable it.

cups-browsd has been removed as it insists on setting up broken drivers for my brother printers, they run to their full capabilities using the brother drivers. I also tend to remove avahi because it insists on a 169.xx.xx.zz routing address to the world if it cannot find a working dhcpd on the system, which a hosts based network does not need. dns queries are sent to dd-wrt running on the router, which in turn sends them on to my isp's dns server. dd-wrt returns that result to what ever asked for it, usually in under 20 milliseconds.

I have asked on the cups list, but I've known Mike since he was a starving college student in the later '80's, both of us on delphi dialup at the time, and my messages to that list have been redirected to /dev/null for around 20 years now.

I figure this is a common enough problem that someone has solved it. cups at localhost:631 can't see the printers. coyote.coyote.den:631 can't see a thing, but 182,168.71.3:631 works. What is the difference between buster which works a treat, and bullseye which doesn't?

I just went thru the cups docs on printer sharing, did everything suggested, both to this server and to one of the bullseye clients, no change could be detected.

I need a fresh outlook, I'm obviously missing something.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Reply via email to