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.
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
What do you think about adding discovery for common network devices like Ubiquiti and other common wireless manufacturers?
Julien, thanks for sharing. Here is Julien's Github repo for his Universal Scanner.
It's so good to see someone take this on!
Just tried it and works great for what is on my network.
Work well, detects everything very fast and lists the unique ID.
Thanks!
04/28/20 12:33am
Very cool. I have not had a chance to check it out yet, but hope to later this week.
IPVMU Certified | 04/28/20 04:05am
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
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!
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!
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
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!
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.
I have a ton of Hanwha cameras and they don't show. I am using my WiFi...? I love the idea of this tool!!
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.
Second the Linux comment! Cool tool.
This is a brilliant idea, nice work!
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.
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?
Thanks,
Julien
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).
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
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?
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
Julien,
Is there a way to define the IP address pool the scanner will scan?
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.
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?
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
Awesome! Now it properly discovers my Hanwha devices, even with the Wisenet Device Manager tool running.
Thanks for this.
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:
For example, here it is UniversalScanner which hold the port 7711.
They showed up as Hanwha devices. See screenshot below.
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.
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
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`).
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
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
A good idea, access control devices would be good as well, just my 2 cents.
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).
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).
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.
It's about time someone made a tool like this. Great job!
How is this better or different than Fing Desktop? Fing Desktop | Network toolkit and scanner | Fing
I applaud your efforts.
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.
Newest Discussions
| Discussion | Posts | Latest |
|---|---|---|
|
Started by
Undisclosed Integrator #1
|
5
|
2 minutes by George Peffer |
|
Started by
Carl Stoffers
|
5
|
less than a minute by Dan Kosco |
|
Started by
John Honovich
|
10
|
about 13 hours by Undisclosed #3 |
|
Started by
AJ Smith
|
13
|
about 3 hours by Undisclosed Integrator #3 |
|
BREAKING - FCC Bans Dahua & Hikvision In Final Vote + New Proposal To Revoke Existing Authorizations
(3)
Started by
Conor Healy
|
3
|
less than a minute by Jacob Hengel |
