* Added models in hirshmann definition file
* Added Hirschmann_ms4128.snmprec to ~/tests/snmpsim
* Generic SysObjectID
* Some devices are not replying with all the table data
* fix tests accordingly
* add more sensors
* Move Temperature to YAML
Discovery and polling are currently buggy, this will fix it and make it capable of handling more than one temp sensor.
History of temperatures will be lost here.
---------
Co-authored-by: PipoCanaja <38363551+PipoCanaja@users.noreply.github.com>
* fix regex for hardware and version
* updated test data
* Update hwg-ste2.snmprec
* Create hwg-ste2.json
---------
Co-authored-by: PipoCanaja <38363551+PipoCanaja@users.noreply.github.com>
* Added support of new OS for NTP/PTP systems:
- support of Meinberg microSync OS (mbg-meinbergos)
- support of Safran (Orolia) SecureSync OS (orolia-securesync)
- support of Adva OSA (5401 and 5412) OS (adva_fsp150cm)
* Fix Safran (Orolia) images
* Added Test-unit JSON files
* Changed SVG images
* Changed SVG images
* Changed SVG images
* Add more filter options for the BGP API endpoint. bgp_descr, bgp_state and bgp_adminstate
* typo and lint
* Adress family filter would also be helpful. casting AS1234 Like inputs to plain numbers
* linting again...
With tools installed, the string provided by ESXi contains a lot more information. In 8.9, Red Hat have further extended the string to include a machine readable string, parsable by tools that are compatible with OVAL:
Linux 4.18.0-513.5.1.el8_9.x86_64 Red Hat Enterprise Linux 8.9 (Ootpa) 8.9 Red Hat Enterprise Linux 8.9 (Ootpa) cpe:/o:redhat:enterprise_linux:8::baseos
Disc is typically used for optical media, not hard disks (so unlikely
to encounter discs in mdraid related circumstances).
mdadm and friends use the disk spelling, the host script also shows
shows this `"disc_count": $(maybe_get "${mdadmSysDev}/md/raid_disks"),`
Fixing the variable names as well would be nice, but that change would
be a lot bigger and probably break things as it would need host script
adjustment synchronising and all that, but I think we can at least
change the cosmetic spelling.
https://en.wikipedia.org/wiki/Spelling_of_disc
* Disable GET login by default
GET login allows users to put username and password in the url, this is helpful for displays where you cannot login interactively.
Unfortunately, the plaintext password will be in the access logs.
GET login also allows brute force attacks against your install.
* Apply fixes from StyleCI
---------
Co-authored-by: StyleCI Bot <bot@styleci.io>
* Update Zyxelnwa.php
Discovering wireless clients on all bands
* Update ZYXEL-ES-WIRELESS
Replace '_' by '-' as it is a bad practice to use underscores in values
* Update Zyxelnwa.php
* Update ZYXEL-ES-WIRELESS
* Update zyxelnwa.snmprec
* Create zyxelnwa.json
* Update Zyxelnwa.php
* Update zyxelnwa.snmprec
* Update ZYXEL-ES-WIRELESS
* Update Zyxelnwa.php
* Update zyxelnwa.snmprec
* Update Zyxelnwa.php
* Update Zyxelnwa.php
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Increase max package name length to 80 characters
One of my packages has a name of 65 characters. LibreNMS limits package names to 64 characters (`varchar(64) NOT NULL`). As the name of my package is truncated, polling fails with the following error:
```
Error polling unix-agent module for http-jglt01.gmdo.ha.cyberfusion.cloud. PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '458-python3-cyberfusion-cluster-configurations-redirect-fast-...' for key 'packages_device_id_name_manager_arch_version_build_unique' in /opt/librenms/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:117
```
There is no well-defined max package name length. An email on the `debian-devel` mailing list (https://lists.debian.org/debian-devel/2011/04/msg00981.html) states that the length of package names should not exceed 40 characters, and that the length of file names should not exceed 90 characters, but these limits are not enforced. Lintian does not check package name length, but does check that file name length does not exceed 80 characters (tag 'package-has-long-file-name').
Summarised: there are no well-defined and enforced limits, and those that Lintian advices differ from the aforementioned post on the `debian-devel` mailing list. Therefore, I have landed on the semi-random limit of 80 characters (which the original limit of 64 characters seems to be as well).
* Create 2023_11_04_125846_packages_increase_name_column_length.php
* Update db_schema.yaml
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Fix Fortinet HA status polling
* Test data
* Update fortigate.inc.php
* Update fortigate.inc.php
* Update all test data
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
