Dwarfguard version 1.0.3 "party patch3"

• status: obsolete, replaced by patch release 1.0.4
• released at: 2025-06-06
• supported modes of operation:
  • production: Yes
  • free usage: Yes
    • 1.0.3 build link
      • MD5sum: 842ed1926bd67c85cf9d7984aac9aada
      • SHA1sum: ef8a46b73256c67039d855d02f22007f0e12c7c3
• supported deployment modes:
  • DT SAAS / DT Cloud / DT Server Managed: Yes / No / Yes
  • Partner SAAS / Partner Cloud / Partner Server Managed: Yes / No / Yes
  • Customer self-managed: Yes
  • Private network: Yes
• support planned: until 1.1.0 release
  • See release table
• upgrade supported from:
  • Dwarfguard 1.0.2 - full upgrade
• target audience: general
• showcase video: Not yet updated, see 082 video

Release notes - known issues, changes since last release

Version 1.0.3 is a patchlevel of the last stable release. No new features are introduced.

Featured changes

• Fix for invalid configuration profile creation when device provides invalid data.
• Sanity check when running on very low performance container - exit when DB is not connected in 10 seconds from start instead of running in partially functioning mode.
• Improved Grafana integration handling when running integration.

Known issues (updates with bugs being reported)

• Long startup script in Advantech router causes problems with profile save, make configuration clone from this device to another not possible.
  • Reported: 2025-09-08
  • Status: Fix ready for 1.0.4
  • Fixed at: 2025-09-12
  • Description: A startup script longer than 4096 bytes causes error when being saved to the DB, making configuration profile for that device broken. This device does not have a valid configuration profile and thus cannot be used for CFG cloning.
  • Impact: Configuration cloning + slightly increased log size
• User override setting for some server parameters does not work
  • Reported: 2025-09-13
  • Status: Fix ready for 1.0.4
  • Fixed at: 2025-09-14
  • Description: On "System Settings" under "Dwarfguard System Configuration" some of the items (numeric ones) are not settable, the input field being grayed out. Also, when any change is done, it persists only until service restart - then, it needs to be re-set.
  • Impact+Workaround: The settings to be persistent must be done by server admin using the "dwarfg.ini" file instead of the web-settable "user.ini" (the server admin file (dwarfg.ini) takes precedence but it can be edited only on command line).