My MFP needs the proprietary HP-binary-plugin (e.g. hplip-3.22.4-plugin.run) to work correctly. I am using a network setup. (Printer: 192.168.1.233 on localnet and 10.0.0.29 on different network, Airsane: 192.168.1.234, IPP_Service_Host: 192.168.1.10)
the printers http service pages shows an WS-Discovery Service so we should have a WSD up and running.
But it seems to not register in MDNS/WSSD/ZEROCONF and so airscan is not able to detect it. I tested my normal setup with an avahi-reflector and also moved the printer to the same network segment as airscan. It made no difference.
while tcpdumping a hpaio:// scan (scanimage --test --verbose --progress) i was able to see the WSD XML the printer reported:
Hi, hope this is the right place for this prob.
My MFP needs the proprietary HP-binary-plugin (e.g. hplip-3.22.4-plugin.run) to work correctly. I am using a network setup. (
Printer: 192.168.1.233 on localnet and 10.0.0.29 on different network, Airsane: 192.168.1.234, IPP_Service_Host: 192.168.1.10
) the printers http service pages shows an WS-Discovery Service so we should have a WSD up and running. But it seems to not register in MDNS/WSSD/ZEROCONF and so airscan is not able to detect it. I tested my normal setup with an avahi-reflector and also moved the printer to the same network segment as airscan. It made no difference.while tcpdumping a
hpaio://
scan (scanimage --test --verbose --progress
) i was able to see the WSD XML the printer reported:And i was able to forge a curl post for wsdiscovery - So airscan stuff should work
avahi (thx to reflector) lists the printer on localnet and different net
airscan-discover -d
But airscan only seems to scan Printers reporting _ipp._tcp and _ipps._tcp, which is not ideal in my case. The printer does not provide ipp and so the ipp service address is provided via DrPsychick docker-cups-airprint logfile airscan-discover -d (valid 3weeks) pcap success scanning hpaio (valid 2weeks)