opnsense/plugins

AI Summary: This feature request for the OPNsense Chrony plugin aims to enhance security by allowing users to edit the `chrony.keys` file directly through the UI. Currently, there are no widgets to manage this file, preventing users from configuring key-based authentication. The proposed solution involves adding a boolean checkbox and an input field to the Chrony UI for this purpose.

AI Summary: The GitHub issue reports a missing 'resourceId' field in the configuration form for Azure Dynamic DNS within the `os-ddclient` plugin. When 'azure' is selected as the service type, the form reconfigures but omits this crucial field, preventing users from properly configuring Azure DNS zones.

AI Summary: The user reports that the Postfix plugin's greeting uses only the hostname, not the fully qualified domain name (FQDN), when its own hostname field is left empty. This occurs even if the system's general settings define a FQDN. The expected behavior is for Postfix to default to the system's FQDN in its greeting.

AI Summary: The `os-bind` plugin's UI currently restricts DNS forwarders to IP addresses only, preventing users from specifying custom ports like `127.0.0.1:5353`. Attempts to do so result in a validation error. The user requests the ability to configure DNS forwarders with non-standard ports through the UI.

AI Summary: Implement GUI support within the OPNsense FRR plugin to manage multiple OSPF and BGP processes. This involves extending the existing plugin's interface to allow users to configure and control independent routing instances, enabling features like inter-process route import/export and filtering.