Am 04.03.2015 um 14:30 schrieb Rolf Leggewie: > Hello, > > with scanbd sitting on top of the net backend I wonder if and how actual > scanning over the LAN still works. Two scenarios. > > a) sharing a scanbd scan host SH via the LAN to scan client SC > b) accessing a saned LAN scanner LS on a scanbd-enabled computer SES > > Are both scenarios supported? This will have implications for my > packaging as well. > > I guess scenario A ought to be possible by adding something like > "192.168.0.0/24" to /etc/sane.d/saned.conf on SH, while scenario B would > require adding the IP or hostname of LS to /etc/sane.d/net.conf on SES. > > So far, so (theoretically) good? I wonder especially if scenario B > isn't going to blow up in my face.
Should be ok if you omit localhost in saned / /etc/scanbd/net.conf. But: local or remote scan-applications must (only) include the scanbd host in /etc/sane.d/net.conf (either localhost or remote). -- Wilhelm w.me...@unix.net -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
