manual entry for a device

[miji2 2]

Is there a way to manually define a device for ones that are a very hardened or are in a neighbouring subnet and thus not auto-detected?

[Lars 10]

Not at this point, no.

[miji2 2]

That's too bad because on a segregated network, the agent only reports router for the subnet, and not the main one just above it or any devices on the parent subnet. 

[Giancarlo 31]

There is already a request for an additional feature here:

When Domotz will support this, I suppose also your case will be supported.

[garym999 0]

Problem for me too. I have two IP addresses that "Advanced IP Scanner" will find with a simple IP scan yet Domotz can't and they all sit on the local LAN.

 

Granted they are not 100% normal but also not that unusual. One is a printer that is attached to a DLink USB print server. The IP address for the DLink's web admin console is found but not the address that it uses to present the USB printer. The second device is a custom device (IOT like) but it is located in a part of the building with no hardwired connectivity so it is connected to a TP-Link wireless access point. Again the web console IP address for the WAP is found but not the IP address of the actual device.

 

Surely any method of finger printing and profiling devices is essential as it could be these vary devices causing issues? So a manual add is a must or a better method to identify devices in the first place

[garym999 0]

Also forgot to say Fing finds them straight away but flags them a being multiIP relating the host address and the client together

[Giancarlo 31]

@garym999, sorry for the delay in getting back to you. Well, as for Fing, you should also be able to see the two IP addresses behind the main device.

 

For example, if you click on the DLink USB Print Server, you should also see the IP address of the Printer (bound to the same device). Two IP addresses should be reported in the Device Details - Info tab of the DLink USB Print Server. Same for TP-Link WiFi access point. Let us know if this is not the case.

 

At the moment, as Fing does, we distinguish devices by their MAC address. In the case of the Printer behind the DLink USB Print server, it is basically shown on the network with the same MAC address of the DLink USB Print server itself. Same for the TP-Link wireless access point.  

[garym999 0]

Ah you are right, if I click on the host device there is the second IP address under the master. In Fing it clearly shows the device in the initial list with a nice icon to highlight the fact there are two addresses on the one device. Surely that is the way to do it? It should show both addresses on the initial devices page for clarity otherwise it is not obvious

[garym999 0]

It also means that the IP address behind the device that maybe the more important thing to monitor can't. So either this needs to be sorted out or there needs to be a way to manually add addresses to be monitored. The later may still be required as there may be things that are important to the clients network that might reside elsewhere