Subscriber Discussion

Universal IP Tool For Axis, Hikvision, Dahua, Bosch, Hanwah, Vivotek, Panasonic, Sony, Flir, Etc.

Hi everyone,

During my week-ends/spare time, I am working on an open-source project I would like to share with IPVM members and propose you to participate.

This is small unique tool that scan a network and can detect several camera vendors, using open protocols (ONVIF, UPnP, etc.) but ALSO proprietary vendor discovery protocols.

UniversalScanner

Last version can be found here: UniversalScanner (Portable) or here: UniversalScanner (Installer).You will need a Windows system with dotNet v4.5.2

Today, it supports the open protocols below:

  • SSDP (UPnP)
  • WS-Discovery (ONVIF)
  • DNS-SD (Zeroconf)

And vendor discovery protocols:

  • Axis
  • HikVision
  • Dahua
  • Bosch
  • Hanwha
  • Vivotek

I am working to integrate also currently these vendor protocols as well: Sony, Flir, PanasonicThese last ones are almost done and Jhon Honovich has proposed me his help in order to validate and finish integration with the devices in IPVM's lab, that's pretty cool!

It does support only IPv4 for now, I am considering to add support of IPv6.I was thinking to make also a Linux software port later (would be only in command tools) for installers who install/use camera over Linux.

How you can participate?

  • Test the tool and share your feedback;
  • You want another vendor discovery protocol to be integrated into the tool? With a test device on you side and the vendor IP Tool you can probably collect enough information to let do this.
  • Let me know if a Linux version (in command line) would be helpful for you;
  • Let me know also if a IPv6 support would be helpful (should be available for most of the camera vendors);

Thank you!Julien

Agree
Disagree
Informative: 29
Unhelpful
Funny

What do you think about adding discovery for common network devices like Ubiquiti and other common wireless manufacturers?

Agree: 3
Disagree
Informative
Unhelpful
Funny

Hi Steven,

Yes, this is good idea.The main condition is to have a discovery protocol in layer 3 such as multicast or broadcast. For Ubiquiti, for example it is clearly a good canditate.

Warning: boring technical details follows...

After a quick check, Ubiquiti discovery protocol looks to be:

* multicast datagrams on 233.89.188.1 on port 10001* broadast ipv4 datagrams on port 10001

Payload is basic, it looks to be the version of protocol on 32 bits, big endianness.

Do you have Ubiquiti unit accessible? I am interested to get a Wireshark capture (1) on your station when a Ubiquiti device reply to a discovery datagram; I can assist to perform such capture.

(1) Warning: do not post such capture file on the forum directly as it might contains personal information captured also.

Thanks,

Julien

Agree
Disagree
Informative: 2
Unhelpful
Funny

Hi Steven,

Do you have a network with an Ubiquiti equipment on which we could do some basic detection tests?

Thanks

Agree
Disagree
Informative
Unhelpful
Funny

Hi again,

I made this specific procedure to help to create new protocol, in case you get some free time or this.

Let me know,

Thanks,

Julien

Agree
Disagree
Informative
Unhelpful
Funny

Hi Steven,

This was finally implemented for Ubiquiti, you can find the last version with this discovery protocol here:

UniversalScanner (Portable)

UniversalScanner (Installer)

Julien

Agree
Disagree
Informative: 1
Unhelpful
Funny
Agree
Disagree
Informative: 3
Unhelpful
Funny

It's so good to see someone take this on!

Agree: 5
Disagree
Informative
Unhelpful
Funny

Just tried it and works great for what is on my network.

Agree: 3
Disagree
Informative: 1
Unhelpful
Funny

Thank you Steve.

Agree
Disagree
Informative
Unhelpful
Funny: 1

Awesome Julian, thanks for sharing!

Agree: 2
Disagree
Informative
Unhelpful
Funny

Work well, detects everything very fast and lists the unique ID.

Thanks!

Agree: 2
Disagree
Informative: 1
Unhelpful
Funny

Very cool. I have not had a chance to check it out yet, but hope to later this week.

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

Julien. I look forward to putting this tool to use. Being new to the industry I am quickly learning about all the little tools available to function in this industry. I have used the ip for Axis and Hikvision, it will definitely be advantageous for this info to be in one tool.

Cheers

Jason

Agree: 1
Disagree
Informative: 2
Unhelpful
Funny

I just installed your tool, and was amazed at the speed you have gotten out of it. It found all of my cameras on my home network, and some interesting anomalies as well! The data gathered is quite helpful from both a physical security aspect, as well as a network and hardening aspect. GREAT JOB!

