[sane-devel] FIXED: network scanning quit working -- and a related question

Perry Hutchison pluto at agora.rdrop.com
Sat Dec 5 09:48:46 GMT 2020


pluto at agora.rdrop.com (Perry Hutchison) wrote:
> This has to be something utterly trivial :(
>
> I have a Canon copier/printer/scanner on the same (wired) Ethernet
> as an Ubuntu Linux system.  In the past this combination has "just
> worked" -- I didn't have to configure anything -- but today neither
> Simple Scan nor "scanimage -L" can find the scanner.
>
> The one change I know of is that, since the last time it was working,
> the scanner reported (via the front-panel LCD) that its IP address
> had changed; and the new IP address is a bit strange:  169.254.53.67,
> (previously 192.168.0.10, the local network being 192.168.0/24).
> ...
>
>   Canon ImageCLASS MF4880dw
>
>   Ubuntu 18.04.5 LTS
>   Intel processor, 64-bit mode
>
>   $ scanimage -V
>   scanimage (sane-backends) 1.0.27; backend version 1.0.27
>
>   $ scanimage -L
>   No scanners were identified ...

After power-cycling the device, it reported that its IP address had
changed back to 192.168.0.10, and it is now found:

  $ scanimage -L
  device `pixma:MF4800_192.168.0.10' is a CANON Canon i-SENSYS MF4800 Series multi-function peripheral

Question:  Since link-local addresses in 169.254.0.0/32 seem to be
every bit as local as addresses on the local subnet, would it make
sense for SANE to search for networked scanners on 169.254.0.0/32
in addition to the local subnet?



More information about the sane-devel mailing list