* 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>
* Adding basic support for Datacom DmOS devices.
Adding basic support for Datacom DmOS devices. These devices includes OLTs and Switches developed by Datacom (Teracom Telematica Ltda):
https://www.datacom.com.br/en/produtos/dmos
All the product models which uses this OS (DmOS) have the same specific sysObjectID = .1.3.6.1.4.1.3709.1.2.137 So new future devices will also have this OID.
* Rename DMOS-SYSMON-MIB.mib to DMOS-SYSMON-MIB
removing extension ".mib" from the filename
* Rename DMOS-TC-MIB.mib to DMOS-TC-MIB
removing extension ".mib" from the filename
* JSON files
json files related to the snmprec files sent in an earlier commit.
* Update dm4770 test data
* Fix mib_dir
* Update datacom-dmos.yaml
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Fixed BGP Remote peer link and graph in Routing Overview, or just static text when not a device in LibreNMS
* Added extra space
* Reverted back to overlibLink (due to BGP update graphs on hover)
* Added extra space
* Remove graph for remote peer, as it is falsely (showed earlier the Updates Graph for local peer)
* Removed unnecessary/unused code
* Remove graph for remote peer, as it is falsely (showed earlier the Updates Graph for local peer), replaced with just a DeviceLinks
* Change Url::deviceLink to return $text if the device doesn't exist. Default to ''
Import some of the things to improve readability.
* update phpdoc
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Add support for FiberStore "data center" switches
FiberStore has two different model lines of switches, and this adds
support for the "data center" line. This was configured and tested
against the N5860-48SC model.
The MIBs are from FiberStore's website, with the exception of the
FS-FIBER-MIB (the website version is a little behind the software, so
support sent me an updated version and should be getting it published
soon).
This does not currently handle 4x10 or 4x25 QSFP+ light levels, as I
don't currently have any to test against.
* Add test data for fs-switch-dc
This is from a production switch, with data filtered to just the
FiberStore enterprises OID.
* Update fs-switch-dc_fs-switch-dc.json
* correct processors warn field name
* Update fs-switch-dc_fs-switch-dc.json
* Update fs-switch-dc.yaml
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
