Skip to main content ↑ ↓
Topic: HPLIP and SNMP (Read 461 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

HPLIP and SNMP

My HP Color Laserjet Printer M551 has been sitting nicely in my kitchen as a workhorse for almost 10 years now.  With the crash of my workstation I can't get it to fully work with cups or hplip.  Even when I give it the exact IP address on my 10.0.0.0 network, it can't find it.

I tried hplip and it also  can't find the printer.

I can pint it and see it in palemoon although it has an old ssl cert that doesn't work in chrom.

Avahi is up and running in openrc and it is actually started by cupsd, but SNMP does not set up correctly from the packages.
sudo /etc/init.d/snmpd start
snmpd             | * snmpd requires an /etc/snmp/snmpd.conf configuration file
snmpd             | * ERROR: snmpd failed to start

I don't even know what snmpd does exactly,  but hplid claims to need it ti id the printer under bonjour protocals.

Re: HPLIP and SNMP

Reply #2 –
Quote from: nous – on
https://wiki.archlinux.org/title/CUPS
http://localhost:631/

it is not showing even when I point its nose right at the damn IP address.

Evidently, it is too stupid to understand basic IP networking without Ahavi

And this thing is clusterf*
https://wiki.archlinux.org/title/Avahi#Hostname_resolution

Code: [Select]
Using Avahi
Hostname resolution

Avahi provides local hostname resolution using a "hostname.local" naming scheme. To enable it, install the nss-mdns package and start/enable avahi-daemon.service.

Then, edit the file /etc/nsswitch.conf and change the hosts line to include mdns_minimal [NOTFOUND=return] before resolve and dns:

hosts: mymachines mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] files myhostname dns

Note:

    If you experience slowdowns in resolving .local hosts (or you do not want to use IPv6) try to use mdns4_minimal and mdns4 instead of mdns_minimal and mdns respectively.
    The line above makes nss-mdns authoritative for the .local domain, unless your unicast DNS server responds to SOA queries for the top level local name, or if the request has more than two labels. See nss-mdns activation notes.
        systemd-resolved responds to these queries even if its mDNS support is disabled. See #systemd-resolved prevents nss-mdns from working.
        More info about nss configuration can be found on nss-mymachines(8) and in Avahi docs.

I don't even know what this means and I only has an MS in Comp Sci with lots of Networking credits.

What can possibly stop it from finding an IP address that I explicitly give it.


 

Re: HPLIP and SNMP

Reply #3 –
Can an nmap scan find the printer ?
Can you telnet to it ?
Can you access the printers embedded webserver ?

If the answer to all is no then maybe it's an issue with the printers network setup. I'd be checking the printers network settings via the built in display. Also directly connecting the printer by USB and then letting hp-setup work it's magic. I'd be considering a factory reset on the printer as well.

If you can't get Bonjour (mDNS) and SNMP to work maybe try Internet Printing Protocol (IPP).

Re: HPLIP and SNMP

Reply #4 –
Quote from: gripped – on
Can an nmap scan find the printer ?
Can you telnet to it ?
Can you access the printers embedded webserver ?

If the answer to all is no then maybe it's an issue with the printers network setup. I'd be checking the printers network settings via the built in display. Also directly connecting the printer by USB and then letting hp-setup work it's magic. I'd be considering a factory reset on the printer as well.

If you can't get Bonjour (mDNS) and SNMP to work maybe try Internet Printing Protocol (IPP).

all the ip stuff works