Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-2725

Latest OPNsense identified as FreeBSD

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • None
    • None
    • None

    Description

      Hi,

      latest OPNsense switched from an older snmp daemon to Net-SNMP (both currently supported but the old daemon announced end-of-life) and when using the Net-SNMP plug-in, the OS is identified as FreeBSD:

      FreeBSD xxx 11.1-RELEASE-p11 FreeBSD 11.1-RELEASE-p11 116e406d37f(stable/18.1) amd64

      While this is not generally wrong, it was better when it was identified as a Firewall and automatically categorized.

      Attachments

        Issue Links

          is mentioned by

          Bug - A problem which impairs or prevents the functions of the product. OBS-3745 OPNsense (NET-SNMP) identified as FreeBSD

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            [OBS-2725] Latest OPNsense identified as FreeBSD
            landy Mike Stupalov added a comment -

            Added in r9341.

            landy Mike Stupalov added a comment - Added in r9341.
            accelerated Nicolaj added a comment -

            Hi,

            access is not possible but here is the output (stripped by some IP infos that shouldn't be required here anyways).

            snmp-output.txt

            accelerated Nicolaj added a comment - Hi, access is not possible but here is the output (stripped by some IP infos that shouldn't be required here anyways). snmp-output.txt
            landy Mike Stupalov added a comment -

            accelerated Can you provide temporary snmp access to device? (if yes, write me to mail mike@observium.org)

            Or attach output for full snmpwalk:

            snmpwalk -On -v2c -c <community> <hostname> .1

            landy Mike Stupalov added a comment - accelerated Can you provide temporary snmp access to device? (if yes, write me to mail mike@observium.org) Or attach output for full snmpwalk: snmpwalk -On -v2c -c <community> <hostname> .1
            adama Adam Armstrong added a comment -

            Our ability to autodetect OPNsense relies on the string "OPNsense" to be present in the sysDescr.

            You can probably occumplish this by putting OPNsense in the device's own hostname.

            adama Adam Armstrong added a comment - Our ability to autodetect OPNsense relies on the string "OPNsense" to be present in the sysDescr. You can probably occumplish this by putting OPNsense in the device's own hostname.
            accelerated Nicolaj added a comment -

            I must correct myself: switching back to the old plug-in doesn't actually solve this. This affects the latest OPNsense:

            OPNsense 18.1.12-amd64
            FreeBSD 11.1-RELEASE-p11
            OpenSSL 1.0.2o 27 Mar 2018

            accelerated Nicolaj added a comment - I must correct myself: switching back to the old plug-in doesn't actually solve this. This affects the latest OPNsense: OPNsense 18.1.12-amd64 FreeBSD 11.1-RELEASE-p11 OpenSSL 1.0.2o 27 Mar 2018

            People

              landy Mike Stupalov
              accelerated Nicolaj
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: