Firewall: NAT: Add the same UI design to the NAT pages as the firewall page (#10359)
* Firewall: NAT: Add the same UI design to the NAT pages as the firewall page from 18533b4, but slightly adjusted as NAT rules do not have sort_order or priority groups, so all grouping happens either by category, or to a synthetic automatic category if the rules contain an is_automatic true boolean.
* Implement sort_order in DNAT controller so the same tree view logic as in firewall rules can be used, this eases maintainence
* Add sort order volatile fields to SourceNatRuleField shared by SNAT, ONAT and NPTv6 inside filter model.
* make sweep
* prio_group is static in NAT rules, so we can use it directly
* Add comment about prio_group inside filter_rule.volt
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.
(cherry picked from commit 6ffad1bb73da9db36c409130fcf00a9af286f94f)
mvc: unify migration message returns a bit
Mostly noticed due to "check log for details" which now in
most cases is not relevant since we use the verbose flag.
Services: Kea DHCPv4/6: Fix missing visual cues for manual mode in DDNS and DHCPv4/6 (#10340)
(cherry picked from commit 720c791b15fbbbbde73c55d818fee63468bcd3ab)
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.
(cherry picked from commit e209de9719943a5224a06f8e155629d1052ddcba)
