firewall: group filter rules by type and category
Always group rules by their priority/type in the filter grid and reuse the
same rule type metadata for both bucket labels and icons. When tree view is
enabled, categorized non-automatic rules are grouped one level deeper by
category, while automatic and uncategorized rules remain directly below their
rule type bucket.
This keeps the default view structured without relying on a mixed flat/tree
array and makes the tree toggle an additive category grouping layer.
Reporting: Settings: convert to MVC (#10337)
Move all relevant toggles and actions to their respective pages with associated forms and endpoints.
Removes the Netflow Repair button as well.
Firewall - fix interface sortng by value for live-log and groups, closes https://github.com/opnsense/core/issues/10348
We might consider moving the sorting logic to BaseListField at some point as most cases expect sort by value anyway and we only have a couple of exceptions to that logic.
Kea: Hook up reservation.next_server (#10344)
This field was added to the Kea dialogReservation4.xml form in
https://github.com/opnsense/core/pull/8890, however this specific option
was not properly hooked up and did not generate the expected config,
preventing netboot scenarios that rely on next-server from being set on
a per-reservation basis (the per-subnet variant of this option does work
fine).
This commit hooks it up to generate the expected "next-server" Kea
config entry on a per-reservation basis.
mvc: remove grouped ModelRelationField option handling (#10339)
The group option collapsed multiple related model rows into a single
display entry while still storing the UUID of one concrete source row.
This makes the selected relation dependent on iteration order and is not
a stable representation of the grouped object.
References:
https://github.com/opnsense/core/commit/fe571ac442efe76c3a1efd3e6f90b8ec4cb6e7bd
Frr was the only consumer (I could grep in core and plugins, don't know if external ones exist), I reworked how the relationship is displayed there to make it more obvious to the user how items relate to each other, and also prevent that the wrong items get deleted. Configs should be more coherent now.
It's also not perfect, but more "obvious" lets say.
It also helps with the addition of internalModelUseSafeDelete in FRR.
opnsense/plugins at 0798cde
opnsense/plugins at d3c3e79
opnsense/plugins at cb9a5d6
mvc: remove grouped ModelRelationField option handling
The group option collapsed multiple related model rows into a single
display entry while still storing the UUID of one concrete source row.
This makes the selected relation dependent on iteration order and is not
a stable representation of the grouped object.
References:
https://github.com/opnsense/core/commit/fe571ac442efe76c3a1efd3e6f90b8ec4cb6e7bd
