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

Olaf Meeuwissen olaf.meeuwissen at avasys.jp
Tue Nov 27 23:41:46 UTC 2012


Joel Webster writes:

> 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

So both client and server are on the same subnet and can communicate
directly with one another.

> Here is /etc/sane.d/net.conf from the server:
> # [...snip...]
> localhost
> 127.0.0.1

And on the client you have a net.conf that lists the server's IP
address?  You don't really need localhost on the client.

> And here is /etc/sane.d/saned.conf from the server:
> # [...snip...]
> data_portrange = 10000 - 10100
> ## Access list
> localhost
> 127.0.0.1
> 192.168.17.1/24

That looks fine, access should be granted to any client on the same
subnet in addition to localhost.  However, in your initial post you
mentioned that you cannot even scan through localhost even though saned
appears to be running and the saned user is in the scanner group.  Hmm.

Is saned listening, and on the right port?  Can you access saned via
telnet?  On the server, run

  sudo netstat -tunealp | egrep '(:6566|saned)'
  telnet localhost 6566

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



More information about the sane-devel mailing list