Arch Linux

barney

Member

Registered: 2020-12-14

Posts: 130

[SOLVED]avahi problems with sane

I have successfully configured scanner on the server side. Now I wont to access it on the laptop. I have followed the instruction on https://wiki.archlinux.org/title/SANE and when I add the IP address of the server in

/etc/sane.d/net.conf

I can access the scanner over the network, but when I add a line of the form <server-hostname>.local in the

/etc/sane.d/net.conf

the scanner cannot be found by

scanimage -L

I suppose that name resolution is not working, but cups on the same server is working perfectly, it shares the printers on the network and I can find them on the workstations (laptops, mobiles).

ping <server-histname>.local

is working

avahi-resolve-host-name -4 <server-hostname>.local

is giving the correct address.

Last edited by barney (2023-12-17 05:49:32)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,096

Re: [SOLVED]avahi problems with sane

https://man.archlinux.org/man/sane-net.5.en only mentions hostnames, not FQDN names.

Have you tried putting just the hostname in net.conf ?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

barney

Member

Registered: 2020-12-14

Posts: 130

Re: [SOLVED]avahi problems with sane

https://man.archlinux.org/man/sane-net.5.en only mentions hostnames, not FQDN names.

Have you tried putting just the hostname in net.conf ?

I have found what was the problem.
In /etc/nsswich.conf I have put

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

. Because of that the name resolution was in the IPv6 address space, but in the /etc/sane.d/saned.conf I have put

192.168.0.0/24

, which is in the IPv4 address space. So when I wanted to connect to the server the resolved address of the laptop was IPv6 address and that address was not allowed to access the server. I have replaced mdns_minimal with mdns4_minimal (on the server and on the laptop), and everything is working fine.
Thanks.