Agree: 1
Disagree
Informative: 4
Unhelpful
Funny

Installed on my home network to get a feel. Loving it! Detected various PCs and network devices!

Always wanted something like this that is neutral, lightweight and easy to use.

Bravo!

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

Thank you all for your feedback.

For information, I have tested and validated Sony cameras meanwhile.

Very last version can be now here: UniversalScanner (Portable) or here: UniversalScanner (Installer).

Still, supports the open protocols below:

  • SSDP (UPnP)
  • WS-Discovery (ONVIF)
  • DNS-SD (Zeroconf)

And new vendor discovery protocols list:

  • Axis
  • HikVision
  • Dahua
  • Bosch
  • Hanwha
  • Vivotek
  • Sony
Agree
Disagree
Informative: 3
Unhelpful
Funny

Any chance of being able to filter or scan selected ranges? I just tried the tool on one of our NVR's and it works great, found a bunch of stuff, but it's scanning both NIC cards. We have one NIC for connection to VMS, and then two other NIC's teamed together for access to the camera stacks, really only interested in seeing what's on that subnet.

Great work regardless!

Agree
Disagree
Informative: 1
Unhelpful
Funny

I will consider this function but I would like to keep the user interface as simple as possible. Maybe I will add some advanced parameters somewhere (in a config file or as command line parameters).

In the current design, it will request on all interfaces, on all protocols at time (multithreading) when you click Scan button; and it is continously listening for devices info., even before you start the Scan.

What you can do until this function comes, is to perform a scan, and then export the results in CSV (right-click on the list), then within an Excel you should be able to filter out some IP range using the right formula.

Agree
Disagree
Informative: 1
Unhelpful
Funny

Sounds great! A linux version would be an obvious plus, and also a MacOS version. Almost all of the decent tools out there have MacOS, and Windows 10 distributions and many have linux ubuntu versions. AngryIP scanner, Dahua and Axis's own discovery tools etc.

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

This is a small tool I am devlopping alone for now. Having as first step, a command line scanner for Linux and Mac can be an option in the future, yes.

I am not sure I would have enough free time to port the graphical application on macOS or Linux as it involves to make again the program in objective-c/Cocoa for Mac and in C/GTK or C++/Qt for Linux. Unless I found a partner to help me on this part of the code.

Agree
Disagree
Informative: 1
Unhelpful
Funny

Great work Julien! A commandline tool for Linux would be awesome. We now have to switch away from Linux to Windows, purely to find the cameras in the network. That is quite a hassle, especially when working in the field.

A linux tool (even with the most limited functionality) would be like a gift from God :-)

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

I plan to make some linux command line also once I will get some free time but I am not sure when I will be able to do it.

Agree
Disagree
Informative
Unhelpful
Funny

If the Linux command line tool works on a chromebook (newer chromebooks have a Linux option that can be enabled) , that would be amazing. I'm happy to test!

Now an Android tool would also be neat. To be able to scan from wifi on the ladder.... 😊

Agree
Disagree
Informative
Unhelpful
Funny

I have a ton of Hanwha cameras and they don't show. I am using my WiFi...? I love the idea of this tool!!

IPVM Image

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

Hanwha discovery protocol answer always on the port 7711.If this port is already in use, the application will not listen Hanwha answer.

You cannot run both the Wisenet ip tool and UniversalScanner at same time.

I will try to see if I can find a workaround by sharing the port with the other application if this port is already in use.

Agree
Disagree
Informative
Unhelpful
Funny

Hi again,

I have checked and I am afraid this is a limitation of Hanwha protocol.

I won't be able to share the same port between both applications (Wisenet and UniversalScanner) unless I use a sniffer like WinPcap which I do not want because it is ugly design and unsafe.

Please close Wisenet when you want to use UniversalScanner (before starting it) if you would like to detect Hanwha device or alternatively enable UPnP on these devices.

Thanks,

Julien

Agree
Disagree
Informative: 2
Unhelpful
Funny

Love the idea, but it didn't pick up all of the Axis cameras at my office. I will try and see if it works better at my house.

Agree
Disagree
Informative: 1
Unhelpful
Funny

Or do you have a routed network or inter-VLAN maybe?

What about the Axis IP Utility? Does it work better?

If yes, could it be that you have Axis cameras connected behind Axis NVRs?

The Axis devices are capable to relay the presence of other Axis devices on the network, for now UniversalScanner is not yet able to get the "relayed" message from Axis device, only direct answer from camera or recorder.

Agree
Disagree
Informative
Unhelpful
Funny

It might be the same issue than the one I just made a test patch (see at bottom of the page).

If it is the case, this might be fixed after I include the fix in the next release.

Julien

Agree
Disagree
Informative
Unhelpful
Funny

This should be fixed since the build 2020-05-10 which is the first build of version 0.2.

Very last version can be found here: UniversalScanner (Portable) or here: UniversalScanner (Installer).

Do you mind to double check if it is now working?

Note: You can also see all addresses of the found devices, including ZeroConf ones by tweaking this value : HKEY_CURRENT_USER\Software\UniversalScanner\ForceZeroConf (key will be created at first launch of new version)

Thanks

Julien

Agree
Disagree
Informative
Unhelpful
Funny

Second the Linux comment! Cool tool.

Agree: 2
Disagree
Informative: 2
Unhelpful
Funny

This is a brilliant idea, nice work!

Agree: 2
Disagree
Informative: 1
Unhelpful
Funny

Hi Julien,

This is really slick. One thing I just noticed when running in our lab is that a number of the Axis cameras are showing 169.254.x.x addresses instead of their configured addresses. Any thoughts? I have posted what the Axis camera finder finds to show the difference. The other interesting thing is that this tool only seems to find Axis cameras with the ACCC8E MAC address. I have some cameras that are older and have the original Axis MAC addresses of 00408C scheme (you can see them at the bottom of the Axis camera finder screenshot) that are not being found by your scanner.

IPVM Image

IPVM Image

Agree
Disagree
Informative: 2
Unhelpful
Funny

Hi,

These are interesting points you are raising. Axis devices send back request results with a set of records including all their IPs (including the DHCP or fixed IPv4 address, the zeroconf).

The previous behavior was to pick to first IP of each device.

Can you kindly try the test patch bellow and give me feedback about the result?

Test patch for Axis

Thanks,

Julien

Agree
Disagree
Informative
Unhelpful
Funny

That patch seems to partially solve the problem. Now it just duplicates every Axis device that it finds and shows its configured IP address and its 169.254.x.x address. Whereas before it showed the 169.254.x.x address for just some devices, now it shows it for all devices.

