Hi Anton,
Success!
Very good! :-)
I got my TS9120 recognized by sane-airscan! I ran make uninstall in the
sane-backends directory. That eliminated all of sane files in usr/local
as far as I could tell. I considered reinstalling sane-airscan but
instead just ran scanimage -L. It found the scanner! I cleaned up:
Deleted the sane-backends folder, scangearmp2, closed all the holes in
the firewall except for port 443 tcp.
You don't need to keep any ports open. Firewall is about incoming
connections, outgoing connections are usually unrestricted by default.
Xsane finds 4 Canon TS9100 scanners (ESCL https 443, http 80, 443, and
Airscan serial escl network scanner). I can't complain about too much now.
Seems you have two backends installed: sane-escl from SANE and
sane-airscan from me;
AirScan - this is my backend. ESCL - this is sane-escl. As your scanner
exposes 3 endpoints, sane-escl shows it as 3 distinct devices, while
sane-airscan merges all instances together, choosing the best endpoint
automatically.
At least on my system finding the scanner can take minutes most times.
It finds the scanners but sometimes returns with scanner out of memory.
Please retest it separately with sane-escl and with sane-airscan.
sane-airscan should use significantly less memory that sane-escl.
small observation:
In windows, the scanner finds the windows computer, allowing the scanner
to initialize saving to computer, but that is not part of airscan,
apparently. Not needed; can attach to email or something else.
Yes, it is different mode. Linux lacks required infrastructure to
implement such a mode (and I'm not sure if it actually useful).
--
Wishes, Alexander Pevzner ([email protected])
