sane (sane-airscan) not working
I posted this question on the sane-devel list a few weeks ago and Johannes Meixner was so kind as to point me to a possible solution, but that didn't work. Since I'm having this problem only with openSUSE machines, I now think this is actually the right list to ask. I have a multifunction printer Canon MF746Cx. I also have several machines, relevant are one bare-metal Ubuntu 22.04, one VM Kali 2024, one VM Debian 12, both running under openSUSE Leap 15.5 with KVM, the bare openSUSE Leap 15.5 and one bare-metal Tumbleweed. Like said, on all three Debian-based machines, scanning just works out of the box. On both openSUSE machines, it doesn't. I have installed for Leap and TW the sane-airscan package from https://software.opensuse.org/search?baseproject=ALL&q=airscan as suggested by Johannes Meixner in the other mailing list. One thing I have noticed is that in both openSUSE machines "airscan-discover -d" only "tries" the network address of the machine itself: it seems not to "go out of the machine", whereas in the Debian-based machines it scans the entire network. Could it be a firewall/apparmour/selinux problem? Any suggestion would be most appreciated. Thank you.
Le 04/06/2024 à 07:43, Andreas Croci a écrit :
Any suggestion would be most appreciated.
stop the firewall at discovery time (setup)? jdd -- https://artdagio.fr
On 04/06/24 07:47, jdd@dodin.org wrote:
Le 04/06/2024 à 07:43, Andreas Croci a écrit :
Any suggestion would be most appreciated.
stop the firewall at discovery time (setup)?
jdd
That worked for a certain time. I systemctl stop(ped) firewalld.service and reran scanimage -L. It found the scanner. Then, since I don't really want to leave the firewall stopped, I started it again. Right after that scanimage kept finding the scanner, for some to me obscure reason. After a few minutes, though, another scanimage -L gives me: "No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages)." I tried to open port 80 in the firewall, because that appeared to be the port where "airscan-discover -d" found the scanner before, but it didn't work. Is there a permanent solution without deactivating the firewall altogether? Amazingly enough the same device works fine as a printer. Thank you.
Maybe this one: https://forums.opensuse.org/t/xerox-c235-scanning/175323/7 Am Dienstag, 4. Juni 2024, 13:01:44 CEST schrieb Andreas Croci:
On 04/06/24 07:47, jdd@dodin.org wrote:
Le 04/06/2024 à 07:43, Andreas Croci a écrit :
Any suggestion would be most appreciated.
stop the firewall at discovery time (setup)?
jdd
That worked for a certain time. I systemctl stop(ped) firewalld.service and reran scanimage -L. It found the scanner. Then, since I don't really want to leave the firewall stopped, I started it again. Right after that scanimage kept finding the scanner, for some to me obscure reason. After a few minutes, though, another scanimage -L gives me:
"No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages)."
I tried to open port 80 in the firewall, because that appeared to be the port where "airscan-discover -d" found the scanner before, but it didn't work. Is there a permanent solution without deactivating the firewall altogether? Amazingly enough the same device works fine as a printer.
Thank you.
That didn't work either. It did as long as I have the firewall turned off, but when I turn it back on, it can't find the scanner any more. I guess there must be a way to add an exception in the firewall somehow, but I'm not that good with firewalld: I have used iptables until now. Very naively, I tried to set my whole home network (192.168.200.0/24) in the "sources" tab of the default zone (public, why is a different question), but it didn't work either. I was thinking maybe it's not the scanning of the network that's blocked by the firewall, but the reply from the devices. No luck, I'm open for further suggestions. On 04/06/24 13:06, Stephan Hemeier wrote:
Maybe this one: https://forums.opensuse.org/t/xerox-c235-scanning/175323/7
Am Dienstag, 4. Juni 2024, 13:01:44 CEST schrieb Andreas Croci:
On 04/06/24 07:47, jdd@dodin.org wrote:
Le 04/06/2024 à 07:43, Andreas Croci a écrit :
Any suggestion would be most appreciated.
stop the firewall at discovery time (setup)?
jdd
That worked for a certain time. I systemctl stop(ped) firewalld.service and reran scanimage -L. It found the scanner. Then, since I don't really want to leave the firewall stopped, I started it again. Right after that scanimage kept finding the scanner, for some to me obscure reason. After a few minutes, though, another scanimage -L gives me:
"No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages)."
I tried to open port 80 in the firewall, because that appeared to be the port where "airscan-discover -d" found the scanner before, but it didn't work. Is there a permanent solution without deactivating the firewall altogether? Amazingly enough the same device works fine as a printer.
Thank you.
Try to find out on which Port the network is scanned, and open this Port in the FW.
Schöne Grüße
Axel
--
Written from cell phone - excuses for typos
Am 4. Juni 2024 13:49:17 MESZ schrieb Andreas Croci
That didn't work either. It did as long as I have the firewall turned off, but when I turn it back on, it can't find the scanner any more.
I guess there must be a way to add an exception in the firewall somehow, but I'm not that good with firewalld: I have used iptables until now. Very naively, I tried to set my whole home network (192.168.200.0/24) in the "sources" tab of the default zone (public, why is a different question), but it didn't work either. I was thinking maybe it's not the scanning of the network that's blocked by the firewall, but the reply from the devices.
No luck, I'm open for further suggestions.
On 04/06/24 13:06, Stephan Hemeier wrote:
Maybe this one: https://forums.opensuse.org/t/xerox-c235-scanning/175323/7
Am Dienstag, 4. Juni 2024, 13:01:44 CEST schrieb Andreas Croci:
On 04/06/24 07:47, jdd@dodin.org wrote:
Le 04/06/2024 à 07:43, Andreas Croci a écrit :
Any suggestion would be most appreciated.
stop the firewall at discovery time (setup)?
jdd
That worked for a certain time. I systemctl stop(ped) firewalld.service and reran scanimage -L. It found the scanner. Then, since I don't really want to leave the firewall stopped, I started it again. Right after that scanimage kept finding the scanner, for some to me obscure reason. After a few minutes, though, another scanimage -L gives me:
"No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages)."
I tried to open port 80 in the firewall, because that appeared to be the port where "airscan-discover -d" found the scanner before, but it didn't work. Is there a permanent solution without deactivating the firewall altogether? Amazingly enough the same device works fine as a printer.
Thank you.
OK, thank you everybody. The linked document didn't help, because, as far as I understand, the listed ports 8610 and 8612 refer to the pixma backend. By enabling firewalld logging (and walking my way through the jungle of entries in the journal, that are an awful lot), I was able to find out that the ports to open are the 3702 for WSD and 5353 for eSCL, if one wants that too: any one will do. Bottom line, it now works fine and survives reloads of the firewall and reboots on both Leap and TW, so we can consider the problem solved. Thanks, Andreas On 04/06/24 15:53, Larry Len Rainey wrote:
This document says what ports to open for sane
https://wiki.debian.org/SaneOverNetwork#Opening_Ports
On 6/4/24 08:22, Axel Braun wrote:
Try to find out on which Port the network is scanned, and open this Port in the FW.
Schöne Grüße Axel
On 06-04-2024 12:43AM, Andreas Croci wrote:
I posted this question on the sane-devel list a few weeks ago and Johannes Meixner was so kind as to point me to a possible solution, but that didn't work. Since I'm having this problem only with openSUSE machines, I now think this is actually the right list to ask.
I have a multifunction printer Canon MF746Cx. I also have several machines, relevant are one bare-metal Ubuntu 22.04, one VM Kali 2024, one VM Debian 12, both running under openSUSE Leap 15.5 with KVM, the bare openSUSE Leap 15.5 and one bare-metal Tumbleweed.
Like said, on all three Debian-based machines, scanning just works out of the box. On both openSUSE machines, it doesn't. I have installed for Leap and TW the sane-airscan package from https://software.opensuse.org/search?baseproject=ALL&q=airscan as suggested by Johannes Meixner in the other mailing list.
One thing I have noticed is that in both openSUSE machines "airscan-discover -d" only "tries" the network address of the machine itself: it seems not to "go out of the machine", whereas in the Debian-based machines it scans the entire network. Could it be a firewall/apparmour/selinux problem?
I think airscan-discover is depreciated see here: > https://github.com/alexpevzner/airscan-discover#airscan-discover On the Tumbleweed machine here passing airscan-discover -d gives this output: :~> airscan-discover The program 'airscan-discover' can be found in the following package: * sane-airscan [ path: /usr/bin/airscan-discover, repository: openSUSE:repo-oss ] Try installing with: sudo zypper install sane-airscan :~> zypper se airscan Loading repository data... Reading installed packages... S | Name | Summary | Type ---+--------------------+---------------------------------------------------+-------- i+ | libsane-airscan1 | Library files for sane-airscan | package i+ | sane-airscan | Universal driver for Apple AirScan (eSCL) and WSD | package | sane-airscan-devel | Devel files for sane-airscan | package Not certain as to why passing airscan-discover has a different output here. The Tumbleweed machine here is getting the package from repository
1. What is the scanimage -L output? 2. Have you looked at /etc/sane.d/dll.conf contents? 3. Have you added an entry to /etc/sane.d/airscan.conf for your device? For scanner here have added the following under [devices] > "brother-MFC-J485DW" = http://192.168.1.20:80/eSCL 4. Have you installed any Canon MF746Cx proprietary software? 5. Curiously Does YaST2 recognize the scanner at all? 6. Which frontend are you attempting? Using Xsane here. In airscan.conf you can setup to trace > https://github.com/alexpevzner/sane-airscan#reporting-bugs On the Tumbleweed machine here firewalld status is: > firewalld.service enabled disabled I am not much familiar with firewalld but I added that information. -Thanks
participants (6)
-
-pj -
Andreas Croci -
Axel Braun -
jdd＠dodin.org -
Larry Len Rainey -
Stephan Hemeier