[SOLVED] cannot scan with sane over network, local machine works
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
root@server:~# cat /etc/services | grep sane
sane-port 6566/tcp #SANE network scanner daemon
root@server:~# cat /etc/inetd.conf | grep sane
sane-port stream tcp nowait root.scanner /usr/sbin/saned saned
root@server:~# cat /etc/sane.d/saned.conf
# 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
# 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
10.0.0.0/24
[2001:5c0:1503:6600::]/64
[fe80::]/10
# 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)).
This may be so obvious that it sounds stupid, but, if this is a printer as well as a scanner, can you print to to it over the network?
Also, what are the make and model of the scanner and how is it shared over the network? If it is shared via Samba and CUPS, what does smbclient report?
Last edited by frankbell; 12-17-2010 at 07:53 PM.
Reason: clarity
I've been trying so much that I don't know what made it work, but it works. For now.
What I think did the trick is loading the module "nf_conntrack_sane" into the kernel on the server.
That way iptables recognises the higher ports that are used for I-don't-know-what as RELATED. I think it's similar to FTP.
BTW, If anyone from the Slackware Team is reading this:
The module names for connection tracking in rc.modules are outdated. They are still called ip_conntrack_* instead of nf_conntrack_*.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.