| 1 |
On Tuesday, 30 June 2020 04:51:03 BST Alan Grimes wrote: |
| 2 |
> I was sitting smug and happy thinking I could print from either of my |
| 3 |
> computers to the laserjet printer downstairs. So therefore when I need |
| 4 |
> to RMA my mobo and need to print out the forms, it doesn't work. |
| 5 |
> |
| 6 |
> The sack of crap seems to think it can connect to the printer using: |
| 7 |
> |
| 8 |
> Connection: |
| 9 |
> dnssd://HP%20Color%20LaserJet%20Pro%20M453-4%20%5B804AC2%5D._ipp._tcp.local/ |
| 10 |
> ?uuid=beff9c81-55ea-548f-5867-4d44f4da191e |
| 11 |
|
| 12 |
You must have enabled DNSSD (DNS Service Discovery) on your systems, whereby |
| 13 |
DNS packets are sent/received for the purpose of scanning your LAN and |
| 14 |
discovering various network services, including network printers, media |
| 15 |
servers, torrents, etc. |
| 16 |
|
| 17 |
DNSSD is also known as zeroconf and from what I understand was derived from |
| 18 |
Apple's Rendezvous/Bonjour. |
| 19 |
|
| 20 |
The Linux equivalent is Avahi (for server) and nss-mdns (for clients), but |
| 21 |
systemd had to re-engineer everything into its own stack as 'systemd- |
| 22 |
resolved', which uses the MSWindows preferred LLMNR. |
| 23 |
|
| 24 |
This is all great if you trust the devices in your LAN not to spoof names and |
| 25 |
intercept your communications, or if LAN side network services pop-up and down |
| 26 |
all the time and you want to have them autoconfigured for use by your LAN |
| 27 |
clients. |
| 28 |
|
| 29 |
|
| 30 |
> Why in god's name does CPUS think that would work, ofcourse I'm going to |
| 31 |
> get: in my error log.... |
| 32 |
> |
| 33 |
> E [29/Jun/2020:18:39:40 -0400] [CGI] Unable to resolve |
| 34 |
> \"dnssd://HP%20Color%20LaserJet%20Pro%20M453-4%20%5B804AC2%5D._ipp._tcp.loca |
| 35 |
> l/?uuid=beff9c81-55ea-548f-5867-4d44f4da191e|HP Color LaserJet Pro> |
| 36 |
> |
| 37 |
> |
| 38 |
> Naturally, there is no other way to configure this crap with the web |
| 39 |
> interface, there are some on-line manpages but they're written in |
| 40 |
> moonspeak. =( |
| 41 |
|
| 42 |
You do not need network services autoconfiguration, which is is what the |
| 43 |
dnssd:// URI is trying to achieve, unless printers are added and removed in |
| 44 |
your LAN on a regular basis with different IP addresses, different client PCs |
| 45 |
and devices are connected and disconnected all the time and you expect them |
| 46 |
all to discover network services automatically. |
| 47 |
|
| 48 |
In your case, cups is trying to do what you have specified, by enabling of |
| 49 |
failing to disable a particular USE flag. If you emerged net-print/cups and |
| 50 |
net-print/cups-filters with USE="zeroconf" enabled you'll get what you got. |
| 51 |
If you disable it you will arrive at a client-printer combo where you have to |
| 52 |
manually configure the connection and driver, at least on the client side. |
| 53 |
|
| 54 |
Since this is an HP printer, I think you'll need the hplip driver, so check |
| 55 |
you have this emerged: |
| 56 |
|
| 57 |
https://wiki.gentoo.org/wiki/HPLIP |
| 58 |
|
| 59 |
Finally, configure your clients to use the printer: |
| 60 |
|
| 61 |
https://wiki.gentoo.org/wiki/Printing |
| 62 |
|
| 63 |
|
| 64 |
TL;DR: Stop the cupsd service on your PC. Open and edit "/etc/cups/ |
| 65 |
printers.conf" file, changing the DeviceURI: |
| 66 |
|
| 67 |
DeviceURI ipp://12.345.678.9/ipp/print |
| 68 |
|
| 69 |
Where '12.345.678.9' is the statically configured IP address of your printer |
| 70 |
on your LAN, the '.../ipp/' and '.../print' may or may not be needed - try and |
| 71 |
see what you get. |
| 72 |
|
| 73 |
Restart you cupsd and try to print. |
| 74 |
|
| 75 |
Others who use this printer may chime in with specifics. |
Archives