MMM-NetworkScanner-loading...indefinitely

[sdetweil]

@jthirasilpa change showUnknown: to true in config.js…

ip addresses 11, 17, and 70 are not known according to the arp scan

[jthirasilpa]

Hi Sam - they were not at the time of the scan, but they have been picked up in console messages previously. For example:

Shouldn’t that then show up on the Mirror?

[sdetweil]

@jthirasilpa not my module. Trying to help

[jthirasilpa]

@sdetweil Hi Sam - I appreciate your assistance. I am actually asking that question legitimately out of ignorance. I assume that if it appears in the console as follows:

Object { ipAddress: “192.168.1.11”, name: “Champagne”, icon: “server”, color: “#ffffff”, showOffline: true, online: true }

then it would be show up in the Mirror, but maybe there are several steps in between…

In any case - thanks for your help.

[sdetweil]

@jthirasilpa it matches the IP address with the scanned Mac addresses.
If not in the Mac addresses it is not shown.

In debug mode I get a big blast of the Mac address info displayed every time there is a scan

[jthirasilpa]

@sdetweil OK - do not have access to machine now, but will have a look later. Thanks.

[jthirasilpa]

@sdetweil
This is one of the devices from the config.js

{ ipAddress: "192.168.1.11", name: "Champagne", icon: "server"}

MMM-NetworkScanner received a notification: IP_ADDRESS 
Object { ipAddress: "192.168.1.11", name: "Champagne", icon: "server", color: "#ffffff", showOffline: true, online: true }

This is from the console:

MMM-NetworkScanner.js:70:30
MMM-NetworkScanner IP_ADDRESS device:  
Array [ "Champagne", true ]
MMM-NetworkScanner.js:80:31
MMM-NetworkScanner is updating device status. 
Array [ "Champagne", true ]
MMM-NetworkScanner.js:284:31
MMM-NetworkScanner Champagne is online

Strangely when I run sudo arp -scan -l, this device doesn’t appear. But doesn’t the information from the console suggest that it should be displayed?

Conversely, the arp scan does find 192.168.1.15, but console displays this:

MMM-NetworkScanner received a notification: IP_ADDRESS 
Object { ipAddress: "192.168.1.15", name: "Millie", icon: "server", color: "#ffffff", showOffline: true, online: false }
MMM-NetworkScanner.js:70:30
MMM-NetworkScanner IP_ADDRESS device:  
Array [ "Millie", false ]
MMM-NetworkScanner.js:80:31
MMM-NetworkScanner is updating device status. 
Array [ "Millie", false ]

I would think that one of these would be displayed on the MM.

Any further thoughts? Thanks.

[sdetweil]

@jthirasilpa are those wireless? The arp scan only did Ethernet connected devices

[jthirasilpa]

Those devices are ethernet connected. Also, I was just checking the logs and there are a lot of ip addresses and:

0|mm       | [20:52:38.389] [LOG]    MMM-NetworkScanner is performing arp-scan
0|mm       | [20:52:38.419] [LOG]    MMM-NetworkScanner is performing ip address scan

but no MAC addresses - which you seem to have in your logs.

[jthirasilpa]

After a complete reinstall of MM, I finally managed to resolve this. After reinstalling the original NetworkScanner module and using macaddresses to add to the config.js, I kept getting the “sudo requires your password” message. I went through node_helper.js and the only command that appears to require sudo is arp-scan. So I amended sudoers to allow sudo arp-scan without password using:

sudo visudo

and then adding:

 # Allow arp-scan without sudo
username ALL=(ALL) NOPASSWD: /usr/sbin/arp-scan

This allows sudo arp-scan to run without a password, while maintaining password requirements for other sudo commands.

Many thanks to Sam et. al. for input on this issue.