On the plus side, it seems to also be finding most of the older devices with the 00408C style MAC address. It found two of the three that I have (the 3rd one is an Axis A1001 which is found one that has the newer MAC address but didn't find the older one).

IPVM Image

Agree
Disagree
Informative: 1
Unhelpful
Funny

Thank for your test.

This patch enable to display all IPv4 addresses returned by Axis devices.

I will probably filter out the Zeroconf ones as it is not very convinient indeed (could be, rarely, if you intend to reach them without changing your IP configuration).

Regarding the missing ones, did you try to press several times the scan button?

If it cannot be detected, it would require deeper investigation I am afraid, therefore I would need Wireshark collections when you detect it with Axis IP Tool and one Wireshark when you fail to detect it via UniversalScanner, and the IP of the device.

Let me know if you want to go further on this, I can assist with related documentation and help.

For now, I will apply this fix and hide the zeroconf address when there is a local IP also existing.

Thank you

Julien

Agree
Disagree
Informative
Unhelpful
Funny

Thanks Julien. I ran it again and it found the one remaining item this time.

Agree
Disagree
Informative: 1
Unhelpful
Funny

Have not tried the tool yet, just migrating / learning Linux(Mint 19.2 cinnamon)

But the dual Ip address happens with Mobotix cameras as from memory the serial number is also a IP address in 10.xxx.xxx.xxx range when using 192.xxx.xxx.xxx.

Will give it a go when Linux is available , Mobotix on the list?

Agree
Disagree
Informative: 1
Unhelpful
Funny

Hi Arne,

Good luck with Linux, tricky at start but once you master it, hard to switch back to another OS.

Currently, I am afraid I won't have the time to develop a Linux version even if it is something I keep in my mind; this could happen later (maybe this year? hard to give you an agenda).

Axis discovery is based on multicast DNS (mdns) providing several IPs at same time. I have no idea regarding Mobotix, I ran MxManagementCenter and it looks to be WSDiscovery (ONVIF) for the lastest version but I am not sure, maybe I missed something.

So if Mobotix does support WsDiscovery, they should be found as well via UniversalScanner (which is not yet available for Linux :( ).

Agree
Disagree
Informative
Unhelpful
Funny

This should be fixed since the build 2020-05-10 which is the first build of version 0.2.

Very last version can be found here: UniversalScanner (Portable) or here: UniversalScanner (Installer).

Do you mind to double check if it is now working?

Note: You can also see all addresses of the found devices, including ZeroConf ones by tweaking this value : HKEY_CURRENT_USER\Software\UniversalScanner\ForceZeroConf (key will be created at first launch of new version)

Thanks

Julien

Agree
Disagree
Informative
Unhelpful
Funny

Julien,

Is there a way to define the IP address pool the scanner will scan?

Agree
Disagree
Informative: 1
Unhelpful
Funny

Hi Steven,

For remind and to be clear on how it works: it is not using a ICMP scan but a bunch of broadcast and multicast protocols in Ipv4. Therefore, it should detect everything (if protocol is known) without specifying an IP range.

Today, there is no filter about this detection results, the protocol used, nor the network interfaces scanned; you have to filter it out after you got the full list of devices.

The method I explained in a previous post was to perform a scan, and then export the results in CSV (right-click on the list), then within an Excel, you should be able to filter out some IP range using the right formula.

You can also sort the device by the order list of the IP address which might also helps to filter.

Julien

Agree
Disagree
Informative
Unhelpful
Funny

The issue I am having is when I am connected to a large enterprise network with multiple VLANs, I can not direct the tools attention to one specific network. The tool only sees the IP scheme given to my interface by the VPN. It does not discover devices on the other networks so I have no results to filter through.

Agree
Disagree
Informative: 1
Unhelpful
Funny

Do you run the tool after you mount the VPN?

Order is important as the tool will start to listen before you click Scan button : when you run it, the listening sockets are immediatly opened on all interfaces found on the machine.

Also you need to check with your IT department if they allow multicast traffic to go through the VPN, if not the only option is to have a "relay" machine you can access remotly on your lab and on which you can run the tool.

Agree
Disagree
Informative
Unhelpful
Funny

I will check on these and get back with you. Currently I am executing the VPN from my house to my firewall. From there my firewall has a tunnel into my customer's firewall. I will also check and see if multicast is allowed. Thank you for your work on this project.

Agree
Disagree
Informative
Unhelpful
Funny

Thanks for your tests.

You can challenge your VPN via the Onvif Device Tool or specific IP vendor tools (Dahua, Axis, Hik, etc.) to see if is detecting the devices throught VPN, that is a good checkpoint.

Agree
Disagree
Informative
Unhelpful
Funny

I just scanned my brother's house since that is where I happen to be. He has several Wyze cameras that did not show up, but it did find all of his Wemo devices and his printer, plus his Google devices. I think the .21 and .22 are part of his Eero system, but I cannot confirm them. I wasn't sure if any of this would be useful to you or not, but data is data right?

IPVM Image

Agree
Disagree
Informative: 1
Unhelpful
Funny

Thanks for your test & report.

The scan looks to works normally indeed. I don't know what kind of protocol Wize uses in order to discovery the cameras but it does not look to be an open standard.

I haven't find any tool online, the detection looks to be only via mobile application.

Printers use WSDiscovery indeed, and UPnP is widely used for network devices.

Agree
Disagree
Informative
Unhelpful
Funny

Thanks all for you tests.

I released a new version today, with which you can do some tweaking in the registry (HKEY_CURRENT_USER\Software\UniversalScanner).

Warning: from this version, by default, devices will appears only once in the list if it's detected by several protocols such UPnP or ONVIF (you can orverride this behavior and get whole list by changing the value ForceGenericProtocols in registry);

Axis issue with ZeroConf IP address should be fixed (value ForceZeroConf allow you as well to see all addresses of the found devices).

IPv6 can be supported for some specific vendors (it is disabled by default, you need to change value EnableIPv6 in regisry to enable it).

I removed "a quirk" mode for old Dahua devices, therfore some old Dahua devices might be not detected if your OS is recent.*

*Please let me know if you are impacted too much by this, I can add a registry entry to force enabling this quirk mode.

Very last version can be found here: UniversalScanner (Portable) or here: UniversalScanner (Installer).

Still, supports the open protocols below:

  • SSDP (UPnP)
  • WS-Discovery (ONVIF)
  • DNS-SD (Zeroconf)

And new vendor discovery protocols list:

  • Axis (should have sharper detection)
  • HikVision
  • Dahua (might be detect less very old device on newer OS)
  • Bosch
  • Hanwha
  • Vivotek
  • Sony
Agree
Disagree
Informative: 2
Unhelpful
Funny

Awesome! Now it properly discovers my Hanwha devices, even with the Wisenet Device Manager tool running.

Thanks for this.

Agree
Disagree
Informative: 1
Unhelpful
Funny: 1

Discovered as UPnP or WSDiscovery? Or as Hawha ?

If it is discovered as Hanwha, it should not works with Wisenet Device opened same time lol

Try to search on Wisenet Device, maybe it is now that one that does not work.

The first application launched should normally "book" the UDP response port (7711) and not share with the other (limitation for Hanwha as it uses static response port).

So it should depend on the order you launch them.

To see which app is in use of the current port of Wisenet protocol, you can use the following dos commands:

IPVM Image

For example, here it is UniversalScanner which hold the port 7711.

Agree
Disagree
Informative: 1
Unhelpful
Funny

They showed up as Hanwha devices. See screenshot below.IPVM Image

I have both applications open and scanned back and forth and they both show up.

I ran the commands (thanks for that), and it initially showed it hooked to the Universal Scanner. They I scanned in Wisenet Device Manager, and now they both show up in the netstat.

IPVM Image

Agree
Disagree
Informative: 1
Unhelpful
Funny

So it is Wisenet tool that support this function, not yet UniversalScanner.

If you run UniversalScanner as the second it won't work, but here you run it as as first; I think this is why it is working.

But, despite of the article I shared previously, port sharing looks to works, at least good enough to - try to - detect devices on two tools at the same time.

I will add this function then to the next release for relevant protocols*, with a registry key leave the ability to disable this feature in case of problem.

* Protocols using static port for listening answers are for now:

  • Hanwha
  • Panasonic
  • Dahua (old devices)

Thanks for your tests and feedback!

Agree
Disagree
Informative
Unhelpful
Funny

I forgot Bosch in the affected protocol list.

I did a test and it might works for:

  • Hanwha
  • Panasonic
  • Bosch

Port sharing won't work for Dahua (old devices) because when port 5050 is in use, it is by a Windows system service.

Gift, I make a fresh release with this function for you:

Release UniversalScanner 2020-05-11 · julienblitte/UniversalScanner · GitHub

Enjoy.

Agree
Disagree
Informative
Unhelpful
Funny

Is it that the tool detects the manufacturer? So if it’s eclipse cctv but it’s made by Uniview, it will say Uniview?

Also I think Uniview should be added

Agree
Disagree
Informative
Unhelpful
Funny

The tools does not detect the vendor itself, it sends a bunch of detection requests on several protocols. The first column actually isn't the device model but the protocol used to detect the device (in fact the one with highest priority which recieved a response).

As far as I know, the discovery tool of UniView is using WSDiscovery and not a proprietary protocol, so it should appears as WSDiscovery item.

I am afraid WSDiscovery won't offer a lot of details, in the list, especially you won't know the device model of the device (only `NetworkVideoTransmitter`).

Agree
Disagree
Informative
Unhelpful
Funny

Hi Julien,

Thanks for your software!

We have a couple of 360 Vision CCTV cameras on-site and your software doesn`t discover it (I used the latest version).

The ONVIF Device Manager and the Advanced IP scanner tool can find them.

Here is the link to 360 Vision CCTV download page if you need to see their discovery tool (by the firmware section): link

Thanks, Geza

Agree
Disagree
Informative: 1
Unhelpful
Funny

Hi Geza,

The discovery protocol of 360 Vision looks to be a broadcast on port 3600 with text commands finished by a Line Feed "\n".

Even, if I can capture the discovery request, I need more information to integrate and implement this protocol, especially a network capture to be able analyze the response format from the devices.

If you are interested, could you please follow this procedure and send me the privately the data?

By the way, the discovery tool itself is based on NodeJs (very surprising choice for an application) the weight for this tool is around 150 MB with embedded JS framework!

Regarding the non-detection of your cameras, please note that:

* AngryScanner uses ICMP (ping) which UniversalScanner does not;

* I suspect their ONVIF stack to be limited only to specific requests (especially ONVIF Device Manager), so for me it could be a broken implementation.

For ONVIF detection, could you try this very last version here (or here for installer version) with this registry key changed:

HKEY_CURRENT_USER\Software\UniversalScanner\onvifVerbatim to value 1?

Thanks,

Julien

Agree
Disagree
Informative
Unhelpful
Funny

Hi Julien,

I sent you a screenshot in email, with registry key changed its discovered the 360 vision cameras.

Network capture left to do will email that too.

Thank you!

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

A good idea, access control devices would be good as well, just my 2 cents.

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

Hi Chris,

Looks good idea, why not!

But I need help to do such integration as I do not have these kind of device on my table.

If would like to participate and give me an hand, you can follow this documentation and send me the collected data for me to integrate devices you would like to see in this small tool.

Agree
Disagree
Informative
Unhelpful
Funny

Hi,

With great help of Geza Gyorfi, I have added the discovery protocol of 360Vision devices. Thank you!

The old Dahua devices are now better detected as I have added broadcast detection (in addition to multicast) to detect them.

Very last version can be now here:

UniversalScanner (Portable) or here: UniversalScanner (Installer).

It supports the open protocols below:

  • SSDP (UPnP)
  • WS-Discovery (ONVIF)
  • DNS-SD (Zeroconf)

And private vendor discovery protocols list:

  • Axis
  • HikVision
  • Dahua
  • Bosch
  • Hanwha
  • Vivotek
  • Sony
  • 360Vision

Anyone else that would like me to add a new private protocol, you can follow this procedure, and send me privately the data (captures might contains personal information).

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

Hello,

I would like to thanks especially John Scanlan from IPVM who helped me, with his test environnement and IPVM products, to validate Panasonic protocol and collect enough data to implement Ubiquiti discovery protocol. Thanks!

Current version can be now here:

UniversalScanner (Portable) or here: UniversalScanner (Installer).

It supports the open protocols below:

  • SSDP (UPnP)
  • WS-Discovery (ONVIF)
  • DNS-SD (Zeroconf)

And private vendor discovery protocols list:

  • Axis
  • HikVision
  • Dahua
  • Bosch
  • Hanwha
  • Vivotek
  • Sony
  • 360Vision
  • NiceVision
  • Panasonic
  • Arecont

If I found the time this week-end, I will try to publish a new release with with the support of Ubiquiti protocol.

You can still help me to add a new private protocol following this procedure, and send me privately the data (as captures might contains personal information).

Agree
Disagree
Informative
Unhelpful
Funny

Hello,

Thanks again to IPVM lab environement, I was able to implement Ubiquiti discovery protocol.

Newest version with this discovery protocol can be now here:

UniversalScanner (Portable) or here: UniversalScanner (Installer).

It supports the open protocols below:

  • SSDP (UPnP)
  • WS-Discovery (ONVIF)
  • DNS-SD (Zeroconf)

And private vendor discovery protocols list:

  • Axis
  • HikVision
  • Dahua
  • Bosch
  • Hanwha
  • Vivotek
  • Sony
  • 360Vision
  • NiceVision
  • Panasonic
  • Arecont
  • Ubiquiti

The discovery was tested on only one antenna so if any others members could kindly check on their lan if they find well their Ubiquiti antennas and share results, this would be appreciated.

Agree
Disagree
Informative: 1
Unhelpful
Funny

It's about time someone made a tool like this. Great job!

Agree: 1
Disagree
Informative
Unhelpful
Funny

How is this better or different than Fing Desktop? Fing Desktop | Network toolkit and scanner | Fing

I applaud your efforts.

Agree
Disagree
Informative
Unhelpful
Funny

This also searches different subnets.

Looks pretty cool

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

Indeed, it is using directly the vendors protocols (via multicast and broadcast) and not classic "ping". Therefore you can find some devices out of your current subnet and it should be much faster.

Agree
Disagree
Informative
Unhelpful
Funny

Hello IPVM,

A newest version here:

UniversalScanner (Portable) or here: UniversalScanner (Installer).

You can now clear the list with the right click option and you can still export results as CSV file.

It supports the open protocols below:

  • SSDP (UPnP)
  • WS-Discovery (ONVIF)
  • DNS-SD (Zeroconf)
  • GigE Vision (industrial cam protocol)

And private vendor discovery protocols list:

  • Axis
  • HikVision
  • Dahua
  • Bosch
  • Hanwha
  • Vivotek
  • Sony
  • 360Vision
  • NiceVision
  • Panasonic
  • Arecont
  • Ubiquiti

As gadget I have added also

  • Google Cast
  • VStarCam

I managed to detect also these brands with the open protocols :

  • Uniview: ONVIF/WS-Discovery
  • Flir: UPnP/SSDP and GigE Vision
  • Siqura: UPnP/SSDP and ONVIF/WS-Discovery
  • Mobotix: ONVIF/WS-Discovery

You have a bunch of advanced options in registry (IPv6, show all protocols, show auto-config IPs, enhance ONVIF compatibility, etc.), more details here.

Agree
Disagree
Informative
Unhelpful
Funny