"fing -n" CLI behave differently under Windows and Raspbian (fing 5.5.2 for both)

typing "fing -n 192.168.1.1/24" using fing CLI under Windows leads after scanning to a list with all hosts which are "up" and if reached before also "down".

Using the same command under Raspbian ist starts with "Discovery round starting" but stucks after a while (and does not go on anymore) The Windows version of Fing CLI does not stop and repeats the search as it should be.

(unfortunatly the same beaviour with "fing" only).

Does someone have any ideas why?



Answers

  • betaLuser
    betaLuser Member Posts: 2
    First Comment
    Installing on a further Raspberry Pi I got the same result.
    fing is installed at /usr/bin/ ("where fing"). Rights are 755 (rwxr-xr-x).

    by accident I tried to run fing with su-rights (sudo) - and it worked.
    which libraries does fing CLI (fing-5.5.2_armhf.deb) use that it runs under the "pi" account, but gets stuck after some devices found?