The answer also includes useless data such as unused XML schemas, it is also allowed but useless and also partially the cause of the oversize of the payload. Fragmentation is done at IP level, it is allowed of course but not really common (makes me think their UDP stack is homemade). The WS-Discovery answer payload is bigger than the maximum so there is packet fragmentation. The camera implementation is not very usual: Then you can follow this procedure to collect enough information for me to integrate a new private detection protocol. You know another vendor discovery protocol that would be good to have integrated into the tool? I was thinking to make also a Linux software port later (would be in command line) for installers who install/use camera over Linux. You have a bunch of advanced options in registry (IPv6, show all protocols, show auto-config IPs, enhance ONVIF compatibility, etc.), more details here. Eden Access Control (sub-controller): Lantronix. Siqura: UPnP/SSDP and ONVIF/WS-Discovery. I managed to detect also these brands with the open protocols : Today, it supports the open protocols bellow: You will need Windows system with dotNet v4.5.2 
julienblitte/UniversalScanner (added protocol Eaton).
julienblitte/UniversalScanner (added protocol GCE, fixed Dahua DSS issue).julienblitte/UniversalScanner (added contextual menu).julienblitte/UniversalScanner (added protocol Advantech).julienblitte/UniversalScanner (added version notifier).
0 kommentar(er)
