Bug#807427: sane-utils: Can not provide access to hplip scanner over network
On Mon 07 Aug 2017 at 11:06:45 +0200, martin f krafft wrote:
> Hey Brian,
>
> Thanks for looking into this and providing me the impetus to check
> the situation out again.
Thank you for doing this. As it turns out it seems our experiences are
quite different.
My setup:
On the sid server: an access list in saned.conf with only 192.168.7.20
in it. dll.conf is empty.
On the client: net.conf has the server IP 192.168.7.66 and net is
uncommented in dll.conf.
libsane and sane-utils on server and client.
The server log on 192.168.7.66 after 'scanimage -L' on the client:
systemd[1]: Started Scanner Service (192.168.7.20:43427).
saned[2103]: saned (AF-indep+IPv6+systemd) from sane-backends 1.0.25 starting up
saned[2103]: check_host: access by remote host: ::ffff:192.168.7.20
saned[2103]: init: access granted to brian@::ffff:192.168.7.20
saned[2103]: [sanei_debug] Setting debug level of dll to 255.
saned[2103]: [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25
saned[2103]: [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d'
saned[2103]: [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d'
saned[2103]: [dll] sane_init/read_dlld: considering /etc/sane.d/dll.d/hplip
saned[2103]: [dll] sane_init/read_config: reading dll.d/hplip
saned[2103]: [dll] add_backend: adding backend `hpaio'
saned[2103]: [dll] sane_init/read_dlld: done.
saned[2103]: [dll] sane_init/read_config: reading dll.conf
saned[2103]: [dll] add_backend: adding backend `net'
saned[2103]: [dll] sane_get_devices
saned[2103]: [dll] load: searching backend `net' in `/usr/lib/i386-linux-gnu/sane:/usr/lib/sane'
saned[2103]: [dll] load: trying to load `/usr/lib/i386-linux-gnu/sane/libsane-net.so.1'
saned[2103]: [dll] load: dlopen()ing `/usr/lib/i386-linux-gnu/sane/libsane-net.so.1'
saned[2103]: [dll] init: initializing backend `net'
saned[2103]: [dll] init: backend `net' is version 1.0.25
saned[2103]: [dll] load: searching backend `hpaio' in `/usr/lib/i386-linux-gnu/sane:/usr/lib/sane'
saned[2103]: [dll] load: trying to load `/usr/lib/i386-linux-gnu/sane/libsane-hpaio.so.1'
saned[2103]: [dll] load: dlopen()ing `/usr/lib/i386-linux-gnu/sane/libsane-hpaio.so.1'
saned[2103]: [dll] init: initializing backend `hpaio'
saned[2103]: [dll] init: backend `hpaio' is version 1.0.0
saned[2103]: [dll] sane_get_devices: found 1 devices
saned[2103]: saned exiting
The client shows
device `net:192.168.7.66:hpaio:/usb/psc_1300_series?serial=HU3AFBQ28Y9F'
is a Hewlett-Packard psc_1300_series all-in-one
device `net:192.168.7.15:hpaio:/usb/ENVY_4500_series?serial=CN56G332DT060D'
is a Hewlett-Packard ENVY_4500_series all-in-one
> I've installed 3.17.6+repack0-2 from testing on this jessie machine,
> alongside sane 1.0.14-12, and while a local scanimage -L listing
> produces:
>
> device `hpaio:/net/HP_LaserJet_3052?ip=192.168.14.30' is
> a Hewlett-Packard HP_LaserJet_3052 all-in-one
>
> doing so remotely just gets "No scanners were identified." Yet, he
> logs on the sane server indicate that the connection attempt was
> authorized, and one local scanner found:
>
> systemd[1]: Started Scanner Service ([2001:xxx]:58988).
> saned[29780]: saned (AF-indep+IPv6+systemd) from sane-backends 1.0.25 starting up
> saned[29780]: check_host: access by remote host: 2001:xxx
> saned[29780]: init: access granted to madduck@2001:xxx
> saned[29780]: saned exiting
> saned[29780]: [sanei_debug] Setting debug level of dll to 255.
> saned[29780]: [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25
> saned[29780]: [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d'
> saned[29780]: [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d'
> saned[29780]: [dll] sane_init/read_dlld: considering /etc/sane.d/dll.d/hplip
> saned[29780]: [dll] sane_init/read_config: reading dll.d/hplip
> saned[29780]: [dll] add_backend: adding backend `hpaio'
> saned[29780]: [dll] sane_init/read_dlld: done.
> saned[29780]: [dll] sane_init/read_config: reading dll.conf
> saned[29780]: [dll] sane_get_devices
> saned[29780]: [dll] load: searching backend `hpaio' in `/usr/lib/x86_64-linux-gnu/sane:/usr/lib/sane'
> saned[29780]: [dll] load: trying to load `/usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1'
> saned[29780]: [dll] load: dlopen()ing `/usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1'
> saned[29780]: [dll] init: initializing backend `hpaio'
> saned[29780]: [sanei_debug] Setting debug level of hpaio to 255.
> saned[29780]: [hpaio] sane_hpaio_init(): scan/sane/hpaio.c 323
> saned[29780]: [dll] init: backend `hpaio' is version 1.0.0
> saned[29780]: [hpaio] sane_hpaio_get_devices(local=1): scan/sane/hpaio.c 342
> saned[29780]: [dll] sane_get_devices: found 0 devices
> saned[29780]: saned exiting
>
> Judging from the local=1 followed by "found 0 devices", I'd say the
> problem continues to exist precisely as I described in #838212.
> I might of course be very wrong
Now my testing results get interesting (or perplexing).
Note the second scanner device discovered. Normally, the ENVY is not
attached to a computer; its scanner function is advertised with AirPrint
and the hpaio backend on a client picks it up, where it can be used with
xsane etc. However, I have now set it up to be shared by the machine at
192.168.7.15. The machine runs jessie!
Ok, there is a difference between the two servers but I do not think it
is relevant. 192.168.7.66 has hplip installed, 192.168.7.15 does not.
192.168.7.15 has only libsane-hpaio, libhpmud0 (from jessie-backports)
and 56-hpmud.rules, which is all that is required for scanning from an
aio device.
Regards,
Brian.
Reply to: