[sane-devel] Cannot scan over an open local network

[Olaf Meeuwissen]

Please reply to the list so that others can chime in and find a solution
to your problem (if any).

Joel Webster writes:

> Relevant output of "sudo ifconifg":
> eth2      Link encap:Ethernet  HWaddr 00:e0:4c:f8:68:6c
>           inet addr:192.168.17.19  Bcast:192.168.17.255  Mask:255.255.255.0
>           inet6 addr: fe80::2e0:4cff:fef8:686c/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:1220938 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:758956 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1027283786 (1.0 GB)  TX bytes:1079186151 (1.0 GB)
>           Interrupt:23 Base address:0xa000

Hmm, "eth2" ... looks like you have more than one network interface.

Is this on the server or the client?  Ideally, I'd like to see both.

> Output of "grep setfacl /lib/udev/rules.d/*-libsane.rules":
> ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw
> $env{DEVNAME}"
>
> Output of "groups saned":
> saned : saned
>
> Output of "sudo service saned status":
> saned is running.
>
>
> I can see that I have a discrepancy in the "groups saned" output. I have
> added the saned user to the scanner group and I have verified that "groups
> saned" returns both saned and scanner. I have restarted the saned service,
> but I still cannot scan via the network, not even through localhost on the
> server.

Which leaves us waiting for your configuration files.

>> For lack of a crystal ball ;-), posting your /etc/sane.d/net.conf and
>> /etc/sane.d/saned.conf files as well as information about your network
>> configuration would be very helpful in trouble shooting this.

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2           FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962               Help support software freedom
                 http://www.fsf.org/jf?referrer=1962