Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS

2021-05-08 Thread Ralph Little
Hi, On 2021-05-08 3:49 p.m., m. allan noah wrote: > Chances are, you are wrong :) > > allan > > On Sat, May 8, 2021 at 4:50 AM Andrew Goodbody wrote: >> Chances are that rather than interfering with Sane, the proprietary >> software does something that made the scanner work the next time you ran

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Ralph Little
Hi, On 2021-05-08 3:23 p.m., Media Mouth wrote: > Haven't yet tried the "-d10" debugging > But even before doing that, checking over syslog.  The following are > the most suspicious lines: > > "inetd[444]: sane-port/tcp: bind: Address already in use" > > "saned[2038]: read_config: could

Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS

2021-05-08 Thread m. allan noah
Chances are, you are wrong :) allan On Sat, May 8, 2021 at 4:50 AM Andrew Goodbody wrote: > > Chances are that rather than interfering with Sane, the proprietary > software does something that made the scanner work the next time you ran > Sane after having just run the ScanSnap app. > > Andrew

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Media Mouth
> On May 8, 2021, at 2:38 PM, Ralph Little wrote: > > no point changing the saned.conf on the client side. > On the server, add 192.168.0.15 to saned.conf on a line on its own. > Ok so for clarity, some simplified IPs Client machine (192.168.0.Client) 'dll.conf' the line "net" is commented

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Ralph Little
Hi, On 2021-05-08 2:13 p.m., Media Mouth wrote: > >> On May 8, 2021, at 1:27 PM, Ralph Little > > wrote: >> >> Do you have 192.168.0.15 in /etc/sane.d/saned.conf? > > Yes. > > Though I wonder if I misunderstood what `saned.conf` is doing. > I thought for remote scanning

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Media Mouth
> On May 8, 2021, at 1:27 PM, Ralph Little wrote: > > Do you have 192.168.0.15 in /etc/sane.d/saned.conf? Yes. Though I wonder if I misunderstood what `saned.conf` is doing. I thought for remote scanning it's in play server side, as opposed to client side. the LAN IP of the Client Machine

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Ralph Little
Hi On 2021-05-08 1:08 p.m., Media Mouth wrote: > > >> On May 8, 2021, at 12:55 PM, Ralph Little > > wrote: >> >> On the client, if the net backend has access to the server then you >> should be able to just do scanimage -L >> >> If you are not sure if it is contacting

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Media Mouth
> On May 8, 2021, at 12:55 PM, Ralph Little wrote: > > On the client, if the net backend has access to the server then you should be > able to just do scanimage -L > > If you are not sure if it is contacting the server, you can generate net > backend diag to see what it is doing: > >

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Ralph Little
Hi, On 2021-05-08 12:50 p.m., Media Mouth wrote: > So the good news is the `netstat -an | grep 6566` returns `tcp6       > 0      0 :::6566                 :::*                    LISTEN` > > To "scanimage" list that printer is `scanimage -L` enough or do you > have to specify the target IP

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Media Mouth
So the good news is the `netstat -an | grep 6566` returns `tcp6 0 0 :::6566 :::*LISTEN` To "scanimage" list that printer is `scanimage -L` enough or do you have to specify the target IP address? > On May 8, 2021, at 10:54 AM, Ralph Little wrote:

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Brian Potkin
On Sat, 8 May 2021 at 18:35, Media Mouth wrote: > On the Server machine > > in file 'sane.d' (/usr/local/etc/sane.d), add the IPs permitted to scan. saned.conf holds the list of permitted hosts. Cheers, Brian.

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Ralph Little
Hi, On 2021-05-08 10:35 a.m., Media Mouth wrote: > Thanks, Ralph for the info below. > If I'm understanding correctly, once the scanner is successfully > connected via USB to a local computer, you can share that scanner to > the LAN. > Is that correct? > > From what I understand (at least from 

Re: [sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Media Mouth
Yes, thanks for the correction saned.conf (/usr/local/etc/sane.d/saned.conf) > On May 8, 2021, at 10:48 AM, Brian Potkin wrote: > > On Sat, 8 May 2021 at 18:35, Media Mouth wrote: > >> On the Server machine >> >> in file 'sane.d' (/usr/local/etc/sane.d), add the IPs permitted to scan. > >

[sane-devel] How to scan via WiFi over a LAN

2021-05-08 Thread Media Mouth
Thanks, Ralph for the info below. If I'm understanding correctly, once the scanner is successfully connected via USB to a local computer, you can share that scanner to the LAN. Is that correct? From what I understand (at least from this link ) On the

Re: [sane-devel] scanimage -L detects no scanners / sane-find-scanner does -- on MacOS

2021-05-08 Thread Media Mouth
RE > In general, you would not have both the factory software and sane on the > machine at the same time. Agreed. For that particular scanner / machine I'm not permitted to remove the existing Fujitsu software, but it does seem to be the very thing that's causing `scanimage -L` to fail to see