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

OS: HardenedBSD

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • OS
    • None

    Description

      Source patch and OS icon files for HardenedBSD OS-variant.

      HardenedBSD is a security-enhanced fork of FreeBSD.

      https://hardenedbsd.org

       

      (svn diff @ trunk/rolling r12297)

      Attachments

        1. hardenedbsd_2x.png
          hardenedbsd_2x.png
          6 kB
        2. hardenedbsd.png
          hardenedbsd.png
          2 kB
        3. hbsd-sample.png
          hbsd-sample.png
          132 kB
        4. opnsense-sample.png
          opnsense-sample.png
          115 kB
        5. os-hbsd.patch
          0.6 kB

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. OBS-4246 distro_ver too short for HardenedBSD

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

          Activity

            [OBS-4257] OS: HardenedBSD
            landy Mike Stupalov added a comment -

            OPNSense have different "purpose" and many additions (except kernel).

            Anyway, I think you use stable train, all changes initially in rolling train:
            https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

            landy Mike Stupalov added a comment - OPNSense have different "purpose" and many additions (except kernel). Anyway, I think you use stable train, all changes initially in rolling train: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains
            nodefield Ilkka Myller added a comment -

            Fixed the issue:

            Target systems were using older distro script from pre-r12276 and serving that with snmpd:

            extend .1.3.6.1.4.1.2021.7890.1 distro /usr/local/bin/distro

             

            After upgrading the distro script HardenedBSD is detected properly.

            nodefield Ilkka Myller added a comment - Fixed the issue: Target systems were using older distro script from pre-r12276 and serving that with snmpd : extend .1.3.6.1.4.1.2021.7890.1 distro /usr/local/bin/distro   After upgrading the distro script HardenedBSD is detected properly.
            nodefield Ilkka Myller added a comment - - edited

            vs

            nodefield Ilkka Myller added a comment - - edited vs
            nodefield Ilkka Myller added a comment -

            Just tested with fresh r12298 and HBSD detection does not seem to work as definition is missing from bsd.inc.php

            Still uses FreeBSD branding and icon.

             

            Comparing to OPNSense which is nearly identical FreeBSD fork to HBSD and it works ok.

             

             

            nodefield Ilkka Myller added a comment - Just tested with fresh r12298 and HBSD detection does not seem to work as definition is missing from bsd.inc.php Still uses FreeBSD branding and icon.   Comparing to OPNSense which is nearly identical FreeBSD fork to HBSD and it works ok.    
            nodefield Ilkka Myller added a comment -

            I tried to learn how to configure HardenedBSD as a distro of FreeBSD for Observium, but found out that in bsd.inc.php there already seems to be multiple entries (OPNSense, XigmaNAS etc.) that are also very close FreeBSD-variants,using FreeBSD kernel and configured similarly as an individual OS - just like in my patch file.

             

            Looking forward for your solution how to add a distro for existing OS with custom icon because I could not find any examples for that in Observium Professional trunk includes/definitions/os

            nodefield Ilkka Myller added a comment - I tried to learn how to configure HardenedBSD as a distro of FreeBSD for Observium, but found out that in bsd.inc.php there already seems to be multiple entries (OPNSense, XigmaNAS etc.) that are also very close FreeBSD-variants,using FreeBSD kernel and configured similarly as an individual OS - just like in my patch file.   Looking forward for your solution how to add a distro for existing OS with custom icon because I could not find any examples for that in Observium Professional trunk includes/definitions/os
            landy Mike Stupalov added a comment -

            Improved in r12298.

            landy Mike Stupalov added a comment - Improved in r12298.
            nodefield Ilkka Myller added a comment -

            FYI: HBSD can also be detected with 

            kernel => HARDENEDBSD

            nodefield Ilkka Myller added a comment - FYI: HBSD can also be detected with  kernel  =>  HARDENEDBSD
            nodefield Ilkka Myller added a comment -

            My intention was not to separate as new OS but as a FreeBSD variant.

             

             

             

            nodefield Ilkka Myller added a comment - My intention was not to separate as new OS but as a FreeBSD variant.      
            landy Mike Stupalov added a comment -

            I not see reasons for split it into separate os, because it's a just FreeBSD with enhancements.
            Mostly it's just changed kernel..

            But I can set distro name to HardenedBSD and add icon for it.

            landy Mike Stupalov added a comment - I not see reasons for split it into separate os, because it's a just FreeBSD with enhancements. Mostly it's just changed kernel.. But I can set distro name to HardenedBSD and add icon for it.
            bot Observium Bot added a comment -

            General questions and device support can be discussed in our Discord channel, click here to join.

            Please make and attach additional information about the device:

            • full snmp dump from device: 

              snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
              		 
              snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

              If device not support SNMP version 2c, replace -v2c with -v1.

            • If you have problems with discovery or poller processes, please do and attach these debugs: 

              ./discovery.php -d -h <device>
              		 
              ./poller.php -d -h <device>

            • additionally attach device and/or vendor specific MIB files

            This comment is added automatically.

            bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

            People

              landy Mike Stupalov
              nodefield Ilkka Myller
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: