Dwarfguard version 1.4.0 "Afterparty 4 (Keeper BETA 4)"

• status: planned
• released at: not yet
• supported modes of operation:
  • production: Yes but being BETA some features may not work to full extent
  • free usage: Yes but available to BETA partners only
    • 1.4.0 BETA build - will be available to BETA partners only
      • MD5sum: TBD
      • SHA1sum: TBD
• supported deployment modes:
  • DT SAAS / DT Cloud / DT Server Managed: No / No / Yes
  • Partner SAAS / Partner Cloud / Partner Server Managed: No / No / Yes
  • Customer self-managed: Yes
  • Private network: Yes
• support planned: BETA
  • See release table
• upgrade supported from:
  • Full upgrade from 1.3.0_BETA Afterparty 3 (2.0 Keeper BETA 3)
• target audience: BETA partners
• showcase video: N/A

Release notes - known issues, changes since last release

• NOTE: this is likely the last or pre-last beta before the Dwarfguard 2.0 release.

• Version 1.4.0_BETA is a beta version containing functionality to be released as production in Dwarfguard 2.0.0.

• This is a published BETA release, meaning that:

  • It is supported (to a certain extent).
  • Upgrade path from previous BETA is supported.
  • Upgrade path to next BETA will be provided.
  • Upgrade path from last BETA in the 1.y.0 chain to 2.0.0 will be provided.

• It is still a BETA release, meaning that while the user gets the latest features, some may not be working in full and as the product has not been tested as extensively as a production release, the risk of running into bugs is considerably higher than when using a production version.

Featured changes

• This is fourth BETA release for 2.0.
• List of features planned for 2.0.0 is not disclosed here.
• The particular changes between BETA3 and BETA4 are available in the "About -> Release Notes" after upgrade.

Known issues (updates with bugs being reported)

NOTE: only brief description of known issues is provided on this page

• Not fixed from BETA3: It is not possible to use snmp_subtype in devices table as that breaks the table, showing it as empty.
  • Workaround: do not enable the snmp_subtype column (it is not enabled by default). If you enable it and it breaks the table, simply disable it in settings, the table will return to fully functional state.
  • This appears if you upgrade from BETA2 -> BETA3 -> BETA4. In case you install BETA4 as new, the bug should not manifest itself. Please report if it appears anyway.