2 answers
- 10-1
Thanks Mark
I'm very wary of OpenAudIT upgrades after moving from V1.8.x to V2 a while back - only to find the database schema had completely changed and all our custom queries and reports were trashed as a result. Ended up reverting back and eventually re-implementing from scratch - it was simpler
STEVE
Add your comment... - 10-1
Hello Steve,
I strongly recommend you upgrade to v3.0.2, as it includes several very significant improvements to auditing speed (50x faster audits) and troubleshooting. You can get the installer HERE: https://opmantek.com/network-tools-download/open-audit/
I cannot speak specifically to 2.2.7, however in 3.0.2 using system.ip will provide an unpadded IP in the GUI and both the unpadded and padded version in the export. i.e.
"id","icon","type","name","ip","ip_padded" "189","unknown","unknown","ip-10-152-0-5","10.152.0.5","010.152.000.005"
SELECT system.id AS `system.id`, system.icon AS `system.icon`, system.type AS `system.type`, system.name AS `system.name`, system.ip AS `system.ip` FROM system WHERE @filter AND (system.type = 'unknown' OR system.type = 'unclassified')
This webinar might be of help: https://opmantek.com/webinar-developing-custom-queries-with-open-audit/Add your comment...
Hi
In V1 of OpenAudit it was possible to configure the output of query results via the query XML config files to de-pad IP addresses, so 010.001.050.045 appeared as 10.1.50.45
I've written a query to report on DHCP addresses in use, and found that this feature has been deprecated in V2; and I'm struggling to find any documentation on how to achieve de-padding with this version. I'm currently using OpenAudIT 2.2.7 community edition.
Can anyone help or point me in the right direction please
Thanks
STEVE