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

[Joel Webster]

I only have the one eth interface being used on the server, but since I
have the cable plugged into the third port, it comes up as eth2 instead of
eth0.

Ok, so here is the client's relevant ifconfig info:
wlan0     Link encap:Ethernet  HWaddr 00:19:7e:57:45:35
          inet addr:192.168.17.52  Bcast:192.168.17.255  Mask:255.255.255.0
          inet6 addr: fe80::219:7eff:fe57:4535/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:31284 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31597 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:18173897 (18.1 MB)  TX bytes:9295105 (9.2 MB)


Here is /etc/sane.d/net.conf from the server:
# This is the net backend config file.

## net backend options
# Timeout for the initial connection to saned. This will prevent the backend
# from blocking for several minutes trying to connect to an unresponsive
# saned host (network outage, host down, ...). Value in seconds.
connect_timeout = 60

## saned hosts
# Each line names a host to attach to.
# If you list "localhost" then your backends can be accessed either
# directly or through the net backend.  Going through the net backend
# may be necessary to access devices that need special privileges.
localhost
127.0.0.1



And here is /etc/sane.d/saned.conf from the server:
# saned.conf
# Configuration for the saned daemon

## Daemon options
# Port range for the data connection. Choose a range inside [1024 - 65535].
# Avoid specifying too large a range, for performance reasons.
#
# ONLY use this if your saned server is sitting behind a firewall. If your
# firewall is a Linux machine, we strongly recommend using the
# Netfilter nf_conntrack_sane connection tracking module instead.
#
data_portrange = 10000 - 10100


## Access list
localhost
127.0.0.1
192.168.17.1/24
# A list of host names, IP addresses or IP subnets (CIDR notation) that
# are permitted to use local SANE devices. IPv6 addresses must be enclosed
# in brackets, and should always be specified in their compressed form.
#
# The hostname matching is not case-sensitive.

#scan-client.somedomain.firm
#192.168.0.1
#192.168.0.1/29
#[2001:7a8:185e::42:12]
#[2001:7a8:185e::42:12]/64

# NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and
# /etc/services must also be properly configured to start
# the saned daemon as documented in saned(8), services(4)
# and inetd.conf(4) (or xinetd.conf(5)).




On Sun, Nov 25, 2012 at 6:31 PM, Olaf Meeuwissen
<olaf.meeuwissen at avasys.jp>wrote:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20121126/3964c4e4/attachment.html>